story-generator

This Skill generates per-story markdown files by extracting S-XXX references from your epic. It organizes content into Block A for user stories and estimates, and Block B for technical scope, ensuring files are ready for spec, plan, and build phases.

The generated story documents use a two-block markdown structure. Block A captures the user story, acceptance criteria, and estimates for completeness, while Block B includes technical scope and data model considerations only when relevant.

You need to provide an epic containing S-XXX references and maintain a consistent slug structure within the docs/epics directory. This consistent epic slug structure is required to automatically extract references and generate the story files.

Yes, the generator enforces a validation workflow before writing any markdown files. It ensures open questions are resolved, verifies Figma URL presence, and performs a quality check to guarantee the generated stories are implementation-ready.

Yes, you can use this for Agile planning without technical details. The generator includes Block B content for technical scope only when relevant, ensuring Block A estimation content remains complete while preserving the overall epic context and constraints.

The best way to convert epic planning documents into development tasks is to automate the extraction of S-XXX references into per-story markdown files. This preserves epic context while enforcing validation workflows like Figma URL checks for reliable development handoff.