build-implementation-plan
Use when implementation_orchestrator starts building, or when an autonomous factory needs a fresh implementation_builder to implement IMPLEMENTATION_PLAN.md. Do not write product code in-process.
- License 许可
- MIT
- 所属仓库
- sazlin/loadout
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- build-implementation-plan
- description
- Use when implementation_orchestrator starts building, or when an autonomous factory needs a fresh implementation_builder to implement IMPLEMENTATION_PLAN.md. Do not write product code in-process.
02 资源文件 2
- 参考文档evals/evals.json526 B
- 参考文档evals/files/brief.md72 B
03 SKILL.md 正文
Build implementation plan
Dispatch implementation_builder on a fresh subagent to implement
IMPLEMENTATION_PLAN.md.
When to use
implementation_orchestratorhas a plan that survived review- The factory asks for
/build-implementation-plan
Do not use to write the plan, review the tree yourself, or open a PR.
Steps
- Confirm
IMPLEMENTATION_PLAN.mdand the feature branch. The brief must include the PRD path and "quality over speed; loop/review-implementation-buildup to 10 times." Do not label the repo's age or size; the builder inspects the tree. - Dispatch one isolated
implementation_buildersubagent. Do not inherit this session's history. Tell it: "Follow.claude/agents/implementation_builder.md. Commit on the feature branch. Do notgit push. Do notgh pr create." - Wait for the builder JSON. If status is
blocked, return that to the orchestrator; do not finish the work in-process. - Do not edit product code in-process.
Harness
- Cursor: one
Taskcall with namedimplementation_builderif available. - Claude Code: one Agent call using
implementation_builder.
Guardrails
- Never become the builder
- Never skip the fresh-context dispatch
- Never ask a human to pick an implementation; the plan and PRD win
- Never start
pr_review_harnessagents or skills - Never merge
04 同仓库更多 Skills
demo
Demo skill
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback