planlisted

Plan the following work: $ARGUMENTS 1. Have team-planner write docs/plans/NNNN-<slug>.md. Make it reference the charter, CLAUDE.md, BACKLOG and ASSESSMENT/REBUILD_PLAN when they exist. 2. If the plan has 3+ steps or is risk:high, have team-critic review it (follow the operating profile's critic threshold if set); otherwise skip. On REVISE, pass the findings verbatim to the planner (max 2 rounds). 3. If any item meets the escalation criteria, ask the CEO with AskUserQuestion. If a step needs a capability no role has (a permission boundary or a separate judge), say so and suggest `/recruit <gap>` in a sentence. 4. Request approval with a summary (goal, step count, risks, expected diff). Once approved, do not call it via the Skill tool — suggest to the CEO in a sentence: "run `/run`". Never start /build or /run yourself.