Turn a feature request into implementation tasks
Use the product analyst skills to extract requirements, identify ambiguities, and break the feature into tasks with scope and acceptance criteria.
Overview
The Bitwarden AI Plugin Marketplace brings Bitwarden’s engineering practices into Claude Code, from clarifying requirements and researching Jira issues to reviewing code and preparing changes for delivery. Choose plugins for the work you do; several rely on Bitwarden’s standards, repositories, or internal services.
Once a plugin is enabled, Claude can select relevant skills during a conversation, and you can invoke user-accessible skills through their namespaced slash commands. Invoke commands explicitly, or ask Claude to use a named agent for specialized work. Telemetry and documentation hooks run automatically at their configured events. Adding the marketplace makes its plugins discoverable; you install each chosen plugin separately.
Use Cases
Understand a Jira issue before starting
The Atlassian research skill follows linked issues, subtasks, dependencies, and supporting Confluence pages to build context for the work. It needs configured Atlassian credentials.
Evaluate code review feedback
Use the code review skills to assess reviewer comments before changing code, validate potential findings, and classify their severity.
Review changes to Claude Code configuration
The configuration validator routes project guidance, agent definitions, command files, settings, and hooks to targeted reviews for security, structure, and clarity.
Find test gaps for a change
Use assessing-test-coverage to inventory existing coverage for a concrete change, then recommending-test-layers to decide which new tests belong at which layer.
Learn from a Claude Code session
The retrospective skills combine session logs, Git history, code changes, and user feedback to identify useful patterns and opportunities to improve future sessions.
Components
Components belong to individual plugins in the marketplace. Install their parent plugin to get its bundled skills, commands, agents, hooks, or MCP server.
Hooks run automatically while their parent plugin is enabled. See telemetry setup and data collection and documentation hook setup and behavior. To stop a plugin’s hooks, disable that plugin in Claude Code’s plugin manager.
Skills
These plugins' skills 32What you’ll need
Showing all 32
Requirements and design
requirements-elicitation
Extract requirements from specifications, flag ambiguities, and identify constraints.
assessing-requirement-readiness
Judge whether Jira stories are ready to build and test, identifying requirement gaps.
work-breakdown
Turn requirements into implementation tasks with scope, dependencies, and acceptance criteria.
using-figma
Inspect designs, variables, and screenshots through a separately configured Figma Dev Mode MCP server.
Jira issues
researching-jira-issues
Build context from a Jira issue, linked work, dependencies, and supporting Confluence pages.
assessing-jira-issue-relevance
Check whether a single Jira issue still applies to the current codebase.
filing-jira-tickets
Preview and create Jira work items with acceptance criteria and verified dependency links.
Code review and delivery
code-review
Review a GitHub pull request and post validated findings to GitHub.
code-review-local
Review a pull request or local changes and save findings locally without posting.
avoiding-false-positives
Validate potential code review findings against rejection criteria and checks of actual behavior.
classifying-review-findings
Classify validated code review findings by severity using Bitwarden’s review categories.
addressing-code-review-comments
Evaluate reviewer feedback, draft replies, and implement fixes the user confirms.
verifying-doc-parity
Find documentation drift caused by code changes and identify required updates.
perform-preflight
Check tests, code quality, security, and architecture before committing or opening a pull request.
Claude Code configuration
reviewing-claude-config
Route Claude configuration changes to targeted security and quality reviews; excludes SKILL.md files.
reviewing-project-guidance
Check CLAUDE.md guidance for security risks, structure, and actionable instructions.
reviewing-agent-definitions
Review agent definitions for tool-access security, activation triggers, and prompt clarity.
reviewing-command-definitions
Review slash commands and prompts for clarity, shell safety, and valid skill references.
reviewing-runtime-configuration
Review Claude Code settings and hooks for permission scope and unsafe commands.
Application security
analyzing-code-security
Trace attack surfaces and data flows to identify vulnerabilities using OWASP and CWE frameworks.
reviewing-security-architecture
Evaluate authentication, authorization, trust boundaries, data protection, and cryptographic design.
reviewing-dependencies
Assess vulnerable packages, reachable code paths, transitive dependencies, and supply chain risks.
detecting-secrets
Find exposed credentials, distinguish false positives, and guide remediation of leaked secrets.
Test planning and debugging
assessing-test-coverage
Inventory existing tests for a specific change and identify behaviors without coverage.
designing-test-plans
Design tests for ready Jira stories, tracing each test to its acceptance criteria.
recommending-test-layers
Recommend which new tests a change needs and the layer for each.
reading-mailcatcher-api
Retrieve email links from a running Mailcatcher instance for local testing and debugging.
using-stripe-cli
Inspect Stripe test-mode data and advance existing test clocks; other writes are excluded.
Work recaps and retrospectives
daily-recap
Create an interactive HTML recap of your engineering work over a chosen time window.
retrospecting
Analyze session logs, Git changes, and user feedback to recommend improvements for future sessions.
analyzing-git-sessions
Summarize commits and file changes within a time window or commit range.
extracting-session-data
Locate and extract structured data from Claude Code session logs for further analysis.
No matching results.
Commands
8/claude-config-validator:validate-aiReview Claude configuration changes in a pull request and report findings on its diff.
Review a pull request
Enable claude-config-validator in Claude Code and invoke this command with a pull request number or URL; leave the argument blank to use the checked-out branch’s pull request. It produces findings for human review without fixing the reviewed files. See the pull request validation instructions.
Use Claude Code 2.1.210 or later. Older versions can prompt for permission to write the report, causing headless checks to fail.
/claude-config-validator:validate-ai-localReview branch commits and uncommitted Claude configuration changes, then write a local report.
Review local changes
With claude-config-validator enabled in Claude Code, invoke this command from your checkout. Supply a base ref to choose the comparison point, or omit it to use the repository’s default branch. The review includes branch commits and uncommitted work, writes a local report, and posts nothing to GitHub. See the local validation instructions.
Use Claude Code 2.1.210 or later. Older versions can prompt for permission to write the report, causing headless checks to fail.
/bitwarden-init:initCreate a repository CLAUDE.md by analyzing the codebase and applying Bitwarden’s project template.
Create repository guidance
With bitwarden-init enabled in Claude Code, invoke this command in the repository you want to document. It runs the built-in codebase analysis, then applies Bitwarden’s project template. See the repository initialization guide.
/bitwarden-init:enhanceResearch the repository and reorganize an existing CLAUDE.md into Bitwarden’s project template.
Refresh repository guidance
With bitwarden-init enabled in Claude Code, invoke this command in a repository that already has a root CLAUDE.md. It reads the file, researches gaps, and restructures the content into Bitwarden’s project sections. See the enhancement instructions.
/bitwarden-init:init-userChoose behavioral modules through a Q&A to create your user-level CLAUDE.md.
Choose personal guidance
With bitwarden-init enabled in Claude Code, invoke this command to choose modules for ~/.claude/CLAUDE.md, which applies across your projects. Review the proposed diff and confirm Apply before the file is written; an existing file is backed up before overwrite. See the user guidance setup.
/bitwarden-init:init-workspaceChoose Bitwarden guidance modules for a CLAUDE.md shared by your locally cloned Bitwarden repositories.
Set up shared workspace guidance
With bitwarden-init enabled in Claude Code, invoke this command from beneath the folder containing your cloned Bitwarden repositories. Confirm the proposed workspace root, choose guidance modules, review the diff, and confirm Apply. The file lives in that root’s .claude/CLAUDE.md; an existing file is backed up before overwrite. See the workspace setup guide.
/bitwarden-init:enhance-userFind missing behavioral modules and offer to append them to your user-level CLAUDE.md.
Add personal guidance modules
With bitwarden-init enabled in Claude Code, invoke this command when ~/.claude/CLAUDE.md already exists. Choose from the missing modules, review the diff, and confirm Apply. Selected modules are appended without changing existing content, and the original file is backed up. See the user guidance refresh instructions.
/bitwarden-init:enhance-workspaceFind missing Bitwarden guidance modules and offer to append them to your workspace CLAUDE.md.
Add workspace guidance modules
With bitwarden-init enabled in Claude Code, invoke this command and provide the workspace root whose .claude/CLAUDE.md you want to refresh. The file must already exist. Choose missing modules, review the diff, and confirm Apply; selected modules are appended without changing existing content, and the original is backed up. See the workspace guidance refresh instructions.
Agents
7bitwarden-designer
Apply Bitwarden’s design critique framework and select tools for design work and engineering handoff.
Request design support
Enable bitwarden-designer in Claude Code, then ask Claude to use the agent with a design, interface copy, or handoff question. For a critique, include the design’s stage so the review can follow the 30/60/90 framework. See the designer instructions.
product-analyst
Turn Confluence pages, Jira tickets, and other sources into Bitwarden requirements documents.
Request a requirements document
Enable bitwarden-product-analyst in Claude Code, then ask Claude to use product-analyst with your feature request and supporting sources. Jira and Confluence research needs access to those services. See the product analyst instructions.
bitwarden-security-engineer
Triage vulnerabilities, model threats, and analyze code security for Bitwarden.
Request security analysis
Enable bitwarden-security-engineer in Claude Code, then ask Claude to use the agent for a security finding, threat model, dependency audit, or code assessment. Identify the system or code to examine; Aikido findings require access to its integration. See the security engineer instructions.
bitwarden-shepherd
Guide technical strategy ideas through evaluation, implementation planning, and adoption across Bitwarden.
Advance a technical initiative
Enable bitwarden-shepherd in Claude Code, then ask Claude to use the agent with your technical strategy idea or initiative and its current phase. It guides architectural evaluation and coordination while product teams retain their own implementation work. See the shepherd instructions.
bitwarden-software-engineer
Implement stories and fixes for a Bitwarden product team, with code review and QA collaboration.
Assign implementation work
Enable bitwarden-software-engineer in Claude Code, then ask Claude to use the agent with a story, task, or bug in the team’s repository. Include the expected outcome and relevant requirements. See the software engineer instructions.
bitwarden-tech-lead
Scope work and design solutions within a Bitwarden product team, coordinating cross-team technical decisions.
Scope a technical decision
Enable bitwarden-tech-lead in Claude Code, then ask Claude to use the agent with the team’s planning question, implementation alternatives, or cross-team dependency. See the tech lead instructions.
bitwarden-code-reviewer
Review pull requests against Bitwarden’s standards and post validated findings as GitHub comments.
Request a code review
Enable bitwarden-code-review in Claude Code, then ask Claude to use bitwarden-code-reviewer for the pull request you identify. Its workflow validates findings before posting review comments. See the code reviewer instructions.
Hooks
8Session telemetry
At SessionStart, emits session and repository metadata through the telemetry plugin.
Subagent identity telemetry
At SubagentStop, records the completed subagent’s identity.
Slash invocation telemetry
At UserPromptExpansion, records skill or command names from slash invocations.
Skill and agent usage telemetry
After Task, Agent, or Skill use, records the agent or skill identity.
Git linkage telemetry
After matching edits or shell actions, links file paths, successful commits, and new pull requests to the session.
MCP tool usage telemetry
After MCP tool use, records the server and tool names.
Documentation instructions
At SessionStart, adds documentation obligations to Claude’s context when the instruction fragment and jq are available.
Documentation update check
At Stop, can block once per session when code changes in documented scopes lack a documentation update.
MCP servers
1bitwarden-atlassian
Research Jira issues and Confluence pages, with optional Jira creation, linking, and comments.
Bundled with bitwarden-atlassian-tools; requires Node.js 24+ and Atlassian credentials. Live Jira writes require a separate write token; Confluence remains read-only.
Install
Add the marketplace in Claude Code, then install the plugins you need. Each selected plugin installs as a whole, including its bundled components.
Claude Code
- 01
In a Claude Code terminal session on your computer, add the Bitwarden marketplace.
/plugin marketplace add https://github.com/bitwarden/ai-pluginsRestart Claude Code after adding the marketplace.
- 02
Choose the plugins you want from the marketplace’s plugin list. Check the requirements of each selected plugin before installing.
If you select bitwarden-ai-telemetry, its hooks can send your signed-in account email, session identifiers, repository and branch names, file paths, commit identifiers, pull request numbers, and tool names to the configured telemetry destination. They do not collect code contents, prompt text, model responses, or tool arguments and results. Branch and file names are sent as written, so names containing sensitive information can expose it.
Requirements for plugins with automatic hooks
- bitwarden-ai-telemetry needs Python 3 on PATH. Set
BW_TELEMETRY_OTLPto an HTTPS endpoint on bitwarden.pw or one of its subdomains; without an accepted destination, the hooks emit no telemetry and display a throttled warning. Git and GitHub CLI support optional Git linkage events. See telemetry configuration. - bitwarden-doc-parity needs Bash, Git, and jq on PATH. Its hooks allow the session to continue when required tools are unavailable or the working directory is not a Git repository. See documentation parity requirements.
For bitwarden-atlassian-tools, have Node.js 24+ available and configure
ATLASSIAN_CLOUD_ID,ATLASSIAN_EMAIL,ATLASSIAN_JIRA_READ_ONLY_TOKEN, andATLASSIAN_CONFLUENCE_READ_ONLY_TOKENin the environment available to Claude Code. Use the Atlassian setup and token scopes. LeaveATLASSIAN_JIRA_WRITE_TOKENunset to prevent live Jira writes; previews remain available. - bitwarden-ai-telemetry needs Python 3 on PATH. Set
- 03
Open the plugin manager in the Claude Code session.
/pluginIn Discover, find a plugin from
bitwarden-marketplace, open its details, and install it in the scope you need: user, project, or local. Repeat for any other plugins you chose. - 04
Restart Claude Code after installing the selected plugins so their components and any environment configuration load.
- 05
Reopen the plugin manager and check that your selected plugins appear in Installed and are enabled.
/pluginFor a plugin with user-accessible skills, type
/in the session and look for skills prefixed by that plugin’s name. This confirms availability in Claude Code; it does not test access to connected services.