bmad-create-story

Generate comprehensive story files from project artifacts and architectural constraints.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-create-story-marcmontecalvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-create-story
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-create-story-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates developer errors, omissions, and implementation disasters by generating comprehensive, context-aware story files that serve as a master guide for development agents.

Core Features & Use Cases

  • Exhaustive Context Analysis: Automatically synthesizes requirements from PRDs, architecture documents, and epics to ensure the developer has a complete picture.
  • Disaster Prevention: Identifies potential regressions, architectural conflicts, and missing dependencies before development begins.
  • Use Case: When starting a new feature, use this Skill to ingest all project documentation and previous sprint learnings, resulting in a ready-for-dev story file that prevents wheel-reinvention and ensures architectural compliance.

Quick Start

Use the bmad-create-story skill to generate the implementation context for the next backlog story in the current sprint.

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 story context for sprint planning and development agents?

To generate story context, synthesize project artifacts like PRDs and architectural documents into a comprehensive file. This ensures development agents receive exhaustive context and technical constraints to prevent implementation regressions.

What is automated story context generation and why do I need it?

Automated story context generation synthesizes project artifacts and architectural constraints into a master guide for development agents. You need it to eliminate developer errors, omissions, and implementation disasters before coding begins.

How do I prevent architectural regressions when starting a new feature?

Prevent architectural regressions by generating ready-for-dev story files that ingest project documentation and previous sprint learnings. This identifies potential conflicts and missing dependencies before development begins.

Do I need specific project documentation to generate accurate sprint stories?

Yes, you need access to project-root, sprint-status, and planning documentation. Synthesizing these architectural constraints and requirements ensures technical accuracy and maintains consistency across the development lifecycle.

Can I use sprint planning artifacts to automatically prepare implementation context?

Yes, you can ingest sprint planning artifacts and epics to automatically synthesize requirements. This produces an optimized story file that prevents wheel-reinvention and ensures architectural compliance for development agents.

What's the best way to synthesize PRDs and architecture documents for dev agents?

The best way to synthesize PRDs and architecture documents is through exhaustive context analysis. This automatically extracts requirements to ensure the developer has a complete picture and prevents potential architectural conflicts.