Menu
Review the current branch, PR, or worktree against the plan or ExecPlan and record findings. Use when an agent needs a code review with findings for changes associated with an active plan.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Author CLI surfaces as agent-facing documentation, especially `--help` and actionable error messages. Use with any language or parser design when adding or changing a CLI interface, improving help text or validation errors, moving command reference out of AGENTS.md / CLAUDE.md / a README / a skill and into CLI surfaces, or making errors suggest the corrected command line or tool call.
Create or revise repository `AGENTS.md` files using a progressive-disclosure, dispatcher-style structure. Use when an agent needs to author or edit a top-level or directory-local `AGENTS.md`, convert a long instruction file into task-oriented "Start Here for ..." sections, add a concise "Must Follow" section with Always/Never rules, improve skill-discovery cues, or decide whether guidance belongs in root `AGENTS.md`, deeper docs, local `AGENTS.md`, or a repository-local skill.
Create or revise repository `ARCHITECTURE.md` files as short, stable architecture codemaps. Use when an agent needs to author or edit `ARCHITECTURE.md`, restructure an architecture document around a bird's-eye view and code map, clarify system boundaries, add architectural invariants or cross-cutting concerns, or decide which implementation detail should stay out of `ARCHITECTURE.md` and live in deeper design documents instead.
Create or revise Markdown `description` frontmatter so `docgarden match` routes agents to the right repository documents. Use when adding a new routed Markdown document, updating existing frontmatter, fixing noisy or missing match results, tuning skills or docs discovery, or making descriptions more query-aligned without loading document bodies.
Implement from an active plan or ExecPlan while keeping it up to date. Use when an agent needs to implement the active plan, continue plan-driven work, resume the current plan, or carry out an existing ExecPlan.
Create, update, revise, reopen, or rescope a plan or ExecPlan using `PLANS.md`. Use when an agent needs to create a plan, plan a change, update the plan with new requirements, or rewrite an active ExecPlan.
| name | evaluator-execplan |
| description | Review the current branch, PR, or worktree against the plan or ExecPlan and record findings. Use when an agent needs a code review with findings for changes associated with an active plan. |
| metadata | {"internal":true} |
Use this skill when the task is to review the current PR branch or worktree that is closing out an ExecPlan.
Read the diff or changed files. Do not load the ExecPlan, CODESTYLE.md, or TESTING.md yet.
For new methods, exports, or class members, grep for callers before assuming they are used.
Record your observations before moving to Pass 2.
Now load:
docs/PLANS.mdFollow the review authorities listed under Pass 2 in the ExecPlan's Evaluator DoD. If a changed surface is not covered by the plan's DoD, treat the missing coverage as a finding. Then add findings that require plan context:
Apply each rule at the granularity it requires. If TESTING.md says individual tests must move unless they call private functions, inspect individual tests, not just whether a module contains any test.
As evaluator, you own:
CODESTYLE.md violations, TESTING.md violations, and unnecessary complexityDefinition of Done section once the review is clean and all findings are addressedYou do not own:
Use the evaluator when the task is to perform an independent review of the current branch or worktree against the plan.
Act like a reviewer, not a closeout assistant. Record findings in the ExecPlan without softening the review to fit what was built.