bmad-create-story

Generate a complete BMAD story file with sprint status and artifact references.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-create-story-wizarck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/Wizarck/iguanatrader/tree/main/skills/bmad-create-story
Command: npx skills add https://github.com/Wizarck/iguanatrader --skill bmad-create-story-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating consistent, high-quality dev-story files is error-prone and time-consuming. This skill automates the generation of a complete, ready-for-dev story document that provides the developer with every required context, guardrail, artifact reference, and status linkage to eliminate misinterpretations and rework.

Core Features & Use Cases

  • Automated story scaffolding: Produces a ready-to-edit story file containing Epic/Story metadata, acceptance criteria, and developer notes.
  • Sprint-aware integration: Updates sprint-status and references planning/implementation artifacts to maintain traceability.
  • Guardrails and references: Includes architecture constraints, dependencies, and project-context references to prevent drift and duplication.
  • Use Case: When a user asks to "create the next story" or "create story [story identifier]", generate a complete, production-ready story with clear sections for Dev Notes, Project Structure, and Testing guidance.

Quick Start

Provide an epic/story identifier (for example 1-2-user-auth) or a path to the story docs and the system will generate a complete ready-for-dev story file and update sprint tracking.

Frequently Asked Questions about bmad-create-story

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

FAQPage Schema
How do I automate dev story creation for an LLM agent?

Automating dev story creation involves generating a complete, ready-for-dev story file that gives the LLM agent full context. This includes pulling from planning and implementation artifacts to embed metadata, acceptance criteria, and guardrails automatically.

What do I need to generate a ready-for-dev story file?

To generate a ready-for-dev story file, you need to provide an epic or story identifier, such as 1-2-user-auth, or a path to your story docs. The system then pulls project context and artifacts to produce the complete document.

How do I prevent context drift when creating development stories?

Preventing context drift during development story creation requires embedding architecture constraints, dependencies, and project-context references directly into the story file. These guardrails ensure the dev agent adheres to original project specifications.

Can I scaffold a production-ready story file in a single step?

Yes, you can scaffold a production-ready story file in a single step by providing a story identifier. The system outputs a complete document with sections for Dev Notes, Project Structure, and Testing guidance, clearly labeled for ready-for-dev activation.

Why does my dev agent misinterpret story requirements without guardrails?

A dev agent misinterprets story requirements without guardrails due to missing architecture constraints and prior story intelligence. Automating story generation eliminates this by embedding all required context and references directly into the file.