bmad-create-story

Generate a YAML-frontmatter story file from planning artifacts and sprint data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a complete story file for a future development task, so the implementation agent has all the technical, architectural, and project context it needs without piecing details together manually.

Core Features & Use Cases

  • Automated story creation: Builds a dedicated story document from a structured template using epic, architecture, PRD, UX, sprint, and project context inputs.
  • Context aggregation and guardrails: Pulls in prior story learnings, repository patterns, architecture constraints, testing expectations, and technical research to reduce implementation mistakes.
  • Quality validation workflow: Reviews the generated story against a detailed checklist, identifies missing guidance, and supports interactive improvement before handoff to development.
  • Use Case: When a team is ready to implement the next backlog item, use this Skill to create a ready-for-dev story file that captures acceptance criteria, file targets, constraints, reuse opportunities, and validation notes.

Quick Start

Ask the agent to create the next story or create story 2-4 so it generates a ready-for-dev story document with full implementation 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 implementation-ready story briefs for sprint planning?

Creating implementation-ready story briefs involves building a dedicated story document from structured templates using epic, architecture, PRD, and sprint data. This provides the implementation agent with technical context, testing expectations, and validation notes for developer handoff.

How do I add architecture constraints and prior story context to backlog items?

Adding architecture constraints and prior story context to backlog items requires a context aggregation workflow that selectively loads project planning artifacts and repository patterns. This enriches the story brief with technical research and reuse opportunities to reduce implementation mistakes.

Does story generation work with YAML frontmatter for sprint status updates?

Story generation works with YAML-frontmatter-driven document creation to update sprint status. It selects the next backlog item from sprint tracking data, scopes it, and outputs a structured file ready for quality validation before development begins.

What is the best way to validate story quality before developer handoff?

Validating story quality before developer handoff is best achieved through a checklist-based quality control workflow. This reviews the generated story document against detailed criteria, identifies missing guidance, and supports interactive improvement before development begins.

Can I use automated story creation for large software delivery workflows?

Automated story creation is designed for software delivery workflows needing the next story selected, scoped, and enriched with architecture context. It manages backlogs by pulling prior story learnings, repository patterns, and technical research to reduce implementation mistakes.