Menu
Use for non-trivial Cursor work: saved plan, tiered pre-execution review, phased execution, and final review with durable artifacts under plans/.
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.
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 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.
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.
Based on SOC occupation classification
| name | controlflow-strict-workflow |
| description | Use for non-trivial Cursor work: saved plan, tiered pre-execution review, phased execution, and final review with durable artifacts under plans/. |
Use this entry point in Cursor Agent mode for the full ControlFlow workflow: plan, pre-execution review, execution, final review, and durable artifacts. Read and follow sibling skills under .cursor/skills/ (or project skills path).
controlflow-router skill.controlflow-planning at plans/<task-slug>-plan.md.TRIVIAL: optional strict reviewSMALL: delegate controlflow-plan-auditor or follow controlflow-plan-audit skillMEDIUM: plan audit + controlflow-assumption-verifier agent or skillLARGE: add controlflow-executability-verifier agent or skillHIGH semantic risk: include assumption verifier; consider executability verifierplans/artifacts/<task-slug>/.controlflow-orchestration skill; delegate implementer phases to .cursor/agents/controlflow-*-implementer when Task is available.controlflow-code-reviewer agent or controlflow-review skill.controlflow-memory-hygiene as needed.When the Task tool is available, delegate isolated review/research with:
Task(subagent_type="controlflow-plan-auditor", description="Plan audit", prompt="...")
Use subagent_type matching the filename in .cursor/agents/ (without .md). The prompt must include plan path, tier, trace_id, and expected report sections.
Fallback: If Task is unavailable, run the matching skill in this session and save Markdown under plans/artifacts/<task-slug>/. Do not claim isolation was enforced.
Every phase claim needs evidence: command output, artifact path, review result, test result, or documented skip reason. See controlflow-planning references for anti-rationalization rules.
plans/<task-slug>-plan.mdplans/artifacts/<task-slug>/plan-audit.mdplans/artifacts/<task-slug>/assumption-verifier.mdplans/artifacts/<task-slug>/executability-verifier.mdRun the repository verification command when defined (e.g. cd evals && npm test in ControlFlow repo). Update lifecycle sections: ## Progress, ## Discoveries, ## Decision Log, ## Outcomes, ## Idempotence & Recovery.
plugins/controlflow-cursor/USAGE.mddocs/agent-engineering/CURSOR-SUPPORT.mdplugins/controlflow-cursor/templates/