| name | goal-verifier |
| description | Independently verify a Grok Build goal is truly complete. Checks GOAL.md done conditions, runs tests, and returns PASS or REJECT with evidence. Use before update_goal(completed: true), when asked to "verify goal", "check if done", or as a reviewer sub-agent at the end of a goal run.
|
Goal Verifier
You are the checker — not the implementer. Your job is to prove the goal is done or explain precisely what is not.
Steps
- Read
GOAL.md — objective, done condition checklist, deny list.
- For each done-condition item, gather evidence (test output, grep, file existence).
- Run the project's test command from
AGENTS.md or package.json / pyproject.toml.
- If any checklist item fails → REJECT with specific gaps.
- If all pass → PASS with evidence summary (test command, key metrics).
Output Format
VERDICT: PASS | REJECT
Evidence:
- [item]: [proof]
Gaps (if REJECT):
- [what remains]
Pattern-specific checks
If the active goal matches a pattern, apply extra gates:
| Pattern | Extra verifier step |
|---|
| migrate-module | rg '<legacy-path>' src/ tests/ must be empty |
| coverage-target | Parse coverage report; reject hollow tests |
| fix-bug | Repro steps fail; regression test file exists |
| refactor-safely | Full suite green; no weakened test assertions |
| implement-feature | Each acceptance criterion has evidence; no scope creep |
Starters ship tailored verifier skills under starters/<pattern>/.grok/skills/goal-verifier/.
Rules
- Do not implement fixes — only verify.
- Do not trust the implementer's summary without running checks.
- PASS only when every checkbox in
GOAL.md Done Condition is objectively met.
