菜单
Use when a repository task needs a strict ControlFlow-style implementation plan before coding, especially for 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/.
用 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 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.
| name | controlflow-planning |
| description | Use when a repository task needs a strict ControlFlow-style implementation plan before coding, especially for 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/. |
Create a durable, execution-ready Codex plan. Keep the contract local: the saved artifact defines scope, risks, files, phases, validation, review route, and handoff without depending on VS Code agent mode.
SMALL, MEDIUM, or LARGE; skip it only for truly TRIVIAL work.plans/<task-slug>-plan.md unless the user names another path.SMALL, MEDIUM, LARGE), include the five fixed lifecycle sections in this exact order and with these exact headings: ## Progress, ## Discoveries, ## Decision Log, ## Outcomes, ## Idempotence & Recovery. These headings are required by ../../scripts/validate-strict-artifacts.ps1 and must match the template and fixtures exactly.ABSTAIN or REPLAN_REQUIRED when confidence is below 0.9 or evidence is insufficient.HIGH-impact risk is unresolved.SMALL -> controlflow-plan-audit; MEDIUM/LARGE -> add controlflow-assumption-verifier; unresolved HIGH risk -> include controlflow-assumption-verifier regardless of size.When requirements, acceptance criteria, boundaries, or verification gates are not explicit, use controlflow-spec first. Carry its spec_path, scope, acceptance criteria, constraints, success metrics, and open risks into the plan. If spec capture is unnecessary, state why the request is already clear enough.
READY_FOR_EXECUTION without a strict review route and artifact destination.plans/<task-slug>-plan.md.Agent: Planner in the artifact so the document matches the original conceptual role even though the implementation is a Codex skill.READY_FOR_EXECUTION plans, include a clear handoff section that points execution to orchestration.references/plan-template.mdreferences/complexity-tiers.mdreferences/semantic-risk-taxonomy.mdreferences/controlflow-portability.mdreferences/planner-output-contract.mdreferences/llm-behavior-guidelines.md