From 20c8d21c3209d6fcf3e9a7df75f8dc3789c3dd9c Mon Sep 17 00:00:00 2001 From: Mick Letofsky Date: Fri, 24 Apr 2026 17:49:04 +0200 Subject: [PATCH 1/2] Rename architect plugin to bitwarden-tech-lead --- .claude-plugin/marketplace.json | 6 +- README.md | 2 +- plugins/bitwarden-architect/README.md | 56 ------------- plugins/bitwarden-architect/agents/AGENT.md | 28 ------- .../.claude-plugin/plugin.json | 6 +- .../CHANGELOG.md | 8 +- plugins/bitwarden-tech-lead/README.md | 78 +++++++++++++++++++ plugins/bitwarden-tech-lead/agents/AGENT.md | 32 ++++++++ .../skills/architecting-solutions/SKILL.md | 2 +- 9 files changed, 125 insertions(+), 93 deletions(-) delete mode 100644 plugins/bitwarden-architect/README.md delete mode 100644 plugins/bitwarden-architect/agents/AGENT.md rename plugins/{bitwarden-architect => bitwarden-tech-lead}/.claude-plugin/plugin.json (86%) rename plugins/{bitwarden-architect => bitwarden-tech-lead}/CHANGELOG.md (57%) create mode 100644 plugins/bitwarden-tech-lead/README.md create mode 100644 plugins/bitwarden-tech-lead/agents/AGENT.md rename plugins/{bitwarden-architect => bitwarden-tech-lead}/skills/architecting-solutions/SKILL.md (92%) diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json index 80a96552..8eb0bde4 100644 --- a/.claude-plugin/marketplace.json +++ b/.claude-plugin/marketplace.json @@ -65,9 +65,9 @@ "description": "GitHub Actions workflow compliance, action security auditing, and org-wide CI/CD remediation." }, { - "name": "bitwarden-architect", - "source": "./plugins/bitwarden-architect", - "version": "1.0.0", + "name": "bitwarden-tech-lead", + "source": "./plugins/bitwarden-tech-lead", + "version": "2.0.0", "description": "Software architect agent for planning features across any Bitwarden repository. Discovers platform context dynamically via CLAUDE.md and repo-local planning skills." } ] diff --git a/README.md b/README.md index 007a0d62..2721a19b 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ A curated collection of plugins for AI-assisted development at Bitwarden. Enable | Plugin | Version | Description | | ------------------------------------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------- | -| [bitwarden-architect](plugins/bitwarden-architect/) | 1.0.0 | Software architect for technical planning, architecture reviews, and implementation phasing | +| [bitwarden-tech-lead](plugins/bitwarden-tech-lead/) | 2.0.0 | Software architect for technical planning, architecture reviews, and implementation phasing | | [bitwarden-atlassian-tools](plugins/bitwarden-atlassian-tools/) | 2.2.3 | Read-only Atlassian access via MCP server with deep Jira issue research skill | | [bitwarden-code-review](plugins/bitwarden-code-review/) | 1.9.0 | Autonomous code review agent following Bitwarden engineering standards with GitHub integration | | [bitwarden-devops-engineer](plugins/bitwarden-devops-engineer/) | 0.1.1 | DevOps engineering assistant: workflow compliance linting, action security auditing, and org-wide CI/CD remediation | diff --git a/plugins/bitwarden-architect/README.md b/plugins/bitwarden-architect/README.md deleted file mode 100644 index df660200..00000000 --- a/plugins/bitwarden-architect/README.md +++ /dev/null @@ -1,56 +0,0 @@ -# Bitwarden Software Architect Plugin - -## Overview - -Software architecture planning for Bitwarden repositories. Generic AI assistance doesn't know our zero-knowledge constraints, multi-client reality, dual-ORM strategy, or V+/-2 version matrix. This plugin keeps architecture decisions grounded in how we actually build software at Bitwarden. - -## Agent - -| Agent | What It Does | -| --------------------- | ------------------------------------------------------------------------------ | -| `bitwarden-architect` | Produces implementation plans grounded in Bitwarden's architectural principles | - -## Skills - -| Skill | What It Does | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ | -| `architecting-solutions` | Principal engineer perspective on architecture decisions. Provides the architectural judgment framework applied across all planning. | - -## Cross-Plugin Integration - -| Plugin | How It's Used | -| ----------------------------- | ------------------------------------------------------------------------ | -| `bitwarden-security-engineer` | Security context (P01-P06), architecture pattern review, threat modeling | -| `bitwarden-product-analyst` | Consumes requirements documents as upstream input | -| `bitwarden-software-engineer` | Implementation conventions for server, client, and database decisions | -| `bitwarden-atlassian-tools` | Jira issue research and Confluence page access | - -All cross-plugin skills are required because we rely upon each of them for a rich, complete workflow. - -## Installation - -```bash -/plugin install bitwarden-architect@bitwarden-marketplace -``` - -## Usage - -The architect agent activates when you need to plan a feature, review an architecture decision, assess blast radius, or produce an implementation plan: - -``` -Plan the implementation for PM-12345 -``` - -``` -Review the architecture of [feature area] and suggest improvements -``` - -``` -Assess the blast radius of adding [capability] to [service] -``` - -## References - -- [Bitwarden Security Definitions](https://contributing.bitwarden.com/architecture/security/definitions) -- [Bitwarden Security Principles](https://contributing.bitwarden.com/architecture/security/principles/) -- [Bitwarden Contributing Guidelines](https://contributing.bitwarden.com/contributing/) diff --git a/plugins/bitwarden-architect/agents/AGENT.md b/plugins/bitwarden-architect/agents/AGENT.md deleted file mode 100644 index 1804cc62..00000000 --- a/plugins/bitwarden-architect/agents/AGENT.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -name: bitwarden-architect -description: "Software architect for technical planning, architecture decisions, blast radius assessment, and implementation phasing across Bitwarden repositories. Use when planning a feature, reviewing architecture, assessing blast radius, choosing between approaches, or producing a phased implementation plan. Produces structured architecture plans ready for the software-engineer agent." -model: opus -tools: Read, Write, Glob, Grep, Skill -skills: - - architecting-solutions -color: cyan ---- - -You are a senior software architect at Bitwarden. Your primary job is not writing code — it's surveying the landscape of possible solutions, choosing the right approach, and producing plans that engineers execute. You plan, you evaluate trade-offs, you break work into phases, and you ensure the pieces fit together. When a feature needs building, you decide _what_ gets built and _how_ the parts connect — then you hand implementation to engineers who specialize in writing code. - -## Orientation - -Before proposing anything, orient yourself: - -- **Read the repo's CLAUDE.md** — learn architecture constraints, security rules, code organization, and available platform-specific skills -- **Explore the codebase** — find existing implementations of similar features, relevant services, and reusable patterns before designing anything new - -## Cross-Plugin Integration - -All cross-plugin skills are required. If unavailable, **STOP** and alert the human that they must be installed. - -Use their skills to inform your planning: - -- **Security** (`bitwarden-security-engineer`): `Skill(bitwarden-security-context)` for P01-P06 principles, `Skill(reviewing-security-architecture)` for architecture pattern validation, `Skill(threat-modeling)` for formal threat models -- **Requirements** (`bitwarden-product-analyst`): Consume requirements documents as primary input when available in the working directory -- **Jira/Confluence** (`bitwarden-atlassian-tools`): `Skill(researching-jira-issues)` for Jira tickets, `get_confluence_page` MCP tool for Confluence pages diff --git a/plugins/bitwarden-architect/.claude-plugin/plugin.json b/plugins/bitwarden-tech-lead/.claude-plugin/plugin.json similarity index 86% rename from plugins/bitwarden-architect/.claude-plugin/plugin.json rename to plugins/bitwarden-tech-lead/.claude-plugin/plugin.json index 26924cf4..619123a1 100644 --- a/plugins/bitwarden-architect/.claude-plugin/plugin.json +++ b/plugins/bitwarden-tech-lead/.claude-plugin/plugin.json @@ -1,12 +1,12 @@ { - "name": "bitwarden-architect", - "version": "1.0.0", + "name": "bitwarden-tech-lead", + "version": "2.0.0", "description": "Software architect agent for planning features across any Bitwarden repository. Discovers platform context dynamically via CLAUDE.md and repo-local planning skills.", "author": { "name": "Bitwarden", "url": "https://github.com/bitwarden" }, - "homepage": "https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-architect", + "homepage": "https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-tech-lead", "repository": "https://github.com/bitwarden/ai-plugins", "keywords": [ "architect", diff --git a/plugins/bitwarden-architect/CHANGELOG.md b/plugins/bitwarden-tech-lead/CHANGELOG.md similarity index 57% rename from plugins/bitwarden-architect/CHANGELOG.md rename to plugins/bitwarden-tech-lead/CHANGELOG.md index 21fc5a7c..eb2991e7 100644 --- a/plugins/bitwarden-architect/CHANGELOG.md +++ b/plugins/bitwarden-tech-lead/CHANGELOG.md @@ -1,10 +1,16 @@ # Changelog -All notable changes to the `bitwarden-architect` plugin will be documented in this file. +All notable changes to the `bitwarden-tech-lead` plugin will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [2.0.0] - 2026-04-24 + +### Changed + +- **BREAKING:** Renamed plugin from `bitwarden-architect` to `bitwarden-tech-lead`. Users must uninstall the old plugin and reinstall under the new name (`/plugin install bitwarden-tech-lead@bitwarden-marketplace`). The agent's callable identifier (`name:` in AGENT.md frontmatter) also changed to `bitwarden-tech-lead`. + ## [1.0.0] - 2026-04-16 ### Added diff --git a/plugins/bitwarden-tech-lead/README.md b/plugins/bitwarden-tech-lead/README.md new file mode 100644 index 00000000..30bfacf7 --- /dev/null +++ b/plugins/bitwarden-tech-lead/README.md @@ -0,0 +1,78 @@ +# Bitwarden Tech Lead Plugin + +## Overview + +Tech lead agent for a Bitwarden product team. Generic AI assistance doesn't know our zero-knowledge constraints, multi-client reality, dual-ORM strategy, or V+/-2 version matrix — and it certainly doesn't know how we actually operate: the Software Initiative Funnel, the Work Transition Playbook, the Architecture / Engineering Operating Model, or the Technical Strategy Ideas backlog. This plugin keeps tech-lead decisions grounded in how we actually build software at Bitwarden and how work actually moves between architecture, shepherds, and teams. + +The tech lead represents a team inside Bitwarden's architecture process — architecting inside the team's domain while staying coherent with the holistic architecture, receiving work from initiative shepherds, breaking epics down into stories, and surfacing team-level patterns upstream into technical strategy. + +## Agent + +| Agent | What It Does | +| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `bitwarden-tech-lead` | Plans and architects inside a team's scope, works alongside initiative shepherds, receives work transitions, breaks down initiative epics, and surfaces ideas to architecture | + +## Skills + +| Skill | What It Does | +| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `architecting-solutions` | Tech lead's architectural judgment framework: security mindset, blast radius, Bitwarden constraints, working with the architecture group and shepherds | + +## Cross-Plugin Integration + +| Plugin | How It's Used | +| ----------------------------- | ------------------------------------------------------------------------ | +| `bitwarden-security-engineer` | Security context (P01-P06), architecture pattern review, threat modeling | +| `bitwarden-product-analyst` | Consumes requirements documents as upstream input | +| `bitwarden-software-engineer` | Implementation conventions for server, client, and database decisions | +| `bitwarden-atlassian-tools` | Jira issue research and Confluence page access | + +All cross-plugin skills are required because we rely upon each of them for a rich, complete workflow. + +## Installation + +```bash +/plugin install bitwarden-tech-lead@bitwarden-marketplace +``` + +### Upgrading from `bitwarden-architect` + +This plugin was previously named `bitwarden-architect`. The rename reflects Bitwarden's actual role nomenclature — teams are led by tech leads, not team-level architects; the architecture group operates upstream. To upgrade: + +```bash +/plugin uninstall bitwarden-architect@bitwarden-marketplace +/plugin install bitwarden-tech-lead@bitwarden-marketplace +``` + +The `architecting-solutions` skill is retained (refactored around the tech-lead perspective and holistic architecture). Three new skills are added: `navigating-the-initiative-funnel`, `receiving-work-transitions`, and `contributing-to-technical-strategy`. + +## Usage + +The tech lead agent activates when you're planning work inside your team's scope, receiving an initiative epic, preparing to break it down, receiving a work transition, or evaluating whether a team-level pattern of pain belongs upstream in the funnel: + +``` +Plan the implementation for PM-12345 within our team +``` + +``` +Break down the epic BW-2025-423 into stories for our team +``` + +``` +We're receiving a framework transition from the Platform team. Help me prepare. +``` + +``` +Is this pain we keep hitting something that belongs in Architecture's idea backlog? +``` + +## References + +- [Software Initiative Funnel](https://bitwarden.atlassian.net/wiki/spaces/EN/pages/584515614) +- [Work Transition Playbook](https://bitwarden.atlassian.net/wiki/spaces/EN/pages/2521038855) +- [Architecture / Engineering Operating Model](https://bitwarden.atlassian.net/wiki/spaces/EN/pages/1286963201) +- [Technical Strategy Ideas](https://bitwarden.atlassian.net/wiki/spaces/EN/pages/2344517656) +- [Idea-Based Initiatives](https://bitwarden.atlassian.net/wiki/spaces/EN/pages/2785181779) +- [Bitwarden Security Definitions](https://contributing.bitwarden.com/architecture/security/definitions) +- [Bitwarden Security Principles](https://contributing.bitwarden.com/architecture/security/principles/) +- [Bitwarden Contributing Guidelines](https://contributing.bitwarden.com/contributing/) diff --git a/plugins/bitwarden-tech-lead/agents/AGENT.md b/plugins/bitwarden-tech-lead/agents/AGENT.md new file mode 100644 index 00000000..185aaad0 --- /dev/null +++ b/plugins/bitwarden-tech-lead/agents/AGENT.md @@ -0,0 +1,32 @@ +--- +name: bitwarden-tech-lead +description: "Tech lead for a Bitwarden product team. Architects solutions inside the team's domain while staying coherent with Bitwarden's holistic architecture. Use when planning work inside a team's scope, receiving a work transition, breaking down an initiative epic, and choosing between approaches within a team." +model: opus +tools: Read, Write, Glob, Grep, Skill +skills: + - architecting-solutions +color: cyan +--- + +You are a tech lead embedded in a Bitwarden product team. Your primary job is not writing code — it's surveying the landscape of possible solutions inside your team's domain, choosing the right approach, and producing plans that the team executes. You plan, you evaluate trade-offs, you break epic-level work into stories, and you make sure the pieces fit together both inside your team and alongside the rest of Bitwarden's architecture. + +You are not the architecture group. Architecture operates upstream, shepherding broad technical initiatives through the Software Initiative Funnel. You are downstream of that — you represent your team inside those initiatives, and you own the decisions that fall within your team's scope. The operating model framing applies: the question is not whether your team needs Architecture's permission — it doesn't. The question is whether the work has architectural implications that benefit from their input. When it does, surface it. When it doesn't, decide and move. + +You are not the shepherd either. Shepherds are Staff+ engineers who drive a single initiative across teams. You work alongside them: you break their epic into your team's stories, estimate with your team, review early PRs for approach alignment, and feed concerns back up. You own the _how_ inside your team; the shepherd owns the cross-team vision. + +## Orientation + +Before proposing anything, orient yourself: + +- **Read the repo's CLAUDE.md** — learn architecture constraints, security rules, code organization, and available platform-specific skills +- **Explore the codebase** — find existing implementations of similar features, relevant services, and reusable patterns before designing anything new + +## Cross-Plugin Integration + +All cross-plugin skills are required. If unavailable, **STOP** and alert the human that they must be installed. + +Use their skills to inform your planning: + +- **Security** (`bitwarden-security-engineer`): `Skill(bitwarden-security-context)` for P01-P06 principles, `Skill(reviewing-security-architecture)` for architecture pattern validation, `Skill(threat-modeling)` for formal threat models +- **Requirements** (`bitwarden-product-analyst`): Consume requirements documents as primary input when available in the working directory +- **Jira/Confluence** (`bitwarden-atlassian-tools`): `Skill(researching-jira-issues)` for Jira tickets, `get_confluence_page` MCP tool for Confluence pages diff --git a/plugins/bitwarden-architect/skills/architecting-solutions/SKILL.md b/plugins/bitwarden-tech-lead/skills/architecting-solutions/SKILL.md similarity index 92% rename from plugins/bitwarden-architect/skills/architecting-solutions/SKILL.md rename to plugins/bitwarden-tech-lead/skills/architecting-solutions/SKILL.md index 734126ed..d145a168 100644 --- a/plugins/bitwarden-architect/skills/architecting-solutions/SKILL.md +++ b/plugins/bitwarden-tech-lead/skills/architecting-solutions/SKILL.md @@ -1,6 +1,6 @@ --- name: architecting-solutions -description: Principal engineer perspective on architecture, system design, architecture reviews, blast radius assessment, trade-off analysis, and decision-making. Use when planning a solution, reviewing architecture, assessing blast radius, evaluating trade-offs, or needing expert software engineering advice. +description: Tech lead perspective on architecture, system design, architecture reviews, blast radius assessment, trade-off analysis, and decision-making. Use when planning a solution, reviewing architecture, assessing blast radius, evaluating trade-offs, or needing expert software engineering advice. --- ## Security Mindset From 309e6c9ec57f95c4a03168c2ba32ed971283aa0c Mon Sep 17 00:00:00 2001 From: Mick Letofsky Date: Tue, 28 Apr 2026 11:04:46 +0200 Subject: [PATCH 2/2] Nuke the funnel things --- plugins/bitwarden-tech-lead/README.md | 22 ++++++++------------- plugins/bitwarden-tech-lead/agents/AGENT.md | 4 ---- 2 files changed, 8 insertions(+), 18 deletions(-) diff --git a/plugins/bitwarden-tech-lead/README.md b/plugins/bitwarden-tech-lead/README.md index 30bfacf7..8275eb40 100644 --- a/plugins/bitwarden-tech-lead/README.md +++ b/plugins/bitwarden-tech-lead/README.md @@ -8,15 +8,15 @@ The tech lead represents a team inside Bitwarden's architecture process — arch ## Agent -| Agent | What It Does | -| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `bitwarden-tech-lead` | Plans and architects inside a team's scope, works alongside initiative shepherds, receives work transitions, breaks down initiative epics, and surfaces ideas to architecture | +| Agent | What It Does | +| --------------------- | ------------------------------------------ | +| `bitwarden-tech-lead` | Plans and architects inside a team's scope | ## Skills -| Skill | What It Does | -| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `architecting-solutions` | Tech lead's architectural judgment framework: security mindset, blast radius, Bitwarden constraints, working with the architecture group and shepherds | +| Skill | What It Does | +| ------------------------ | --------------------------------------------------------------------------------------------------- | +| `architecting-solutions` | Tech lead's architectural judgment framework: security mindset, blast radius, Bitwarden constraints | ## Cross-Plugin Integration @@ -44,28 +44,22 @@ This plugin was previously named `bitwarden-architect`. The rename reflects Bitw /plugin install bitwarden-tech-lead@bitwarden-marketplace ``` -The `architecting-solutions` skill is retained (refactored around the tech-lead perspective and holistic architecture). Three new skills are added: `navigating-the-initiative-funnel`, `receiving-work-transitions`, and `contributing-to-technical-strategy`. - ## Usage -The tech lead agent activates when you're planning work inside your team's scope, receiving an initiative epic, preparing to break it down, receiving a work transition, or evaluating whether a team-level pattern of pain belongs upstream in the funnel: +The tech lead agent activates when you're working inside your team's scope: ``` Plan the implementation for PM-12345 within our team ``` ``` -Break down the epic BW-2025-423 into stories for our team +Break down the epic BW-123456 into stories for our team ``` ``` We're receiving a framework transition from the Platform team. Help me prepare. ``` -``` -Is this pain we keep hitting something that belongs in Architecture's idea backlog? -``` - ## References - [Software Initiative Funnel](https://bitwarden.atlassian.net/wiki/spaces/EN/pages/584515614) diff --git a/plugins/bitwarden-tech-lead/agents/AGENT.md b/plugins/bitwarden-tech-lead/agents/AGENT.md index 185aaad0..3a48f229 100644 --- a/plugins/bitwarden-tech-lead/agents/AGENT.md +++ b/plugins/bitwarden-tech-lead/agents/AGENT.md @@ -10,10 +10,6 @@ color: cyan You are a tech lead embedded in a Bitwarden product team. Your primary job is not writing code — it's surveying the landscape of possible solutions inside your team's domain, choosing the right approach, and producing plans that the team executes. You plan, you evaluate trade-offs, you break epic-level work into stories, and you make sure the pieces fit together both inside your team and alongside the rest of Bitwarden's architecture. -You are not the architecture group. Architecture operates upstream, shepherding broad technical initiatives through the Software Initiative Funnel. You are downstream of that — you represent your team inside those initiatives, and you own the decisions that fall within your team's scope. The operating model framing applies: the question is not whether your team needs Architecture's permission — it doesn't. The question is whether the work has architectural implications that benefit from their input. When it does, surface it. When it doesn't, decide and move. - -You are not the shepherd either. Shepherds are Staff+ engineers who drive a single initiative across teams. You work alongside them: you break their epic into your team's stories, estimate with your team, review early PRs for approach alignment, and feed concerns back up. You own the _how_ inside your team; the shepherd owns the cross-team vision. - ## Orientation Before proposing anything, orient yourself: