release-generate-stories

To generate user stories, provide the path to a release file containing a Features section. The system extracts each feature and produces one structured story file using a standard Gherkin template, without modifying the original release document.

Yes, agile story generation applies a Gherkin template to structure each feature with scenarios and acceptance criteria. This ensures derived stories maintain consistent formatting and traceability directly from the release documentation.

Generating stories from a release file does not overwrite or modify the original specs. The process reads the Features section and creates separate kebab-case story files, preserving the source release document entirely.

User story files are generated using kebab-case naming conventions to avoid collisions. This formatting standardizes the output structure and prevents file overwrites when deriving multiple stories from a single release.

The best way to structure acceptance criteria is using the story-gherkin-template.md asset. It automatically formats each generated user story with standard Gherkin scenarios, ensuring consistent behavioral definitions across the backlog.

You need a release document containing a dedicated Features section to trigger story generation. The process scans this specific structure to extract features and create corresponding individual story files.