review-plan
Skill88 starsChanged 21 days agoMITView on GitHub
审查技术方案。 当技术方案需要在进入实现前接受审查时使用。 仅当对话包含可解析的任务引用时才可自动调用本技能。
37 other projects use a version of this.
Adopted by
Most recently taken up by
- event-driven-io/emmetttheir own version, first seen Nov 16, 2026
- nicosocoro/agent-skillstheir own version, first seen Nov 15, 2026
- atomicinnovation/acceleratortheir own version, first seen Nov 14, 2026
- CsHeng/agent-skillstheir own version, first seen Nov 9, 2026
- serionist/claude-session-restoretheir own version, first seen Nov 8, 2026
- withpiper/pipekittheir own version, first seen Nov 8, 2026
Used with
Projects with it also use implement-plan, review-design and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JasonPaffSkillimplement-plan
Execute implementation plan with structured tracking and validation using subagent architecture
Also in 5 projects that use this
dirkkok101Skillreview-design
Use before /plan, after /technical-design, when user says "review design", "check the design", or when design quality is uncertain.
Also in 3 projects that use this
SvampenSkillreview-implementation
Reviews implementation against session/work stream goals before committing. Identifies shortcuts, hacks, incomplete work, and validates accomplishments match actual changes. Use before /session-end to ensure implementation quality.
Also in 3 projects that use this
PydanticSkillreview-security
Security review of the current branch against its merge base — sandbox escapes, memory errors, panics and resource-limit bypasses. Use when reviewing changes for security risk, or before merging anything touching the heap/ module, path_security.rs, the wire protocol or the pool.
Also in 3 projects that use this
am-willSkillplanner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
Also in 3 projects that use this
sahinSkillexecute
Also in 3 projects that use this
Other versions37 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 37
- penpot/penpot★ 62ksame name
- event-driven-io/emmett★ 567same name
- JetBrains/youtrackdb★ 443same name
- wallstop/unity-helpers★ 177same name
- shader-slang/slangpy★ 157same name
- microsoft/vscode-team-kit★ 67same name
- DasDigitaleMomentum/opencode-processing-skills★ 60same name
- Cleveland-RD/hivehouse★ 46same name
- atomicinnovation/accelerator★ 35same name
- hawkyre/hawk-skills★ 30same name
27 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-taskSkill
- archive-tasksSkill
- block-taskSkill
- cancel-taskSkill
- check-taskSkill
- close-codescanSkill
- close-dependabotSkill
- code-taskSkill
- commitSkill
- complete-manual-validationSkill
- complete-taskSkill
- create-prSkill
- create-release-noteSkill
- create-taskSkill
- entropy-checkSkill
- import-codescanSkill
- import-dependabotSkill
- import-issueSkill
- init-labelsSkill
- init-milestonesSkill
- plan-taskSkill
- post-releaseSkill
- refine-titleSkill
- releaseSkill
- restore-taskSkill
- review-analysisSkill
- review-codeSkill
- review-prSkill
- run-manual-validationSkill
- test-integrationSkill
- testSkill
- update-agent-infraSkill
- upgrade-dependencySkill
- watch-prSkill
The file
Files
技术方案审查
--agent取值见.agents/rules/task-management.md「合作者 token 规范」。
生命周期事件必须携带显式触发信息:普通技能调用使用 model;仅用户明确要求时使用 human。{request-id} 是本任务与本轮产物的稳定单行标识,{reason-code} 使用 user-request 或 review-finding;started 与 completed 使用同一组值。
审查最新技术方案产物,并产出 review-plan.md 或 review-plan-r{N}.md。
行为边界 / 关键规则
路径与返工
本阶段只消费核心从最新有效分析产物解析出的规范路径事实;未被所选路径包含的阶段不得创建产物。同阶段完成一次修订—复审后再次收到 Changes Requested 时,必须在下一执行产物前提交绑定 finding、来源 SHA 和稳定任务事实摘要的返工分类;轮次或文件名变化不是新证据。
持久化报告证据
生成审查报告时,先读取 .agents/rules/evidence-reporting.md。正常检视记录命令、范围、结构化结果、实际结论和未覆盖部分;finding、阻塞或争议保留可复现位置与决定性摘录,身份字段必须精确保留。
- 审查候选资格或
HD-N判断时,先读取.agents/rules/decision-qualification.md,逐项复核产物中的三张资格审计决策表、资格快照、digest 和 QCR;不得把流程标签当作身份认证 - 本技能只审查方案产物并写报告,不修改业务代码
- 生成会同步到 Issue 的任务或生命周期 Markdown 前,先读取
.agents/rules/sync-content-generation.md并遵循其中的生成端约束;同步端不解析或改写正文 - 执行本技能后,你必须立即更新 task.md
版本戳规则:创建或更新 task.md frontmatter 时,先读取 .agents/rules/version-stamp.md,并写入或刷新 agent_infra_version。
第 0 步:状态核对(执行前硬约束)
在加载 workflow / skill / rules 指令之后、做任何任务状态判断或用户可见结论之前,必须先执行状态核对。指令类文件读取不算对外动作或结论。
运行以下命令,并在本轮产物的 ## 状态核对 段记录任务/产物范围、关键结果和未覆盖部分;正常成功不粘贴完整目录清单或 task.md 尾部。失败、阻塞、身份不一致或争议时,附决定性原文行:
agent-infra-internal task-snapshot {task-id} --format text状态核对完成前,禁止任何关于外部状态的断言。
任务上下文解析
入口可省略 task ref;显式 task scope 仅接受
--task <ref>或-t <ref>,不再解释位置 task ref。保留其余业务操作数后调用agent-infra-internal task-context resolve {task-scope};{task-scope}为空或 task flag 之一。只读取结构化结果的taskId,后续把{task-id}绑定为完整TASK-YYYYMMDD-HHMMSS。解析失败时透传非零退出码,不自行扫描任务。
解析任务引用,并确认任务位于本技能支持的状态或目录且存在
task.md;无法定位时按未找到任务处理并停止。
步骤开始:声明 started 事件
确认前置条件和产物上下文后、本轮第一个产出动作之前执行 agent-infra-internal task-event {task-id} review-plan.started --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code}。
执行步骤
1. 验证前置条件
要求存在:
<task-workspace>/active/{task-id}/task.md- 至少一个方案产物:
plan.md或plan-r{N}.md
2. 解析审查上下文
运行 agent-infra-internal task-artifact {task-id} inspect --family review-plan。仅当结果为 ready 时继续。若 selection.disposition 为 reuse,复用 selection.artifact,不得执行 started、init 或写入新产物,并直接进入完成校验与下一步提示。其他状态从 inputs 取得 {plan-artifact},从 next.round / next.name 取得 {review-round} / {review-artifact};不得自行扫描轮次或拼装文件名。随后执行 started 事件并复核返回身份。
3. 阅读方案上下文
读取最新 {plan-artifact}、最新分析产物、task.md 和关联 Issue 上下文(如有)。读取后,把本轮实际检视的最高轮 plan artifact 文件名回填到报告 审查输入 段;无法可靠取得时留空,不要伪造。
4. 执行审查
重点检查方案的简洁性、可执行性、风险控制、测试策略、文件清单和阶段边界。
共享检视方法见
.agents/rules/review-method.md。执行此步骤前先读取该规则,并按五遍协议完成覆盖声明、风险镜头判断、追踪矩阵和反证检视。 详细审查标准见reference/review-criteria.md。执行此步骤前先读取reference/review-criteria.md。
5. 编写审查报告
在首次写入本轮 {review-artifact} 前,先创建受控审查骨架:
agent-infra-internal task-artifact {task-id} init --family review-plan --artifact {review-artifact}骨架不生成审查结论、发现或计数;完成审查内容后才能进入 summary finalizer。结构错误时,遵循 .agents/rules/local-artifact-repair.md 直接修正正式审查产物并重跑原 finalizer;当前产物内容是唯一输入。
创建 <task-workspace>/active/{task-id}/{review-artifact}。
报告格式见
reference/report-template.md。写报告前先读取reference/report-template.md。
6. 更新任务状态
报告完成后,先调用 agent-infra-internal task-review {task-id} preflight --stage plan --artifact {review-artifact},不得先写入账本。失败后直接修正正式产物并重跑;只有 preflight 通过后,才逐条调用 agent-infra-internal task-ledger {task-id} finding-upsert --stage plan --review-artifact {review-artifact} --ordinal {n} --severity {blocker|major|minor} --evidence {review-artifact}#{anchor},或复核上一轮响应时调用 finding-review --id {ledger-id} --status {confirmed|closed|open|needs-human-decision} --evidence {相称证据}。不得扫描编号或手写账本行。全部账本写入完成后调用 agent-infra-internal task-review {task-id} finalize-summary --stage plan --artifact {review-artifact};不能把失败类型或 changed=false 当作自动授权。
从该次返回值绑定并复用以下结构化映射:
{unresolved-blockers} = stageStatus.unresolvedFindingCounts.blocker
{unresolved-major} = stageStatus.unresolvedFindingCounts.major
{unresolved-minor} = stageStatus.unresolvedFindingCounts.minor该 intent 原子最终化报告摘要并返回同一次账本快照;不得再调用 stage-status、手工替换占位符或扫描问题清单。失败后,模型只能在共享规则的机械安全门通过时修改同一个受控 artifact,并完整重跑相同 intent;每次失败都重新判断是否收敛。最终一次完整成功返回决定同一快照的 verdict 和计数:stageStatus.canAdvance=true 且结论为 Approved 时允许跨阶段推进;stageStatus.canAdvance=false 时仍须执行 agent-infra-internal task-event {task-id} review-plan.completed --agent {standard-agent-token} --initiator {trigger-initiator} --request-id {request-id} --reason-code {reason-code} --artifact {review-artifact} --verdict {approved|changes-requested|rejected} --blockers {unresolved-blockers} --major {unresolved-major} --minor {unresolved-minor} --manual-validation {n},使用 changes-requested 并路由到同阶段修订/复审(报告明确拒绝时使用 rejected)。失败、模型停止、无进展或紧急熔断时,不发布完成事件或跨阶段命令,但必须按 reference/output-templates.md 的 repair-stop 场景展示已有 summary/findings、artifact、实际修复次数、最后诊断和停止原因。
manual-validation 是 ai task log 中 review 行「人工校验点」(EN Manual-validation)计数的数据源;不要新增并行人工验证字段。
如果 task.md 中存在有效的 platform_issue_identity,调用 agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token},再调用 agent-infra-internal platform-comment sync {task-id} --kind artifact --artifact {review-artifact} --agent {standard-agent-token};失败按 .agents/rules/issue-sync.md 记录 warning。
最终化 intent 会在写入摘要前检查详情块 ID;任何可见重复都返回结构化失败并保持 artifact 字节不变,由模型按共享规则判断是否进行最小编辑。无法通过安全门、诊断重复、没有实际字节变化或达到紧急熔断时,停止在完成事件之前;停止路径仍必须展示已有审查结果,不得吞掉 artifact 内容。
7. 完成校验
agent-infra-internal task-verify {task-id} review-plan.completed --artifact {review-artifact} --format text按 .agents/rules/validation-output.md 展示当次校验摘要;失败、阻塞和软警告保留必要诊断。
校验通过后继续告知用户;校验失败则修复报告或 task 状态后重跑。
8. 告知用户
按 reference/output-templates.md 的结论分支输出,并通过统一 helper 渲染已选场景的下一步命令。
渲染最终输出前先读取
.agents/rules/next-step-output.md,并将「下一步」命令的{task-ref}渲染为当前任务短号NN(取值与回退见该文件);其他{task-id}占位(报告标题、路径)保持完整 TASK-id 形式。
完成检查清单
- 已审查最新方案上下文
- 已创建
{review-artifact} - 已更新 task.md 并追加 Activity Log
- 已通过统一 helper 渲染已选场景的下一步命令
注意事项
- 首轮审查使用
review-plan.md,后续轮次使用review-plan-r{N}.md - 所有问题都要引用具体文件路径和行号;方案产物问题可引用
{plan-artifact}的行号
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

