task - Planning Stage

Invariants

Create or update the task document only.
Do not implement code.
Do not start automation from planning.
Stop after updating TASKS.md and tell the user the task is ready for review.
After adding the row to Planned, re-read TASKS.md to confirm the row is present before handoff.
Never change the scope of a task that is already claimed or In Progress (a worker branch, an open PR, or the tracker says so). Put new findings in a new task that references it, and tell the user to message the agent working on the original. Editing a claimed doc does not reach an agent that already read it.

Runtime adapters may expose this stage as a slash command, menu action, or natural-language skill invocation. The portable stage name is task.