issues▌

Convert product requirements into independently-deliverable GitHub issues using vertical-slice architecture. \n \n Fetches PRD content from GitHub, analyzes the codebase context, and breaks requirements into thin vertical slices that span all integration layers end-to-end \n Distinguishes between HITL (human-in-the-loop, requiring decisions) and AFK (autonomous, mergeable without review) slices, preferring AFK where possible \n Presents proposed breakdown for user feedback on granularity, depend

Interactive QA session where users report bugs conversationally, and the agent files GitHub issues while exploring the codebase for context.

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.

Triage GitHub issues through a label-based state machine for efficient issue management.

Load all open issues from the current GitHub repository and save them as markdown files in the ./specs/issues/ directory.

This skill helps triage GitHub issues by routing issues, applying labels, and leaving first-line responses.

Create GitHub Issues automatically from implementation plan phases. \n \n Analyzes implementation plan files to identify phases and generates one issue per phase \n Uses feature_request.yml or chore_request.yml templates, with fallback to default issue format \n Checks for existing issues before creation to avoid duplicates, and updates existing issues when needed \n Includes phase details, requirements, and context in issue descriptions with appropriate labels \n

Automatically create GitHub issues for specification requirements not yet implemented in code. \n \n Analyzes specification files to extract all requirements, then checks codebase implementation status for each one \n Searches existing issues to prevent duplicates before creating new feature request issues \n Generates issues with requirement IDs, detailed descriptions, implementation guidance, and acceptance criteria \n Scans related specification files and code patterns to verify whether requi

Systematic workflow for identifying missing features, prioritizing them, and creating detailed GitHub issue specifications. \n \n Guides through five structured phases: project understanding, gap analysis, prioritization scoring, specification development, and issue creation \n Uses a quantitative priority matrix (User Impact × Strategic Alignment / Implementation Effort × Risk Level) to rank features objectively \n Includes work distribution optimization to maximize independent development stre

Create and manage Jira issues using the Jira REST API or MCP.