bmad-development-execution

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Development Execution Skill

开发执行Skill

When to Invoke

调用时机

Automatically activate when user:

Says "Implement story X", "Start coding", "Develop this"
Asks "Write the code", "Let's code", "Build [feature]"
Mentions "implement", "code", "develop"
Story file ready (Phase 4)
Uses words like: implement, code, develop, build, program, coding

Specific trigger phrases:

"Implement story [X]"
"Start coding [feature]"
"Develop this story"
"Let's code"
"Write the implementation"
"Build [feature]"

Prerequisites:

Story file exists (from bmad-story-planning)
Architecture patterns defined

Do NOT invoke when:

No story file (use bmad-story-planning first)
Planning needed (use bmad-product-planning first)
Architecture not defined (use bmad-architecture-design first)

当用户出现以下情况时自动激活：

说出“Implement story X”、“开始编码”、“开发这个需求”
询问“编写代码”、“我们来编码吧”、“构建[功能]”
提到“implement”、“code”、“develop”
故事文件已准备就绪（第4阶段）
使用以下词汇：implement、code、develop、build、program、coding

特定触发短语：

“Implement story [X]”
“Start coding [feature]”
“Develop this story”
“Let's code”
“Write the implementation”
“Build [feature]”

前置条件：

故事文件已存在（来自bmad-story-planning）
架构模式已定义

请勿调用的情况：

无故事文件（请先使用bmad-story-planning）
需要进行规划（请先使用bmad-product-planning）
架构未定义（请先使用bmad-architecture-design）

Mission

任务目标

Implement approved stories end-to-end, maintaining transparency, testing discipline, and traceability back to requirements and architecture decisions.

端到端实现已获批的需求故事，保持透明度、测试规范性，并确保可追溯至需求和架构决策。

Inputs Required

所需输入

story: developer-ready story file from delivery-planning skill
architecture_refs: relevant sections of ARCHITECTURE.md or component notes
ux_guidance: UX specs or validations tied to the story
quality_plan: scenarios or gates supplied by quality-assurance skill

story：来自delivery-planning skill的开发就绪型故事文件
architecture_refs：ARCHITECTURE.md的相关章节或组件说明
ux_guidance：与该故事相关的UX规范或验证要求
quality_plan：由quality-assurance skill提供的场景或质量关卡

Outputs

输出成果

Code diffs and test results captured in the working repository
Updated story file (Dev Agent Record, status transitions, learnings)
implementation-notes.md - Development summary (generated from
```
assets/implementation-notes-template.md.template
```
)
Summary of changes, tests, and outstanding risks for stakeholders

Template location:

.claude/skills/bmad-development-execution/assets/implementation-notes-template.md.template

代码差异和测试结果已捕获至工作仓库
更新后的故事文件（Dev Agent记录、状态转换、经验总结）
implementation-notes.md - 开发总结（基于
```
assets/implementation-notes-template.md.template
```
生成）
向干系人提供变更、测试情况及未解决风险的总结

模板位置：

.claude/skills/bmad-development-execution/assets/implementation-notes-template.md.template

Process

执行流程

Confirm prerequisites via
```
CHECKLIST.md
```
and restate story scope.
Plan implementation steps, identifying affected files and tests.
Apply small, reviewable code changes with explanations and references.
Execute required test suites and capture command output verbatim.
Update story documentation, including Dev Agent Record and status.
Summarize work, highlight follow-ups, and notify orchestrator for next steps.

通过
```
CHECKLIST.md
```
确认前置条件，并重述故事范围。
规划实现步骤，确定受影响的文件和测试内容。
提交小型、便于评审的代码变更，并附上说明和参考依据。
执行所需的测试套件，逐字记录命令输出。
更新故事文档，包括Dev Agent记录和状态。
总结工作内容，突出后续待办事项，并通知编排器进入下一步。

Quality Gates

质量关卡

All items in

CHECKLIST.md

must pass before code is considered complete. Never mark a story done without full testing evidence.

在代码被视为完成前，

CHECKLIST.md

中的所有项必须通过。未提供完整测试证据时，绝不能标记故事为已完成。

Error Handling

错误处理

If prerequisites or environments are missing:

Halt implementation, document the specific blocker, and notify orchestrator.
Provide recommended remediation steps (e.g., refresh artifacts, fix failing baseline tests).
Avoid speculative changes; keep diffs scoped to the approved story.

若缺少前置条件或环境异常：

暂停实现，记录具体阻塞问题，并通知编排器。
提供建议的修复步骤（例如：刷新工件、修复失败的基线测试）。
避免进行推测性变更；保持代码差异仅局限于已获批的故事范围。