bmad-create-story

Generate a ready-for-dev story specification from sprint and planning artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents developer mistakes by automatically generating a comprehensive, implementation-ready story file that pins requirements, architecture constraints, and guardrails to reduce omissions, regressions, and “it’s done” hallucinations.

Core Features & Use Cases

  • Discovers the correct next backlog story from sprint tracking (sprint-status) or user-provided epic/story identifiers, then positions it for implementation.
  • Loads and exhaustively analyzes planning and design artifacts (PRD/epics, architecture, and UX docs), plus prior story learnings and relevant git signals to maintain continuity.
  • Produces a developer master guide that enforces file-structure, architecture compliance, testing standards, and latest-tech diligence, then updates sprint status to ready-for-dev.

Quick Start

Use this skill when the user says create the next story, and it will generate the next ready-for-dev story file from your repo’s existing epics, architecture, and UX documents.

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 spec from backlog epics and architecture docs?

To generate a story spec, the system resolves workflow context from sprint tracking, analyzes your PRD, epics, architecture, and UX artifacts, then outputs a template-based story file with strict developer guardrails and transitions sprint status to ready-for-dev.

What is spec-driven story generation for developer agents?

Spec-driven story generation creates implementation-ready story files that pin requirements, architecture constraints, and guardrails to prevent developer omissions, regressions, and completion hallucinations during automated software delivery.

Can I target a specific epic or story identifier instead of the next backlog item?

Yes, you can explicitly provide epic or story identifiers to target a specific backlog item, or the system can automatically discover the correct next story by resolving context from your existing sprint tracking and planning artifacts.

Does story generation work with existing git history and prior sprint learnings?

Yes, the process loads and analyzes prior story learnings and relevant git signals when available, integrating this intelligence to maintain continuity and enforce architecture compliance across sequential sprint implementations.

What's the best way to enforce file-path conventions and architecture guardrails in story specs?

The generated story spec acts as a developer master guide that deterministically enforces file-structure rules, architecture compliance, testing standards, and latest-tech diligence through strict template-based output sections.

What planning artifacts are required to create an implementation-ready story file?

You need existing PRD or epic documents, architecture docs, and UX artifacts in your repository, plus sprint tracking data to enable exhaustive artifact analysis and accurate story positioning.