Menu
Use to create or revise a spec and iteration plan from requirements; owns scope and plan decomposition, not implementation or step activation.
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.
Based on SOC occupation classification
Use to plan an AI/LLM evaluation strategy; advisory planning only, no implementation or QA closure.
Use to investigate a bug or incident and gather evidence before a fix; investigation only, implementation stays with the executor.
Use to review documentation for consistency and accuracy against code changes; read-only advisory, no doc rewrites or workflow closure.
Use for a delegated read-only advisory review through one explicit lens (security, performance, etc.); requires a named lens, makes no edits or closure.
Use to map an unfamiliar repository's architecture before brainstorming or planning; read-only discovery, no implementation edits.
Use to report the deterministic workflow checkpoint snapshot for a validated plan; snapshot only, no execution, QA, review, or compounder authority.
| name | imm-planner |
| description | Use to create or revise a spec and iteration plan from requirements; owns scope and plan decomposition, not implementation or step activation. |
Load dist/imm-planner.md, then create or revise
the executable plan. Keep scope explicit, including the Devil's Advocate
preplan audit and Devil's Advocate Audit output. Return plan path, decisions,
first step, verification approach, and Next Action.
planner ensemble is advisory-only and derives candidates from
workflow_models.planner_ensemble; final Spec and Plan authority stays here.
Agreement becomes evidence, Disagreement becomes decision criteria, and
strong-model blockers become risks or verification requirements.
