| name | controlflow-assumption-verifier |
| description | Use when a saved plan may contain hidden assumptions disguised as facts, especially for medium or large tasks, unresolved high-risk plans, or plans that mention files, APIs, versions, integrations, tests, or concurrency patterns that should be verified against the repository before execution. |
ControlFlow Assumption Verifier
Overview
Hunt mirages in a saved plan. This skill adapts ControlFlow's AssumptionVerifier to Codex by checking whether the plan invents files, APIs, dependencies, conventions, or execution assumptions that the repository does not support.
Workflow
- Read the saved plan artifact first.
- For each important claim in the plan:
- identify the claim
- decide whether it is repository-verifiable
- verify it against files, paths, symbols, configs, or tests
- classify it as
VERIFIED, UNVERIFIED, or MIRAGE
- Use references/mirage-patterns.md as the review grid.
- Focus especially on:
- phantom paths
- phantom APIs
- missing dependencies
- pattern mismatches
- missing error paths
- missing migrations
- missing security boundaries
- Save the verdict to
plans/artifacts/<task-slug>/assumption-verifier.md using ../../templates/assumption-verifier-report-template.md.
- Return a structured text report with:
COMPLETE or ABSTAIN- blocking and minor mirages
- a dimensional scorecard
- a recommendation
- If the plan requires meaningful redesign, classify it as:
fixableneeds_replanescalate
Output Shape
- Status
- Mirages Found
- Dimensional Scores
- Summary
- Failure Classification when blocking issues exist
Common Mistakes
- Treating every unknown as a mirage instead of separating
UNVERIFIED from MIRAGE.
- Checking only presence claims and skipping missing requirements or edge cases.
- Reviewing the plan abstractly without actually opening the referenced files or paths.
References
references/mirage-patterns.md../../templates/assumption-verifier-report-template.md
