What problem does it solve? Developer agents often fail because story files lack context: wrong libraries, wrong file locations, missed regressions, and vague requirements. This Skill creates a complete, self-contained story file that gives the dev agent everything needed for correct implementation. ## Core Features & Use Cases - Automatic Story Discovery: Reads sprint-status.yaml to find the next backlog story, or accepts an explicit epic-story identifier like "2-4". - Exhaustive Context Extraction: Analyzes epics, GDD, architecture, UX docs, project-context.md, previous story learnings, and git history to build developer guardrails. - Quality Validation: Validates the generated story against a checklist that hunts for missing requirements, regressions risks, and LLM-optimization issues before marking it ready-for-dev. - Use Case: After sprint planning, say "create the next story" and the Skill produces a story file with acceptance criteria, architecture compliance rules, library versions, file structure requirements, and testing standards, then updates sprint status to ready-for-dev. ## Quick Start Ask the agent to create the next story from the sprint backlog, or specify a story like "create story 2-4" to generate its implementation file.
