bmad-create-story

Name: bmad-create-story
Availability: InStock
Author: skyoxu

Generate a ready-for-dev story context document from epic and architecture inputs.

Updated Nov 6, 2025

Search Tags:#documentation #guardrails #project-management #architecture-analysis #story-generation #epic-workflow #dev-automation

Ready to run

npx skills add https://github.com/skyoxu/godotgame --skill bmad-create-story-skyoxu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/bmad-create-story
Command: npx skills add https://github.com/skyoxu/godotgame --skill bmad-create-story-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, automated method to generate a complete story context document for software development, ensuring developers have a precise, ready-to-use guide that reduces misinterpretations and rework.

Core Features & Use Cases

Self-contained story generation: Produces a ready-for-dev narrative with epic, architecture, and prior-story insights.
Guardrails and best practices: Embeds developer guardrails, validation steps, and references to ensure correct implementation.
Cross-artifact synthesis: Aggregates inputs from epics, PRDs, architecture docs, and previous stories to maintain consistency across delivery.

Quick Start

Provide epic and story identifiers to generate a ready-for-dev story file with full context.

Frequently Asked Questions about bmad-create-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a ready-for-dev story context document from existing project artifacts?▼

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.

What is the best way to enforce developer guardrails and reuse patterns during story generation?▼

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.

How do I automate epic workflow planning and ensure developers have full technical context?▼

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.

Can I use prior-story intelligence to maintain consistency when creating new development stories?▼

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.

Do I need specific epic and story identifiers to start automated story generation?▼

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.