القائمة
Use after a ControlFlow plan is saved and before implementation. Runs tier-gated adversarial verification inline: structural audit, assumption/mirage detection, and cold-start executability simulation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a non-trivial repository task needs a durable, execution-ready ControlFlow plan before coding, especially for cross-file changes, migrations, architectural uncertainty, or explicit risk review.
Use after implementation when a ControlFlow plan exists and review should focus on plan conformance, scope drift, evidence-backed correctness findings, and residual validation gaps rather than duplicating native Codex /review.
Use when a repository task needs a high-quality ControlFlow plan before coding — small, medium, or large scope, cross-file edits, risky migrations, architectural uncertainty, or any work that should produce a saved Markdown plan artifact in plans/. Single-sources the plan format from schemas/planner.plan.schema.json and the plan template.
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.
Use when a saved plan should be tested for cold-start executability before coding, especially for large tasks, weak-confidence plans, or plans whose early phases may be too vague for a fresh executor to follow without hidden context.
Use when work spans many turns or phases and you need durable notes, active-objective tracking, or context compaction without letting stale memory override the current codebase.
| name | controlflow-verify |
| description | Use after a ControlFlow plan is saved and before implementation. Runs tier-gated adversarial verification inline: structural audit, assumption/mirage detection, and cold-start executability simulation. |
Verify a saved plan before implementation. The checks run inline in the current host context with zero subagents shipped by the plugin. This skill combines the useful parts of the former plan-audit, assumption-verifier, and executability-verifier workflows without reproducing Codex subagent orchestration.
Select the skill explicitly. In Codex, invoke it with $controlflow-verify.
schemas/planner.plan.schema.json and
plans/templates/plan-document-template.md, use them.../controlflow-plan/references/plan-format.md.| Tier | Verification |
|---|---|
TRIVIAL | Skip unless explicitly requested |
SMALL | Phase 1 |
MEDIUM | Phases 1–2 |
LARGE | Phases 1–3 |
Any unresolved applicable HIGH semantic risk requires all three phases.
confirmed, uncertain, or refuted.APPROVED: all required phases pass and implementation may start.NEEDS_REVISION: the design is viable but specific plan defects must be fixed.REJECTED: the scope or architecture is not safely deliverable as written.failure_classification: fixable, needs_replan, or escalate for non-approval.plans/artifacts/<task-slug>/verify-verdict.md.APPROVED./review
is the built-in review command.references/adversarial-framing.mdreferences/verify-phases.mdreferences/mirage-patterns.md