bmad-create-story

Create a self-contained story file with acceptance criteria and developer guidance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a dedicated story file that provides all the context, acceptance criteria, and operational guidance the dev agent needs to implement a story flawlessly. This reduces back-and-forth, prevents omissions, and accelerates delivery.

Core Features & Use Cases

  • Self-contained story file containing epic/story metadata, acceptance criteria, tasks, and developer guidance.
  • Context-rich guidance with guardrails, source hints, testing expectations, and architecture constraints to ensure correct implementation.
  • Use Case: When a user requests "create the next story" or "create story [identifier]", this Skill generates a ready-to-use story file for development.

Quick Start

Provide epic and story identifiers or let the workflow auto-create a ready-for-dev story file with complete guardrails.

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 dev-ready story file with complete context and acceptance criteria?

Yes, you can auto-create a ready-for-dev story file by letting the workflow extract content from epic and story identifiers. It aggregates planning artifacts and architecture references automatically.

What is a self-contained story file in agile development workflows?

A self-contained story file provides all the context, acceptance criteria, and operational guidance a developer needs. It ensures flawless implementation by embedding validation steps, testing expectations, and architecture constraints.

How do I prevent common developer mistakes when implementing agile stories?

Embedding guardrails, validation steps, and source hints into the story file prevents common mistakes. This provides context-rich guidance and testing expectations to ensure correct implementation.

Do I need sprint-planning outputs to create a complete story file?

You can use either sprint-planning outputs or direct epic and story identifiers to create a complete story file. The workflow aggregates content from available planning artifacts and architecture references.

What's the best way to structure developer guidance for deterministic implementation?

Structure developer guidance by encapsulating context, acceptance criteria, and architecture constraints into a dedicated story file. This reduces back-and-forth and prevents omissions during implementation.