beads-implement

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Beads Implement

Beads 实现

Use this skill to execute work from a bead or epic id with minimal back-and-forth.

使用此skill以最少的来回沟通，通过bead或epic ID执行工作。

Workflow

工作流程

Prime bd (always)
- Run
```
bd prime
```
  first. It is the fastest way to get the current "how to start this bead" primer.
- If
```
bd prime
```
  is unavailable or confusing, consult the official Beads GitHub repo at
```
https://github.com/steveyegge/beads
```
  for workflow guidance.
Open the bead
- Use
```
bd show <id>
```
  and read the title, description, acceptance criteria, and dependencies.
- If required info is missing or a dependency blocks progress, ask a single targeted question and wait.
Start work in Beads
- Mark the bead
```
in_progress
```
  if your bd workflow supports it (check
```
bd prime
```
  /
```
bd update --help
```
  ).
- Add a short note on your intended approach if the bead is ambiguous.
Create a brief to-do list
- At the start of execution, create a short to-do list of the tasks/sub-tasks you plan to complete and update it as you go.
Decide scope
- If the bead is a single task, implement it directly.
- If the bead is an epic, identify all sub-tasks and implement them in dependency order.
Delegate aggressively (use sub-agents)
- If the work splits cleanly, spawn sub-agents instead of serializing everything in your own head.
- Good sub-agent targets: repo exploration, API/library doc lookup, reproducer creation, test strategy, narrow refactors with a clear file list.
- Give each sub-agent explicit ownership (files + expected output), and merge their results.
Implement, commit, and write notes (repeat per task/sub-task)
- Implement, run relevant checks/tests, then commit.
- One commit per task/sub-task.
- Commit message: include the bead id in the subject.
- Commit body: write real notes (what changed, why, tests run, follow-ups/risk).
- After the commit, add the same notes to the bead (so the bead survives compaction and future handoffs). Use
```
bd update <id>
```
  and whatever flag/subcommand your bd version uses for notes (check
```
bd prime
```
  ).
Minimal commit template:
text
```
<BEAD-ID>: <imperative summary>

Why:
- ...

What:
- ...

Tests:
- ...

Notes/Risks:
- ...
```
Communicate only when needed
- Do not interrupt the user while work is progressing.
- Only pause to ask for help when blocked, when information is missing, or when a meaningful decision is required.
Close out
- When complete, close the bead (or mark it done) with a clear reason.
- After closing, run the session-end sync step recommended by
```
bd prime
```
  for your installed
```
bd
```
  version.
- If
```
bd prime
```
  is unavailable, verify the session-close command in the official Beads GitHub repo at
```
https://github.com/steveyegge/beads
```
  before ending the session.
Report progress

Provide a concise summary of completed tasks, commits made, and what remains (if anything).

初始化bd（必须执行）
- 首先运行
```
bd prime
```
  。这是获取当前"如何启动该bead"引导信息的最快方式。
- 如果
```
bd prime
```
  不可用或内容令人困惑，请访问官方Beads GitHub仓库
```
https://github.com/steveyegge/beads
```
  获取工作流指导。
打开bead
- 使用
```
bd show <id>
```
  并阅读标题、描述、验收标准和依赖项。
- 如果缺少必要信息或依赖项阻碍了进度，请提出一个针对性的问题并等待回复。
在Beads中开始工作
- 如果你的bd工作流支持（查看
```
bd prime
```
  /
```
bd update --help
```
  ），将该bead标记为
```
in_progress
```
  。
- 如果bead的内容不明确，请添加一段关于你计划采用的方法的简短说明。
创建简短的待办事项列表
- 在开始执行前，创建一个简短的待办事项列表，列出你计划完成的任务/子任务，并在执行过程中更新该列表。
确定范围
- 如果bead是单个任务，直接实现它。
- 如果bead是epic，识别所有子任务并按照依赖顺序实现它们。
积极委派任务（使用子Agent）
- 如果工作可以清晰拆分，请生成子Agent来处理，而非全部由自己串行处理。
- 适合子Agent处理的工作：仓库探索、API/库文档查阅、复现案例创建、测试策略制定、针对明确文件列表的小规模重构。
- 为每个子Agent明确分配职责（文件范围+预期输出），并合并它们的工作成果。
实现、提交并撰写说明（每个任务/子任务重复此步骤）
- 实现功能，运行相关检查/测试，然后提交。
- 每个任务/子任务对应一次提交。
- 提交信息：主题中包含bead ID。
- 提交正文：撰写真实说明（修改了什么、原因、运行的测试、后续工作/风险）。
- 提交完成后，将相同的说明添加到该bead中（确保bead在压缩和未来交接时仍能保留信息）。使用
```
bd update <id>
```
  以及你的bd版本用于添加说明的参数/子命令（查看
```
bd prime
```
  ）。
最简提交模板：
text
```
<BEAD-ID>: <命令式摘要>

原因：
- ...

修改内容：
- ...

测试：
- ...

说明/风险：
- ...
```
仅在必要时沟通
- 工作进展过程中不要打扰用户。
- 仅在遇到阻塞、缺少信息或需要做出重要决策时才暂停并寻求帮助。
收尾工作
- 完成后，关闭该bead（或标记为已完成）并附上明确的原因。
- 关闭后，运行
```
bd prime
```
  推荐的针对你所安装的bd版本的会话结束同步步骤。
- 如果
```
bd prime
```
  不可用，请在结束会话前到官方Beads GitHub仓库
```
https://github.com/steveyegge/beads
```
  确认会话关闭命令。
汇报进度

提供已完成任务、已提交的内容以及剩余工作（如果有）的简明摘要。