What problem does it solve? Starting work on a Jira ticket without a shared, unambiguous understanding of requirements leads to wrong assumptions, rework, and misaligned implementations. This Skill turns a raw Jira ticket into a developer-approved PRD by distilling the ticket and running a relentless clarifying interview before any planning or coding begins. ## Core Features & Use Cases - Ticket Distillation via Subagent: Fetches the Jira ticket through the Atlassian MCP and writes a clean summary (description, Implementation Plan and Testing Steps fields, substantive comments, flagged uncertainties) to .ai/<TICKET>/jira-summary.md. - Adaptive Clarifying Interview: Seeds and works down an Open Questions list, surfacing both ambiguities and unstated gaps (error paths, edge inputs, affected surfaces) without ever guessing answers. - Gated PRD Deliverable: Produces a structured prd.md (Summary, Problem, Goals & Non-Goals, numbered Requirements, Scope, Acceptance Criteria, Open Questions) that is only marked Approved after explicit developer acceptance. - Use Case: You receive ticket PHG-418 and say "let's start PHG-418". The Skill fetches and distills the ticket, interviews you on every consequential ambiguity, and delivers an approved PRD ready for the downstream planning skill. ## Quick Start Ask the AI to start work on a Jira ticket by saying something like "let's start PROJ-123" and it will fetch the ticket, interview you, and produce an approved PRD.
