plan

/ac/plan

Main-thread planner: parallel read-only research, your own reading of the code, every load-bearing decision through the question tool, then a tier-assigned plan at .ac/plans/<slug>/plan.md.

Request: the text of the user's request. When the run starts from the /ac/plan command, that is the command's argument text. This skill takes no arguments of its own, so the topic and the flags (--auto, --lane, --slug <s>, --revise) are read out of that request text; it is called REQUEST below. A caller that loads this skill with the skill tool writes the request text as one line in its own message first (Request: <text>), which is what this skill then reads.

Standing rules

These hold for the whole run, including after a compaction (which can drop most of a long skill body). Everything below this block is procedure; these are the bounds.

Turn termination. Your turn ends on exactly one of: a question call, the Stage 6 plan summary (or, under AUTO_MODE = true, the chained execute run reaching its own terminal state), a named BLOCKER from <auto_mode>, or a one-line wait status while background subagents you spawned still run (each completion notification starts your next turn; never wait with a sleep or polling loop). Under LANE_MODE the only ends are lane status blocks (Lane mode below). Nothing else ends it. Never end a turn by describing what you would do next, and never on the Stage 4 render: it is followed by a question call in the same turn. When a turn does end on a render and the user says "continue", resume at the question that render was leading to; a stage whose question went unasked did not complete.

Lane mode. --lane sets LANE_MODE = true and implies --auto. A lane is an ac/lane session in its own git worktree: it has no question tool, and its coordinator sees only its last message of each turn. So under LANE_MODE you never call question, wherever this body or a reference says to. A gate that would ask writes the question, exactly as it would have been asked, to the checkpoint's pending_decisions[], and the turn ends with the lane status block defined in ../coordinate/references/lane-protocol.md: DECISIONS for an interview gate, BLOCKED for a BLOCKER gate. The same block with status: WORKING replaces the one-line wait status while research or review agents run, and the run ends with status: PLANNED. The coordinator reads nothing else. Gate outcomes are in the <auto_mode> table, the entry and resume rules in <lane_mode>. A PAUSE message can arrive mid-turn: start no new research or review agent, let the ones running report and record their output, write the checkpoint, and end with status: PAUSED; RESUME continues from the checkpoint's last_stage.