gaia-create-story

Story documentation requires YAML frontmatter for metadata, Given/When/Then statements for acceptance criteria, and sprint-state registration for backlog alignment. This format maintains structure and traceability across implementation artifacts.

Generating sprint stories from planning documentation is best handled by extracting epics from a planning markdown file and writing structured implementation artifacts. This enforces consistent frontmatter, acceptance criteria, and sprint-state registration.

Yes, generating story artifacts requires a specific planning file structure. You need an input file containing high-level epics and stories to extract from, ensuring the output implementation artifact receives all required YAML frontmatter fields and acceptance criteria.

Sprint-state registration works by registering the newly created story status via bundled tooling during artifact generation. This maintains backlog and sprint alignment by linking the formatted implementation artifact directly to the active sprint state.

Yes, you can use a bundled template to enforce consistent story structure and acceptance criteria. This guarantees every generated implementation artifact includes required YAML frontmatter fields and Given/When/Then statements for traceability.