Task plan

Use the smallest record that makes the work clear. Follow the user's requested format and existing project practice. A short task can use a few conversational steps; a task spanning sessions may need a saved plan.

Choose the medium

• Reuse an existing plan or the project's chosen record location.
• When a new file is useful and writing is permitted, use a descriptive name in an appropriate project directory. tasks/<task>.md is one option, not a requirement.
• Without writable files, return the plan as text and identify it as unsaved.
• Leave tracking and ignore policy unchanged unless the user or project calls for a change. Do not assume a plan must be private, ignored, or committed.
• Do not require Git, a branch, a pull request, or a formal specification. If a spec is requested or already exists, link to it instead of replacing it.

Record what matters

Use assets/plan-template.md when helpful. Keep only applicable sections: