Back to Details

bmad-story-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Delivery Planning Skill

交付规划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
当用户进行以下操作时自动激活：
  • 说出“拆分为用户故事”、“创建用户故事”
  • 询问“开发者任务？”、“用户故事拆解？”
  • 提及“用户故事”、“待办事项（backlog）”、“Sprint规划”
  • Epic与架构已就绪（第4阶段）
  • 使用以下词汇：story、stories、backlog、sprint、breakdown、tasks
特定触发短语：
  • “将这个拆分为用户故事”
  • “创建用户故事”
  • “针对[Epic]的用户故事拆解”
  • “开发者就绪任务”
  • “待办事项规划”
  • “Sprint用户故事”
前置条件：
  • 已存在Epic（来自bmad-product-planning）
  • 架构已定义
请勿触发的场景：
  • 尚未创建Epic（请先使用bmad-product-planning）
  • 已存在用户故事（请使用bmad-development-execution）
  • 无需用户故事结构的简单任务

Mission

核心目标

Transform epics and architecture decisions into developer-ready story packages, including acceptance criteria, dependencies, and delivery signals.
将Epic与架构决策转化为开发者就绪的用户故事包，包含验收标准、依赖关系和交付信号。

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
  • epics：来自product-requirements skill的最新epics.md文件
  • architecture：架构决策输出与约束规则
  • ux_assets：相关的带注释线框图或UX说明
  • sprint_status：当前交付节奏与产能信息

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
  • 使用
    assets/story-template.md.template
    创建用户故事Markdown文件
  • 更新待办事项摘要，突出排序、依赖关系与阻塞项
  • 推荐接下来可激活用于开发执行的用户故事

Process

流程步骤

  1. Confirm readiness by running 
    CHECKLIST.md
    and ensuring prerequisite artifacts exist.
  2. Prioritize epics/stories based on value, dependencies, and risk.
  3. Draft or update story files, capturing acceptance criteria, prerequisites, and test hooks.
  4. Use 
    scripts/create_story.py
    when structured JSON is provided; otherwise author manually with template guidance.
  5. Document sprint updates and communicate next-step recommendations to orchestrator and stakeholders.
  1. 运行
    CHECKLIST.md
    确认就绪状态，确保所有前置工件已存在。
  2. 根据价值、依赖关系和风险对Epic/用户故事进行优先级排序。
  3. 草拟或更新用户故事文件，记录验收标准、前置条件和测试钩子。
  4. 若提供结构化JSON，使用
    scripts/create_story.py
    生成；否则根据模板手动编写。
  5. 记录Sprint更新，并向编排器与相关方传达下一步建议。

Quality Gates

质量关卡

CHECKLIST.md
must pass before handing off stories. Every story must align with architecture decisions and cite upstream references.
在移交用户故事前必须通过
CHECKLIST.md
检查。每个用户故事必须与架构决策保持一致，并引用上游参考资料。

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.
若前置条件缺失或存在冲突：
  • 识别缺失的工件或决策，以及其为何会阻碍用户故事创建。
  • 转至负责的skill（架构、UX、product-requirements）以获取澄清。
  • 仅当已有就绪的用户故事时，才建议替代的待办事项。