bmad-create-story

To generate a story context document from epics and planning artifacts, the skill analyzes core artifacts, architecture, and technical specifics to create an intent-and-constraint guide for development agents. It automates this by orchestrating a 6-step process that analyzes sprint data and documentation to produce ready-to-use implementation guides.

A story context document serves as an intent-and-constraint guide for development agents within an implementation workflow. It streamlines development by consolidating analyzed epics, architecture reviews, and technical research into a single directive document that agents use to execute the implementation phase correctly.

Yes, you can automate story generation by triggering the skill to create the next story for implementation. It analyzes existing sprint data, core artifacts, and planning documentation to automatically produce a story context document, while updating sprint status as part of its 6-step process.

Yes, a workflow engine and configuration are required to execute the automated story generation process. The engine drives the 6-step process, which includes artifact analysis, architecture review, technical research, validation, and sprint status updates to produce the final story context document.

The best way to prepare for automated story generation is ensuring your core artifacts, architecture documents, and technical specifics are complete and accessible. The skill analyzes these planning artifacts during its workflow to extract the intent and constraints needed to produce the story context document.

Your story generation workflow requires validation and sprint status updates to ensure the produced story context document is accurate and properly tracked within the implementation workflow. These steps are part of the 6-step process that validates the analyzed artifacts and keeps sprint data current before the document is finalized.