跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
其他技能

review-implementation-plan

Independent single-phase or batch review of implementation plans against scope, codebase reality, actionability, and cross-phase consistency. Produces per-phase structured reviews with severity-rated findings.

DasDigitaleMomentum · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add DasDigitaleMomentum/opencode-processing-skills --skill review-implementation-plan

技能说明


name: review-implementation-plan description: Independent single-phase or batch review of implementation plans against scope, codebase reality, actionability, and cross-phase consistency. Produces per-phase structured reviews with severity-rated findings. license: MIT compatibility: opencode: ">=0.1" metadata: category: review phase: planning

Skill: Review Implementation Plan

This skill provides an independent quality gate for implementation plans authored via author-and-verify-implementation-plan.

A reviewer fresh from the authoring context evaluates one implementation plan or an ordered batch against phase scope, existing code, and actionability criteria. Fresh independence does not mean starting a cold reviewer for every phase. Each review remains a per-phase plan artifact.


When to Use

Use this skill when:

  • An implementation plan has been authored/verified and you want to validate it before execution.
  • Multiple implementation plans have been authored sequentially and should be reviewed together as a dependency-ordered batch.
  • You want to confirm that the implementation plan is concrete enough for execute-work-package.
  • The user explicitly requests an implementation plan review.

Do not use this skill to:

  • Review the plan itself (use review-plan).
  • Review a completed implementation (use review-implementation).
  • Rewrite the implementation plan during the independent review pass. After review completion, the Primary may accept defects and explicitly instruct technical implementation-plan remediation through review-fix in the eligible source session. Conversation-owned plan corrections remain with update-plan.

Review Focus

The default priority is the smallest complete implementation: confirm that phase obligations are covered and no implementation step or new artifact is unauthorized, unnecessary, or needlessly indirect. Use the actual codebase to substantiate material concerns, but record only evidence-backed exceptions. The primary may add a focus via {{focus}}.

Review posture

Detect existing gold-plating without becoming an adversarial reviewer. A reduction finding must name a concrete planned step/artifact and show missing authorization, missing present necessity, or a smaller path in the current codebase that remains complete: the requested behavior must still work, affected real paths must still integrate, and applicable existing invariants must be preserved. Scope discipline is not permission to omit necessary work. Do not invent ideal architecture, hardening, tests, infrastructure, policy, or replacement work. Zero findings remains valid.

Testing, references, Reality Check wording, documentation, and other formal criteria are not checklist obligations. Report them only when a concrete defect would block or misdirect execution.


Execution Model

Roles

  • Primary (maintainer)

    • Invokes the review skill.
    • Delegates to delegate-strong (default) or general (for same-model perspective).
    • Receives review summary and decides on follow-up actions.
    • Routes a batch through one fresh reviewer session by default and retains that task_id for possible remediation.
  • Subagent (delegate-strong / general)

    • Starts without authoring context, then retains shared review context across a batch.
    • Uses the actual codebase selectively when a material concern needs evidence.
    • Writes the existing review artifact for every reviewed phase at plans/<name>/reviews/impl-plan-review-phase-N.md.
    • Reports material cross-phase conflicts in the relevant artifact and returns one aggregate digest.

Why delegate-strong (not doc-explorer)

Same rationale as review-plan: the reviewer must be independent from the authoring work. In batch mode that fresh reviewer keeps useful context between phases rather than repeatedly approaching each phase cold. delegate-strong provides the judgment depth needed to evaluate implementation feasibility and cross-reference plan claims against real code.

Routing Matrix (Who does what)

  • Writes: one or more existing plans/<name>/reviews/impl-plan-review-phase-N.md artifacts; no consolidated artifact is required.
  • Does NOT write: implementation plans, phase docs, or any other plan artifact.
  • Primary: owns the decision of whether to act on findings.
  • delegate-strong/general: performs the review, including codebase verification.

Workflow

1) Select review mode and prepare references

Primary gathers:

  • Review focus from the delegation prompt
  • plans/<name>/plan.md
  • One phase/implementation-plan pair for single-phase mode, or all selected pairs in dependency order for batch mode
  • Relevant existing docs only when they reduce a material code lookup

2) Delegate

Primary delegates to delegate-strong (or general) using tpl-review-impl-plan-prompt.md.

Provide:

  • Review mode and the ordered plan, phase, and implementation-plan paths
  • Docs references (if available)
  • One review output path per phase: plans/<name>/reviews/impl-plan-review-phase-N.md
  • Review focus (freetext — what to prioritize)

In batch mode, one fresh reviewer processes phases sequentially, reuses shared evidence, writes each per-phase artifact, reports only material shared-interface conflicts, and returns one aggregate digest. Split the batch only when unrelated domains or practical context capacity require it.

3) Receive summary

For single-phase mode, the subagent returns the same fields for that phase. For batch mode, it returns one aggregate digest containing:

  • Overall and per-phase verdicts (Ready / Needs Revision / Major Gaps)
  • Overall and per-phase reduction flags
  • Aggregate finding count by severity
  • Top 3 actionable findings across the batch
  • Required next action

4) Act on findings

Primary decides:

  • Ready: Proceed to execute-work-package only when reduction is not required and no Critical/Major findin
阅读完整来源 ↗