bmad-create-story

Name: bmad-create-story
Availability: InStock
Author: enigmaicon-eng

Generate implementation-ready story files from workflow configuration and artifacts.

1|Updated May 16, 2026

Search Tags:#workflow orchestration #architecture compliance #story generation #artifact discovery #epics and acceptance criteria #developer guardrails #sprint status automation

Ready to run

npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-create-story-enigmaicon-eng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/bmm-skills/4-implementation/bmad-create-story
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-create-story-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents LLM developer mistakes by generating a comprehensive, implementation-ready story file with exhaustive context, guardrails, and workflow-driven artifact discovery.

Core Features & Use Cases

Workflow-resolved story setup: Determines the target epic/story either from user input or sprint-status backlog auto-discovery, then computes the story key and paths.
Exhaustive artifact loading & analysis: Discovers and loads PRD, architecture, UX, and epics content and extracts story foundation, cross-story context, and architecture constraints.
Dev-safe implementation guidance: Produces a fully structured “ultimate story” document using templates, including architecture compliance, testing requirements, file structure notes, and developer guardrails.

Quick Start

Ask the agent to create the next story by running bmad-create-story with your epic-story selector (or with an existing sprint-status.yaml) so it can generate a ready-for-dev story file automatically.

Frequently Asked Questions about bmad-create-story

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

FAQPage Schema

How do I create implementation-ready developer stories with architecture compliance and full context?▼

Story generation prevents LLM developer mistakes by producing a comprehensive story file with exhaustive context, dev guardrails, and workflow-driven artifact discovery. It loads PRD, architecture, UX, and epics content to extract story foundation and architecture constraints.

How do I generate a story file from a sprint-status backlog automatically?▼

To generate a story file from sprint-status.yaml, run customization resolution and story parsing to auto-discover the target epic/story. The workflow computes story paths, loads required artifacts, applies template-based document generation, and updates sprint status automatically.

Can I use epic and story tracking workflows for enterprise development with PRD and architecture documents?▼

Epic and story tracking workflows apply to enterprise development environments using PRD, architecture, and UX documents with sprint-status-driven backlog selection. The workflow resolves target epics from user input or auto-discovery and extracts cross-story context and architecture constraints.

What developer guardrails and testing requirements are included in a generated story file?▼

Developer guardrails in a generated story file cover architecture compliance, testing requirements, file structure notes, and dev-safe implementation guidance. The ultimate story document uses templates to structure these elements, ensuring architecture constraints and cross-story context are enforced.

What's the best way to discover required artifacts for workflow orchestration in story generation?▼

The best way to discover required artifacts for workflow orchestration is through exhaustive input loading of PRD, architecture, UX, and epics content. This workflow extracts story foundation, cross-story context, and architecture constraints to produce dev-safe implementation guidance.

Do I need a sprint-status.yaml file to run story generation for my epic and acceptance criteria?▼

A sprint-status.yaml file is not strictly required to run story generation for epics and acceptance criteria. The workflow can determine the target epic/story from direct user input via an epic-story selector or through sprint-status backlog auto-discovery.