Plan Tasks

Purpose and state boundary

Build a causal strategy before execution, then track only work the user explicitly approves. Treat $ARGUMENTS as the task when present; otherwise use the current request and relevant conversation context.

There are two phases:

1. Planning: inspect only read-only context, produce DRAFT or READY_FOR_REVIEW, then stop.
2. Approved execution: begin only after the user explicitly approves the current plan or named A-* actions; create or update a TASK/ tracker and execute only inside that scope.

During planning, never edit target files, create a tracker, run mutating commands, publish, deploy, commit, send an external message, or take an irreversible action. allowed-tools pre-approves read tools; it is not a security sandbox. Continue to obey Claude Code permissions, project instructions, protected paths, privacy rules, and the user's authorization.

Parse inputs and load only needed knowledge

Accept an optional override in the task text:

• --modules M-03,M-07 adds requested modules.
• --exclude M-04 requests removal of conditional modules.