
bitwarden-product-analyst
Product analyst plugin that produces Bitwarden requirements documents and user-facing release notes.
- version
- 0.1.7
- GitHub stars
- 165
What it does
- Adds the
product-analystagent plusrequirements-elicitation,work-breakdown, andwriting-release-notesskills for Bitwarden specifications - Covers requirements extraction from Confluence initiatives, Jira tickets, and other sources, including ambiguity flagging and testable acceptance criteria
- Applies Bitwarden security principles P01–P06 and distinguishes all four web surfaces and all plan tiers in requirements
- Designed for product teams at Bitwarden that need output in their internal template and vocabulary, with Jira and Slack release sources
Product analyst agent for creating comprehensive Bitwarden requirements documents from multiple sources, and writing user-facing release notes
Add marketplace
/plugin marketplace add bitwarden/ai-pluginsRun it inside Claude Code once, then install the plugin below.
Install
/plugin install bitwarden-product-analyst@bitwarden-marketplaceRun it inside Claude Code after adding the marketplace.
Files
Discovered from sourceRequirements Elicitation
Key Capabilities
- Extract Requirements — Identify functional and non-functional requirements from multiple sources
- Clarify Ambiguities — Flag unclear specifications and formulate targeted questions
- Identify Constraints — Find technical, business, security, and resource limitations
- Categorize Requirements — Organize by type (functional, non-functional, security, performance)
Approach
1. Read and Understand
- Read entire specification thoroughly, including all referenced documents
- Identify the primary source (main requirement) vs. supporting documentation
- Note the scope and context of the request
2. Extract Explicit Requirements
- Capture clearly stated requirements
- Document exact specifications (API signatures, data formats, performance metrics)
- Preserve technical details verbatim
3. Identify Implicit Requirements
- Infer unstated but necessary requirements (e.g., error handling, validation, logging)
- Consider security implications based on Bitwarden security principles (P01-P06)
- Identify data classification needs (Vault Data, Protected Data, secure channels)
4. Flag Ambiguities and Gaps
- Document unclear or missing information
- Formulate specific questions to resolve ambiguities
- Identify conflicting requirements between sources
- Note assumptions being made
5. Document Constraints
- Technical constraints (APIs, platforms, compatibility)
- Security constraints (data protection, authentication, authorization)
- Resource constraints (performance, storage, bandwidth)
- Business constraints (timeline, scope, dependencies)
6. Create Acceptance Criteria
- For each requirement, define testable acceptance criteria
- Specify verification methods (commands, tests, manual checks)
- Include edge cases and error scenarios
Bitwarden-Specific Considerations
Security Requirements
Always consider and document:
- Data classification — Is this Vault Data, Protected Data, or other?
- Data states — Requirements for data at rest, in use, in transit
- Security channels — Need for secure/trusted channels?
- Security principles — Which principles (P01-P06) apply?
- Threat scenarios — What could go wrong?
Common Bitwarden Requirement Types
- Authentication/Authorization — Who can access what?
- Encryption — What data needs protection and how?
- Zero-knowledge — Server must not have access to plaintext (P01)
- Cross-platform — Works on all Bitwarden clients?
- Backwards compatibility — Maintains existing behavior?
Example
See examples/export-functionality.md for a complete worked example.
Best Practices
Do's
- ✅ Ask "what" questions, not "how" — Focus on requirements, not implementation
- ✅ Document assumptions explicitly — Make implicit knowledge visible
- ✅ Create testable acceptance criteria — Avoid vague success measures
- ✅ Consider all user types — Free users, premium, enterprise, admins
- ✅ Think about edge cases — Empty vaults, huge vaults, network failures
- ✅ Reference Bitwarden security principles — Ground security requirements in P01-P06
- ✅ Use Bitwarden vocabulary — Standard terminology for data, channels, security
Don'ts
- ❌ Avoid: Making technical implementation decisions — That's the architect's job
- ❌ Avoid: Assuming unstated requirements are obvious — Explicit is better
- ❌ Avoid: Generic acceptance criteria — "It works" is not testable
- ❌ Avoid: Ignoring security implications — Security is never optional at Bitwarden
- ❌ Avoid: Skipping constraints — They're as important as requirements
Output Format
Organize extracted requirements in structured sections:
## Functional Requirements
1. REQ-F-001: [Specific capability the system must have]
- **Acceptance Criteria**: [Testable condition]
- **Priority**: Critical | High | Medium | Low
## Non-Functional Requirements
- **Performance**: [Response time, throughput, resource usage]
- **Reliability**: [Error handling, edge cases, availability]
- **Compatibility**: [Platform support, backwards compatibility]
- **Usability**: [User experience expectations]
## Security Requirements
- **Data Classification**: [Vault Data | Protected Data | Other]
- **Security Principles**: [P01, P02, P03, P04, P05, P06 as applicable]
- **Threat Considerations**: [What could go wrong?]
## Constraints
- **Technical**: [APIs, platforms, dependencies]
- **Business**: [Timeline, scope, resources]
- **Security**: [Compliance, encryption, authentication]
## Open Questions
1. [Specific question needing stakeholder input]
2. [Ambiguity requiring clarification]
3. [Missing information that blocks complete specification]
## Assumptions
- [Assumption 1: explicit statement of what's assumed]
- [Assumption 2: should be validated with stakeholders]
Readme
Bitwarden Product Analyst Plugin
Claude Code skills for product analysis at Bitwarden. Generic AI assistance doesn't know our requirements format, security principles, Confluence initiative structure, or how we think about plan tiers and client surfaces. These skills keep Claude focused on how we specify software here.
Agent
| Agent | What It Does |
|---|---|
product-analyst | Reads Confluence initiative pages, Jira tickets, and other sources to produce structured requirements documents following Bitwarden's template. Applies security principles (P01–P06), distinguishes all four web surfaces and all plan tiers, attributes TBDs by owner (PM/Design/Engineering), and surfaces post-MVP candidates. |
Skills
| Skill | What It Does |
|---|---|
requirements-elicitation | Extracts functional, non-functional, and security requirements from specifications. Flags ambiguities, identifies constraints, and creates testable acceptance criteria using Bitwarden security vocabulary. |
work-breakdown | Decomposes features into implementable tasks organized by phase. Identifies cross-repo dependencies (bitwarden/server vs. bitwarden/clients), task ordering, and team assignments. |
writing-release-notes | Produces user-facing release notes from a Jira release tag and the weekly #release Slack thread. Filters to user-visible changes, respects feature flag enablement, and for server releases always surfaces flag removals in user-facing language. |
Installation
Available through Bitwarden's internal Claude Code marketplace:
# Add the Bitwarden marketplace (if not already added)
/plugin marketplace add https://github.com/bitwarden/ai-plugins
# Install the product analyst plugin
/plugin install bitwarden-product-analyst@bitwarden-marketplace
# Restart Claude Code
Usage
Analyze requirements from https://bitwarden.atlassian.net/wiki/spaces/PROD/pages/123456/Feature-Name
Create a spec document from PROJ-1234
Write a spec for adding passkey support to the browser extension
Write release notes for https://bitwarden.atlassian.net/projects/CL/versions/12345
Draft release notes for the 2025.7.0 server release
References
requirements-elicitation / product-analyst
- Bitwarden Security Definitions — Vault Data, Protected Data, Secure Channel, Trusted Channel vocabulary
- Bitwarden Security Principles — P01–P06 foundation principles
- Product Initiative Template — Canonical PM template; maps to
references/requirements-template.md - Requirements Template — Full requirements document structure
writing-release-notes
- Bitwarden Atlassian Tools — Provides the
search_issues,get_issue, andget_issue_commentsMCP tools used for automated Jira lookups - Jira release report pages (
https://bitwarden.atlassian.net/projects/<PROJECT>/versions/<ID>/tab/release-report-all-issues) and the weekly#releaseSlack thread are the two data sources this skill synthesizes
Details
- Marketplace
- bitwarden/ai-plugins
- Source
- plugins/bitwarden-product-analyst
- Category
- Community
More from bitwarden/ai-plugins
All 25- bitwarden-retrospective-toolsv1.2.0
- bitwarden-security-engineerv2.1.0
- bitwarden-shepherdv1.0.1
- bitwarden-software-engineerv1.1.0
- bitwarden-stripe-toolsv1.0.0
- bitwarden-tech-leadv3.1.0
- bitwarden-testing-toolsv1.5.1
- bitwarden-testmo-toolsv1.0.0
- claude-config-validatorv2.3.1
- claude-retrospectivev1.1.1
- atlassian-readerv1.2.1
- bitwarden-abacusv0.2.0
- bitwarden-abacus-toolsv1.3.0
- bitwarden-adr-toolsv1.0.0
- bitwarden-ai-telemetryv1.5.1
- bitwarden-atlassian-toolsv2.9.1
- bitwarden-code-reviewv3.1.0
- bitwarden-delivery-toolsv4.0.1
- bitwarden-design-toolsv0.1.0
- bitwarden-designerv0.1.0
- bitwarden-devops-engineerv0.3.1
- bitwarden-doc-parityv1.1.0
- bitwarden-initv1.2.2
- bitwarden-mailcatcher-toolsv1.0.0
Similar to bitwarden-product-analyst
More AI Agents & Orchestration
eccaffaan-m/everything-claude-code308.6K starsHarness-native ECC operator layer - 72 agents, 328 skills, 99 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready work
mattpocock-skillsmattpocock/skills304.3K starsMatt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
agent-sdk-devanthropics/claude-code156.1K starsDevelopment kit for working with the Claude Agent SDK
agent-skillsaddyosmani/agent-skills119.6K starsProduction-grade engineering skills covering every phase of software development: spec, plan, build, verify, review, and ship.
agentdbruvnet/ruflo82.2K starsAgentDB (external: maintained in ruvnet/agentdb, pinned to commit 27678c3, plugin 3.6.0): agentdb's own standalone MCP server pinned to agentdb@3.6.0 (vector me
last30daysmvanhorn/last30days-skill72.2K starsResearch any topic across Reddit, X, YouTube, TikTok, Instagram, Hacker News, Polymarket, GitHub, and 5+ more sources. AI agent scores by upvotes, likes, and re