子代理驱动开发

人工智能 社区

技能解读

subagent-driven-development 把「按计划干」这件事拆成「主 agent 调度 + 每条任务一个全新 subagent + 每条任务后两阶段 review」。关键约束:subagent 永远不继承你的对话历史,你必须给它精确剪好的 context。

设计思路

主 agent 做调度(拿计划、分任务、收 review、推进进度),subagent 做执行(fresh context、就这一条任务的 prompt、写代码、跑测试)。每条任务一收尾就走两阶段 review:先 spec 合规——做的是不是计划要求的;再 code quality——实现质量怎么样。两轴顺序固定:先 spec 后 code,避免在「实现得很漂亮但根本不是要的」上浪费时间。

连续执行

作者非常严厉地要求不要在任务之间停下来跟人 check-in。"Should I continue?" 这种 prompt 是在浪费用户时间——他叫你执行计划,那就执行。只有三种情况停:① BLOCKED 你解不开;② 真正阻塞推进的歧义;③ 所有任务完成。

适合

  • 已经有实现计划(写好了 writing-plans / request-refactor-plan)
  • 任务之间相对独立、不强耦合
  • 你想留在当前 session(如果想换并行 session,用 executing-plans)

与 executing-plans 的对比

  • 同 session、不切换上下文
  • 每条任务一个全新 subagent(避免上下文污染)
  • 每条任务后双阶段 review(spec → code)
  • 迭代更快(任务之间无 human-in-loop)

红线

不能跳过两阶段 review;不能让 subagent 读到你 session 里那些「跟这条任务无关」的杂质;不能把 BLOCKED 当作「我先做下一条」继续推。

配套

writing-plans / request-refactor-plan(前置:先有计划)、executing-plans(同语义但跨并行 session)、requesting-code-review / receiving-code-review(两阶段 review 的具体技能)、verification-before-completion(subagent 自检纪律)、ship(链路终点:合并发版)。

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
人工智能
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@obra · 未声明许可证
上下文用量评级
较高消耗
接入复杂程度
需简单配置
是否需要外部接口密钥
不需要
兼容的系统
未声明(默认跨平台)
运行环境要求
未检出明确要求
检测到的文件与系统行为
  • 只读
  • 允许写入 / 修改
  • 命令执行
网络行为
仅限本地
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

输出预览 subagent-driven-development.preview
You: I'm using Subagent-Driven Development to execute this plan.

[Setup: worktree verified]
[Read plan file once: docs/superpowers/plans/feature-plan.md]
[Resolve workspace: scripts/sdd-workspace docs/superpowers/plans/feature-plan.md — no ledger inside, fresh start]
[Create todos for all tasks]

Task 1: Hook installation script

[Run task-brief for Task 1; dispatch implementer with brief + report paths + context]

Implementer: "Before I begin - should the hook be installed at user or system level?"

You: "User level (~/.config/superpowers/hooks/)"

Implementer: [Later]
  - Implemented install-hook command
  - Added tests, 5/5 passing
  - Self-review: Found I missed --force flag, added it
  - Committed

[Run review-package PLAN_FILE BASE HEAD; dispatch task reviewer with the printed path]
Task reviewer: Spec ✅ - all requirements met, nothing extra.
  Strengths: Good test coverage, clean. Issues: None. Task quality: Approved.

[Ledger: Task 1: complete (commits a1b2c3d..d4e5f6a, review clean)]

Task 2: Recovery modes

[Run task-brief for Task 2; dispatch implementer with brief + report paths + context]

Implementer: [No questions]
  - Added verify/repair modes
  - 8/8 tests passing
  - Committed

[Run review-package PLAN_FILE BASE HEAD; dispatch task reviewer with the printed path]
Task reviewer: Spec ❌:
  - Missing: Progress reporting (spec says "report every 100 items")
  Issues (Important): Magic number (100)

[Fix round 1: resume the implementer with both findings]
Implementer: Added progress reporting, extracted PROGRESS_INTERVAL constant.
  Re-ran test/recovery.test.js — 10/10 passing. Fix report appended.

[Run review-package PLAN_FILE FIX_BASE HEAD; dispatch scoped re-review]
Re-reviewer: Missing progress reporting — ADDRESSED (src/recovery.js:41).
  Magic number — ADDRESSED (src/recovery.js:7). New breakage: none.
  Verdict: all findings addressed.

[Ledger: Task 2: fix round 1/5 (2 addressed, 0 open; commits d4e5f6a..b7c8d9e)]
[Ledger: Task 2: complete (commits d4e5f6a..b7c8d9e, review clean)]

...

[After all tasks]
[Run review-package PLAN_FILE MERGE_BASE HEAD; dispatch final code-reviewer, most capable model]
Final reviewer: All requirements met. Deferred minors triaged: none block merge.

[Delete this plan's workspace — the record now lives in git]

Done! Using superpowers:finishing-a-development-branch.

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。