bmad-create-story

Generate a story file with guardrails from epic and architecture context.

3|2|Updated Mar 29, 2024
One-click install
npx skills add https://github.com/josemariafs/MVTools --skill bmad-create-story-josemariafs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/josemariafs/MVTools/tree/main/.cursor/skills/bmad-create-story
Command: npx skills add https://github.com/josemariafs/MVTools --skill bmad-create-story-josemariafs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a comprehensive, ready-to-implement story file by aggregating epic, PRD, architecture, and prior story intelligence into a single, coherent developer guide with guardrails and references.

Core Features & Use Cases

  • Automated Story Synthesis: Generates a complete story document that captures user needs, acceptance criteria, technical requirements, and guardrails.
  • Contextual Intelligence: Incorporates previous story learnings, architecture constraints, and git history to inform implementation and reuse patterns.
  • Project-Context References: Embeds cross-document references to epics, PRD, and architecture to ensure alignment and traceability.

Quick Start

Tell the system the epic_num, story_num, and story_title to generate the full, ready-for-dev story file.

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 developer story file from epic and architecture context?

To generate a developer story file, you provide the epic_num, story_num, and story_title. The system synthesizes architecture constraints and prior story intelligence into a ready-for-dev storyboard with embedded guardrails.

Does automated story synthesis include cross-document references to PRDs and architecture docs?

Automated story synthesis embeds cross-document references to epics, PRDs, and architecture documents. This ensures strict alignment and traceability across the entire project lifecycle during story file generation.

Can I add dev guardrails and testing considerations directly into a generated story file?

Generating a story file embeds cross-cutting dev guardrails, testing, and deployment considerations directly into the documentation. This prevents common mistakes by enforcing alignment with project patterns before implementation begins.

What is the best way to create a ready-for-dev storyboard that aggregates PRD and prior story intelligence?

The best way to create a ready-for-dev storyboard is aggregating epic, PRD, architecture, and prior story intelligence into a single coherent guide. This produces comprehensive documentation with user needs and technical requirements.

Why does story generation require architecture analysis and epic context?

Story generation requires architecture analysis and epic context to ensure the resulting developer guide aligns with project patterns. Without these inputs, the generated story cannot accurately reuse existing solutions or enforce contextual guardrails.