review-implementation-build
Use when implementation_builder needs a fresh implementation_build_reviewer to critique the implementation against IMPLEMENTATION_PLAN.md and the PRD. Do not edit product code in-process.
- License 许可
- MIT
- 所属仓库
- sazlin/loadout
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- review-implementation-build
- description
- Use when implementation_builder needs a fresh implementation_build_reviewer to critique the implementation against IMPLEMENTATION_PLAN.md and the PRD. Do not edit product code in-process.
02 资源文件 2
- 参考文档evals/evals.json466 B
- 参考文档evals/files/brief.md77 B
03 SKILL.md 正文
Review implementation build
Dispatch implementation_build_reviewer on a fresh subagent to review
the current tree against the plan and PRD.
When to use
implementation_builderfinished a build or a revision- The factory asks for
/review-implementation-build
Do not use to fix code, write the plan, or open a PR.
Steps
- Resolve the change set (
git diffagainst the branch point). IncludeIMPLEMENTATION_PLAN.md, the PRD path, and the diff range in the brief. - Dispatch one isolated
implementation_build_reviewersubagent with: "Follow.claude/agents/implementation_build_reviewer.md. Return only your JSON issue schema. Do not edit files. Do not fix the code." - Wait for the JSON report. If the issue schema is missing, one retry, then
record the reviewer as
missing. - Do not edit product code in-process. The builder applies feedback.
Harness
- Cursor: one
Taskcall (named agent type if available). - Claude Code: one Agent call using
implementation_build_reviewer.
Guardrails
- Never become the build reviewer
- Never implement fixes during this skill
- Never ask a human to waive a finding; substantial issues stay open
- Never start
pr_review_harnessagents or skills
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