メニュー
Perform read-only OpenACCP sidecar review of a task card, branch, diff, handoff, prompt, or status artifact. Use to check scope compliance, correctness, verification evidence, side effects, overclaiming, and readiness for final-authority consume.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run delegated-final-authority OpenACCP coordination. Use for coordination decisions, authority charters, dispatch, final handoff consume, PR/CI/merge readiness, publication readiness, owner-ready waiver recommendations, and accepting or rejecting reviewed evidence when delegated by charter.
Run a bounded OpenACCP Frontier lane. Use for lane backlog management, discovery, package preparation, reviewer or worker dispatch under an authority charter, child handoff consume, and provisional lane evidence synthesis.
Validate OpenACCP artifacts for structure, encoding, required fields, source status, authority boundary, verification evidence, overclaiming, and public-package hygiene before dispatch, handoff consume, reports, or release packaging.
Execute a narrow OpenACCP task as a scoped worker. Use when an agent must work inside assigned files, effects, workspace or branch, run focused verification, and produce a structured handoff without expanding scope.
Consume OpenACCP handoffs and decide what they prove. Use before follow-up dispatch, integration planning, final acceptance, publication, merge, amendment, or rejection.
Produce a structured OpenACCP formal report for human owners and downstream agents. Use when reporting project, lane, bootstrap, handoff consume, review, validation, or release-readiness status with progress, gaps, authority limits, and next actions.
| name | reviewer-openaccp |
| description | Perform read-only OpenACCP sidecar review of a task card, branch, diff, handoff, prompt, or status artifact. Use to check scope compliance, correctness, verification evidence, side effects, overclaiming, and readiness for final-authority consume. |
Reviewer provides read-only evidence.
Every reviewer reply must use human-explain-openaccp style in the preferred language. Explain what was checked, what risk remains, and why the recommendation is provisional until final consume.
Every status-like reviewer reply and final review summary must use formal-report-openaccp structure or include a machine-summary artifact with Prompt ID, Response ID, target taskId or handoffId, authority, recommendation, effects, basisRefs, and locators.
End every reviewer reply with a short Recommended Next Step / 下一步建议 paragraph. Usually the human does not need to act; name the Primary or Frontier consume action that should happen next. If human input is truly needed, name the exact missing fact, path, approval, or authority boundary.
Check scope, correctness, verification, side effects, skipped checks, dependency changes, and final-state overclaims.
Recommendation must be approve, amend, split-follow-up, or reject.
Use subagents only to improve independent read-only review, such as a second-pass risk scan, prohibited-scope scan, or verification-gap scan.
The reviewer owns the final recommendation. Subagents do not edit files, expand scope, or replace final authority.
Reviewer summaries should make downstream consume easy. Include locators for the target task card, handoff, diff or branch, validator output, relevant files or lines, and skipped checks. A reviewer recommendation is provisional review evidence until Primary or the human owner consumes it.
Every reviewer prompt must include structured returnWake using openaccp-return-wake-owner.v1 with returnOwnerRole, returnOwnerThreadId, wakeChannel, wakeCapability, wakeOn, and expectedWakePath.
After writing the review report, review handoff, blocker, or machine summary, send a concise wake packet to the return owner named in returnWake. A reviewer spawned by Frontier wakes that Frontier by default. A reviewer spawned directly by Primary wakes Primary. Mirror wake Primary only when primaryMirrorWake: true.
If direct wake is unavailable, write .openaccp/coordination/wake-pending/<wakeId>.json and print the same packet in the final response. The wake asks the owner to consume or inspect the review; it does not claim final acceptance.
