refining-ios-requirements

Analyzes Jira and Confluence tickets into structured implementation-ready requirements for Bitwarden iOS development.

680|154|Updated Jul 14, 2023
One-click install
npx skills add https://github.com/bitwarden/ios --skill refining-ios-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refining-ios-requirements
Source: https://github.com/bitwarden/ios/tree/main/.claude/skills/refining-ios-requirements
Command: npx skills add https://github.com/bitwarden/ios --skill refining-ios-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about refining-ios-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refine a Jira ticket before starting iOS development?

Provide the ticket ID or URL and the Skill fetches it via the Bitwarden Atlassian MCP tools, then extracts core functionality, acceptance criteria, dependencies, and out-of-scope items into a structured requirements document.

What is gap analysis for software requirements?

Gap analysis identifies requirements the ticket author missed, such as network error handling, multi-account edge cases, locked vault states, app extension memory limits, offline behavior, and VoiceOver accessibility support.

Does this work with Confluence pages as well as Jira tickets?

Yes, it fetches Confluence specs using the get_confluence_page MCP tool alongside Jira issue and comment retrieval. If no ticket is available, it can also work from a plain-text description of the requirements.

How does it determine which Bitwarden iOS app is affected?

It reads the Architecture Structure section of Docs/Architecture.md for the canonical domain list, then classifies the work as BitwardenShared (Password Manager), AuthenticatorShared (Authenticator), or both, including affected extensions like AutoFill or Watch.

When should I not use ticket refinement before coding?

Skip it for trivial changes with obvious scope, such as typo fixes or dependency bumps. The structured analysis adds the most value for features touching multiple domains, extensions, or account states where unstated edge cases are likely.