Batuta's onboarding and reconfiguration. Use when the user invokes /batuta:init, wants to set Batuta up in a project, or wants to change an existing setup (lanes, models, profile answers, project map).
Batuta's main entry point — the conducting cycle. Use when the user requests a code task that can be delegated (feature, bugfix, refactor, config), asks where or how something lives in the codebase (research — see "The scout"), or invokes /batuta. Classifies…
Pause Batuta work across sessions. Use when the user invokes /batuta:pause or says they are stopping and want to hand the current state off to a future session.
Resume paused Batuta work. Use when the user invokes /batuta:resume or asks to pick up where a previous session left off.
Batuta status. Use when the user invokes /batuta:status or asks what is in progress, what is done, or how delegated background tasks are going.
Batuta's on-demand verification. Use when the user invokes /batuta:review or asks to review a diff, an executor's work, or uncommitted changes.
Batuta's formal planning. Use when the user invokes /batuta:plan or when work will span sessions and needs an approvable, persistent plan.
Batuta routing. Use when the user invokes /batuta:route or wants to view or edit the complexity-to-executor routing table.