create-stories

To generate sprint-ready user stories, the Skill decomposes accepted epics by creating one story-NNN Markdown file per eligible accepted functional requirement, lifting acceptance criteria verbatim from the approved elicitation document.

Requirements traceability is maintained by mapping one user story per eligible accepted functional requirement and rebuilding a comprehensive stories index that includes a coverage matrix and aggregated open questions.

Yes, you can refine pending stories in place while protecting accepted or rejected stories; the Skill preserves immutable fields for finalized stories by only appending review notes to them.

Yes, generating user stories requires both Accepted Epics in the artifacts directory and an Approved elicitation document to ensure acceptance criteria are lifted verbatim for consistent definition of done.

During artifact generation, acceptance criteria are lifted verbatim from the elicitation document, while AI provisional story points are computed automatically and open questions are aggregated with severity-based review blocking rules.

Pending or rejected epics remain untouched during user story generation; the Skill exclusively targets Accepted Epics to ensure only eligible functional requirements are decomposed into sprint-ready stories.