// Refine requirements, analyze a ticket, perform gap analysis, or clarify what a Jira/Confluence ticket is asking before coding in Bitwarden iOS. Use when asked to "refine requirements", "analyze ticket", "gap analysis", "clarify ticket", "what does this ticket mean", or to understand scope before implementation begins.
Convert an XCTest file to Swift Testing framework. Use when asked to "convert to Swift Testing", "migrate XCTest", "convert test file", "xctest to swift testing", "migrate tests to Swift Testing", or when explicitly asked to convert existing XCTest-based tests.
Convert a hand-written bespoke mock to a Sourcery AutoMockable-generated mock. Use this skill whenever the user says "convert this mock", "migrate mock to AutoMockable", "replace bespoke mock", "use Sourcery for this mock", or mentions wanting to convert a Mock*.swift file to use `// sourcery: AutoMockable`. Also use this skill proactively when you notice a new protocol being created without the annotation, or when an existing bespoke mock is being modified and AutoMockable would be sufficient.
Write tests, add test coverage, unit test, or add missing tests for Bitwarden iOS. Use when asked to "write tests", "add test coverage", "test this", "unit test", "add tests for", "missing tests", or when creating test files for new implementations.
Build the project, run tests, lint, format, spell check, generate mocks, or verify the build passes for Bitwarden iOS. Use when asked to "build", "run tests", "lint", "format", "verify build", "check if it compiles", "run swiftlint", "run swiftformat", "generate mocks", or to execute any part of the build/test/verify pipeline.
Implement, write code, add a new screen, create a feature, new view, new processor, or wire up a new service in Bitwarden iOS. Use when asked to "implement", "write code", "add screen", "create feature", "new view", "new processor", "add service", or when translating a design doc into actual Swift code.
Plan implementation, design an approach, or create an architecture plan for a Bitwarden iOS feature. Use when asked to "plan implementation", "design approach", "architecture plan", "how should I implement", "what files do I need", or to create a design doc before writing code.
| name | refining-ios-requirements |
| description | Refine requirements, analyze a ticket, perform gap analysis, or clarify what a Jira/Confluence ticket is asking before coding in Bitwarden iOS. Use when asked to "refine requirements", "analyze ticket", "gap analysis", "clarify ticket", "what does this ticket mean", or to understand scope before implementation begins. |
Use this skill to analyze a Jira or Confluence ticket and produce structured, implementation-ready requirements before writing any code.
If a ticket ID or URL is provided, fetch it via MCP:
mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue for Jira ticketsmcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_comments for additional contextmcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page for Confluence specsIf no ticket is provided, ask for a description of the requirements.
Identify and list:
Identify unstated requirements the ticket may have missed:
Error states
Edge cases
Platform concerns
Accessibility
Determine which Bitwarden iOS domain(s) are involved. Read Docs/Architecture.md (Architecture Structure section) for the canonical domain list and descriptions.
Determine which app(s) are affected:
## Ticket: [PM-XXXXX] — [Title]
### What
[1-2 sentence summary of what needs to be built]
### Why
[Business/user reason for the change]
### Acceptance Criteria
1. [Criterion 1]
2. [Criterion 2]
### Gap Analysis
**Unstated requirements identified:**
- [ ] Error state: [description]
- [ ] Edge case: [description]
- [ ] Platform concern: [description]
**Clarifying questions (if any):**
1. [Question for product/design]
### Scope
- **Domain**: [from Architecture Structure domain list]
- **App(s)**: [Password Manager / Authenticator / Both]
- **Extensions affected**: [AutoFill / Action / Share / Watch / None]
- **Out of scope**: [explicit exclusions]
Present the structured requirements to the user and ask: "Are these requirements accurate? Should I proceed with planning the implementation?"