task-planning

1# Task planning
2 
3Plan only as much as the work needs. If execution is authorized and the next step
4is small and clear, do it. A request for a plan alone does not require child tasks
5or a new approval gate.
6 
7Describe the intended outcome, relevant constraints, chosen approach, and how to
8verify success. Include uncertainties or decisions that affect execution. Use the
9user's preferred format; keep implementation steps within one owner's task unless
10another owner, useful parallel output, dependency, or independent review warrants
11separate work.
12 
13Save a requested plan as the issue document with key `plan`. Update its current
14revision instead of duplicating it, and link the saved document in your response.
15Use the native document tools when available; legacy agents follow the `paperclip`
16skill's document and planning API mechanics.
17 
18Respect planning mode and explicit approval requests. When approval is required,
19request confirmation of the latest plan revision and wait for that decision.
20After acceptance, execute cohesive work on the current ordinary task. Use
21`paperclip-converting-plans-to-tasks` when delegation is justified.