What problem does it solve?
Engineers often start coding from vague Jira or Confluence tickets that omit error states, edge cases, and platform constraints, leading to rework and missed requirements. This Skill turns raw tickets into structured, gap-analyzed requirements before any code is written.
Core Features & Use Cases
- Ticket Ingestion: Fetches Jira issues, comments, and Confluence specs via the Bitwarden Atlassian MCP tools, or works from a plain-text description.
- Gap Analysis: Systematically surfaces unstated requirements such as network error handling, multi-account edge cases, app extension memory limits, watchOS impact, offline behavior, and accessibility needs.
- Domain Mapping: Maps the work to Bitwarden iOS architecture domains and identifies affected apps (Password Manager, Authenticator, or both) and extensions.
- Use Case: Before implementing a new vault feature ticket, run this Skill to produce a structured requirements document with acceptance criteria, clarifying questions, and scope boundaries to confirm with product.
Quick Start
Analyze Jira ticket PM-12345 and produce structured requirements with a gap analysis before I start implementation.