ワンクリックで
plan-adherence-reviewer
Read-only reviewer for checking whether an implementation milestone matches an approved plan or spec.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Read-only reviewer for checking whether an implementation milestone matches an approved plan or spec.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Watch an open GitHub pull request for CI, mergeability, bot reviews, and human feedback until it is ready, closed, or blocked.
Harness-portable autonomous delivery loop for a scoped software task: front-load uncertainty, produce or confirm a plan, implement with TDD and validation, run review passes, prepare git/GitHub artifacts, and babysit the PR when authorized. Use when the user wants a mostly hands-off problem-to-PR workflow.
Use for commit, push, pull request, issue, and GitHub CLI workflows; emphasizes diff-grounded text and safe non-interactive commands.
Harness-portable planning and requirements-capture workflow for turning vague, risky, architectural, multi-workstream, or scope-drift-prone requests into durable artifacts before implementation. Use when the user asks to scope, plan, workshop, write a spec, capture acceptance criteria, prepare an implementation handoff, or when product intent should not be guessed.
Guide agents to choose a review pass intentionally and keep findings structured.
Use when starting feature work that should be isolated from the main checkout; creates or verifies an isolated git worktree with safety checks.
SOC 職業分類に基づく
| name | plan-adherence-reviewer |
| description | Read-only reviewer for checking whether an implementation milestone matches an approved plan or spec. |
Use this skill after a milestone is implemented and before moving on, opening a PR, or running broader code-quality reviews.
Do not use it to approve the tentative architecture design. It reviews implementation against an already-approved plan.
If required inputs are missing, emit BLOCKED instead of inventing a verdict.
PASS — implementation satisfies the approved plan with, at most, minor
implementation-detail drift.BLOCKED — required input or implementation evidence is missing, or the
implementation must change before proceeding.NEEDS_PLAN_AMENDMENT — the implementation diverges from plan behavior,
scope, guardrails, or out-of-scope boundaries and needs user judgement.Use this structure:
# Plan Adherence Verdict: PASS|BLOCKED|NEEDS_PLAN_AMENDMENT
## Scope Reviewed
- Plan:
- Milestone:
- Diff:
- Worktree:
## Findings
- [severity] File/path: issue and required action
## Evidence
- Validation reviewed
## Notes
- Non-blocking observations