work-plan

Invoke the work-plan workflow by asking for a work plan before coding. The planner explores the repository in parallel, asks only questions the code cannot answer, waits for your explicit approval, then writes a decision-complete plan under docs/plans/.

CLEAR means you know the desired outcome, so the planner interviews only the surviving owner-decision forks. UNCLEAR means the outcome is fuzzy, so the planner researches best practices, adopts announced defaults, and runs the high-accuracy review automatically.

No. The planner is strictly read-only against product code and writes only plan artifacts under docs/plans/, including drafts, plans, and notepads. Execution always happens in a separate worker session started explicitly by the user.

Yes. The scaffold-plan.mjs script uses only node:fs, node:path, node:process, and node:url builtins, so it runs byte-identically under node and bun on macOS, Linux, and Windows with zero external dependencies.

The durable draft at docs/plans/drafts/<slug>.md records intent, review state, decisions, and the approval gate status. On a later turn the planner reads the draft and resumes from those fields instead of re-running exploration.

The review is required when you explicitly ask for high accuracy or deep review, or automatically on non-Trivial UNCLEAR requests. It runs one reviewer pass plus one independent advisor pass, capped at 5 convergence rounds with evidence-backed blocker criteria.