bmad-create-story

Generate a development-ready story file from epic and story inputs.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-create-story-clovernguyen1010-ship-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/_bmad/bmm/workflows/4-implementation/bmad-create-story
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill bmad-create-story-clovernguyen1010-ship-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a comprehensive, ready-for-dev story file that provides the dev agent with complete context, guardrails, and references to ensure flawless implementation.

Core Features & Use Cases

  • Generates a complete story skeleton from epic/story inputs, embedding user story context, acceptance criteria, and required references.
  • Integrates guardrails, architecture cues, and learning from previous stories to prevent repeated mistakes and foster consistency.
  • Use Case: When a user requests to "create the next story" or "create story [story identifier]," the workflow produces a production-ready story document.

Quick Start

Provide the epic and story identifiers (e.g., 1-2-user-auth) and run the create-story workflow to generate a ready-for-dev story file.

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 from epic inputs?

Generate a dev-ready story file by providing the epic and story identifiers, such as 1-2-user-auth, and running the workflow to output a complete story skeleton with technical requirements, code structure guidelines, and testing expectations.

What is a dev-ready story file and what context does it include?

A dev-ready story file is a comprehensive document embedding user story context, acceptance criteria, architecture cues, and guardrails to prevent repeated mistakes, ensuring a development agent has complete context for flawless implementation.

How do guardrails improve development story generation?

Guardrails improve development story generation by integrating architecture cues and learnings from previous stories into the new story file, preventing repeated mistakes and fostering consistency across the implementation process.

Can I automate story generation for the next story in an epic?

Yes, you can automate story generation by requesting the workflow to create the next story or specifying a story identifier, which produces a production-ready story document with references to planning artifacts.

What do I need to create a story with automated guardrails and architecture cues?

You need to provide the epic and story identifiers to create a story with automated guardrails and architecture cues, satisfying requirements for a ready-for-dev document without additional dependencies.