bmad-create-story

To generate a ready-for-dev story context document, this Skill extracts and consolidates epic, architecture, and prior-story intelligence into a self-contained guide. It aggregates inputs from PRDs and previous stories to maintain consistency across delivery.

The best way to enforce developer guardrails during story generation is to synthesize architecture docs and prior-story insights automatically. This workflow embeds validation steps and best practices directly into the generated story context to prevent rework.

Automating epic workflow planning requires extracting architecture analysis and epic intelligence to produce a self-contained narrative. This ensures developers receive precise technical considerations and full context for implementation without manual aggregation.

Yes, you can use prior-story intelligence to maintain consistency by cross-referencing previous story outputs during generation. This Skill aggregates prior delivery artifacts to enforce reuse patterns and reduce misinterpretations in new stories.

Yes, you need to provide specific epic and story identifiers to start automated story generation. Supplying these identifiers allows the workflow to extract the correct architecture and project-management artifacts to output a ready-for-dev file.