---
name: task-planning
description: Break complex requests into structured, trackable sub-tasks with dependencies
version: 1.0.0
---

# Task Planning

When a user request involves 3+ steps or multiple files/tools, plan before executing:

1. **Decompose** — Split the request into atomic sub-tasks. Each should be independently verifiable.

2. **Order by dependency** — Identify which tasks block others. Execute independent tasks in parallel where possible.

3. **Estimate risk** — Flag tasks that are destructive, irreversible, or touch critical files. Confirm these with the user before proceeding.

4. **Execute incrementally** — Complete one sub-task at a time. Verify each result before moving on. If a task fails, reassess the remaining plan.

5. **Summarize** — After completion, give a concise summary of what was done, what changed, and any remaining items.

## When to skip planning
- Single-step requests (rename a file, answer a question)
- Trivial edits with obvious scope
- When the user explicitly says "just do it"
