name: tasked-phases description: Use when the user wants a spec turned into phased work with checklist tasks tracked by the tasked_phases tool, or when ongoing work should be tracked phase by phase.
Tasked Phases
Use the tasked_phases tool as the source of truth for the spec, phases, current focus, and checklist progress.
Workflow
- Clarify missing requirements when the spec is ambiguous.
- Save the accepted spec with
tasked_phasesusingset_spec. - Create or materially revise the plan with
replace_plan. - Keep phases small and tasks concrete enough to check off.
- Set the focus with
set_current_phaseand pass the targetphaseId. - Call
set_task_checkedimmediately after each checklist task is completed. - Use
set_phase_checkedto complete or reopen every task in a phase. The phase must already contain at least one task. - When every task is checked, treat the plan as closed. For unrelated work, call
clearto discard the plan, or callset_specimmediately followed byreplace_planto record a new spec and a new set of phases.
Successful mutations return one progress line; use get_status or
replace_plan for details. set_task_checked changes one task;
set_phase_checked changes every task in a phase.
Planning rules
- Prefer 3–7 phases unless the task is tiny.
- Each task should describe an observable outcome.
- Avoid vague tasks such as “work on this” or “finish implementation”.
- Keep the stored spec and plan concise and operational.
Tool guidance
- Use
get_statusbefore relying on remembered state or revising a long-running plan. - Use
replace_planfor a substantial restructuring; useadd_*,update_*, andremove_*for small changes. - Pass
phaseIdas the raw ID shown in brackets, without the brackets. The tool also accepts a complete phase label or a unique phase title when recovering from copied output. - Do not rely on prose alone for completion state; update the tool after each completed task.