Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ibrahim-3d/loop-plan-evaluator
Evaluate-Loop Step 2: EVALUATE PLAN. Use this agent to verify an execution plan before any code is written. Checks scope alignment, overlap with completed work, DAG validity, dependency correctness, task clarity, and invokes Board of Directors for major tracks. Outputs PASS/FAIL verdict. Triggered by: 'evaluate plan', 'review plan', 'check plan before executing'. Always runs after loop-planner and before loop-executor.
Passed 13 of 18 test cases with the skill, and 5 of 18 without it.
and 15 more in the full report
11 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When running evaluation on `tracks/inventory/`, what is the exact metadata state written to `metadata.json` On Start before passes execute?
| Checked | Without skill | With skill |
|---|---|---|
| Sets current_step to EVALUATE_PLAN and step_status to IN_PROGRESS | Missed | Passed |
| Sets EVALUATE_PLAN checkpoint status to IN_PROGRESS | Missed | Passed |
The instructions your model reads when the skill loads.
Pre-execution quality gate. Verifies the plan is correct and scoped before any implementation begins. This prevents the exact problem that caused the PLAN-005 design system rebuild — an agent executing work that was already done.
For major tracks (architecture, features with 5+ tasks, integrations, infrastructure), this step also invokes the Board of Directors for multi-perspective expert review.
plan.md — the plan to evaluate (including DAG)spec.md — requirements to check againstconductor/tracks.md — completed tracks (overlap check)metadata.json — track type and priorityCheck every task against spec.md:
| For Each Task | Check |
|---|---|
| Is it in spec? | Task must trace to a specific spec requirement |
| Is it needed? | Would removing this task leave a spec requirement unmet? |
| Is it scoped? | Does the task do only what spec asks, not more? |
Output:
### Scope Alignment: PASS ✅ / FAIL ❌
- Tasks in spec: [X]/[Y]
- Tasks NOT in spec (scope creep): [list]
- Spec requirements NOT covered: [list]
Cross-reference with tracks.md and the codebase:
| Check | Method |
|---|
test cases passed, vs 5 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.