release-generate-all-stories

To batch generate user stories from release notes, the Skill scans docs/specs/releases and outputs structured story files in docs/specs/stories. It processes releases in alphabetical order, applying a Gherkin template to enforce consistent naming and structure across all generated files.

Ensuring consistent Gherkin structure across story files requires using a single output template like assets/story-gherkin-template.md. The Skill applies this template to every generated file, maintaining uniform naming conventions and structural formatting automatically during batch processing.

Yes, you can automate story generation without overwriting existing files because the Skill honors idempotency rules. It supports configurable overwrite or skip behavior, ensuring non-destructive edits and deterministic output when regenerating stories from updated release notes.

This story generation tool works specifically with projects that have multiple releases. It batch processes every release note found in docs/specs/releases, generating a corresponding user story file for each feature while maintaining release references within the output documentation.

Before generating user stories in bulk, you need to set up assets/story-gherkin-template.md as your output template. This file acts as the single structural source, defining the Gherkin format and naming conventions applied to all stories written to docs/specs/stories.