What problem does it solve? Developer agents often fail because story files lack context: wrong libraries, wrong file locations, missed regressions, and vague acceptance criteria. This Skill creates a complete, context-rich story file that gives the dev agent everything needed for correct implementation. ## Core Features & Use Cases - Story Auto-Discovery: Reads sprint-status.yaml to find the next backlog story, or accepts an explicit epic-story number like "1-2-user-auth". - Exhaustive Artifact Analysis: Loads epics, PRD, architecture, and UX documents (whole or sharded) plus previous story learnings and recent git history to build developer guardrails. - Quality Validation Checklist: Validates the generated story against a competitive review checklist that catches critical omissions before handoff, then updates sprint status to ready-for-dev. - Use Case: After sprint planning, run this workflow to turn the next backlog story into a fully-contextualized implementation guide with architecture compliance rules, library versions, and testing requirements. ## Quick Start Ask the agent to create the next story from the sprint backlog, or specify one directly such as "create story 2-4".
