Agent Skills › bacoco/BMad-Skills › bmad-story-planning

bmad-story-planning

GitHub

将史诗拆解为开发者就绪的故事包，包含验收标准、依赖和交付信号。适用于敏捷开发中的用户故事拆分、Sprint 规划及积压需求管理，确保故事与架构决策一致。

.claude/skills/bmad-story-planning/SKILL.md bacoco/BMad-Skills

Trigger Scenarios

Break into stories Create user stories Story breakdown for [epic] Developer-ready tasks Backlog planning Sprint stories

Install

npx skills add bacoco/BMad-Skills --skill bmad-story-planning -g -y

More Options

Non-standard path

npx skills add https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/bmad-story-planning -g -y

Use without installing

npx skills use bacoco/BMad-Skills@bmad-story-planning

指定 Agent (Claude Code)

npx skills add bacoco/BMad-Skills --skill bmad-story-planning -a claude-code -g -y

安装 repo 全部 skill

npx skills add bacoco/BMad-Skills --all -g -y

预览 repo 内 skill

npx skills add bacoco/BMad-Skills --list

SKILL.md

Frontmatter

{
    "name": "bmad-story-planning",
    "metadata": {
        "outputs": [
            "user-stories",
            "story-files",
            "acceptance-criteria"
        ],
        "triggers": {
            "keywords": [
                "story",
                "stories",
                "epic",
                "breakdown",
                "task",
                "backlog",
                "sprint"
            ],
            "patterns": [
                "break into stories",
                "create user stories",
                "story breakdown",
                "developer tasks"
            ]
        },
        "auto-invoke": true,
        "capabilities": [
            "story-breakdown",
            "epic-splitting",
            "task-definition",
            "backlog-creation"
        ],
        "prerequisites": [
            "product-requirements-document",
            "architecture-decisions"
        ]
    },
    "description": "Breaks epics into developer stories.",
    "allowed-tools": [
        "Read",
        "Write",
        "Grep"
    ]
}

Delivery Planning Skill

When to Invoke

Automatically activate when user:

Says "Break into stories", "Create user stories"
Asks "Developer tasks?", "Story breakdown?"
Mentions "stories", "backlog", "sprint planning"
Epics and architecture ready (Phase 4)
Uses words like: story, stories, backlog, sprint, breakdown, tasks

Specific trigger phrases:

"Break this into stories"
"Create user stories"
"Story breakdown for [epic]"
"Developer-ready tasks"
"Backlog planning"
"Sprint stories"

Prerequisites:

Epics exist (from bmad-product-planning)
Architecture defined

Do NOT invoke when:

No epics yet (use bmad-product-planning first)
Stories already exist (use bmad-development-execution)
Simple task that doesn't need story structure

Mission

Transform epics and architecture decisions into developer-ready story packages, including acceptance criteria, dependencies, and delivery signals.

Inputs Required

epics: latest epics.md from product-requirements skill
architecture: decision architecture outputs and guardrails
ux_assets: annotated wireframes or UX notes when relevant
sprint_status: current delivery cadence and capacity information

Outputs

Story markdown files created using assets/story-template.md.template
Updated backlog summary highlighting sequencing, dependencies, and blockers
Recommendations for next stories to activate for development-execution

Process

Confirm readiness by running CHECKLIST.md and ensuring prerequisite artifacts exist.
Prioritize epics/stories based on value, dependencies, and risk.
Draft or update story files, capturing acceptance criteria, prerequisites, and test hooks.
Use scripts/create_story.py when structured JSON is provided; otherwise author manually with template guidance.
Document sprint updates and communicate next-step recommendations to orchestrator and stakeholders.

Quality Gates

CHECKLIST.md must pass before handing off stories. Every story must align with architecture decisions and cite upstream references.

Error Handling

If prerequisites are missing or conflicting:

Identify the missing artifact or decision and why it blocks story creation.
Route back to the responsible skill (architecture, UX, product-requirements) for clarification.
Suggest alternative backlog items only when ready stories already exist.