# Planning and Task Breakdown (planning-and-task-breakdown)

> Breaks work into small, ordered tasks with acceptance criteria and verification steps, saved as a plan document and task list.

- Category: [Task Breakdown](https://www.myskills.tools/en/categories/task-breakdown/)
- Source: Community · Addy Osmani
- Repository: https://github.com/addyosmani/agent-skills/tree/main/skills/planning-and-task-breakdown (commit 8300e1b)
- SKILL.md: https://github.com/addyosmani/agent-skills/blob/main/skills/planning-and-task-breakdown/SKILL.md
- Install command: `npx skills add addyosmani/agent-skills --skill planning-and-task-breakdown`
- License: MIT
- Compatible with: Claude Code, Codex, Cursor, Copilot, Gemini CLI
- Permissions: read-repo ✓, write-files ✓, shell ✗, network ✓
- Status: Scan passed
- A rule scan cannot catch every risk. Read this skill's SKILL.md and check its permissions before installing.

## Core rule

Every task must be small enough to implement, test and verify in one focused session, with explicit acceptance criteria.

## Execution Phases

1. **Enter plan mode** — In read-only mode, read the spec and relevant code, note patterns, dependencies, risks and unknowns; write no code.
2. **Map and slice** — Draw the dependency graph, order bottom-up, and slice vertically by complete feature path rather than by database, API and UI layers.
3. **Write tasks** — Give each task a description, acceptance criteria, verification, dependencies, likely files and size; split anything L or larger.
4. **Order and checkpoint** — Satisfy dependencies, put high-risk tasks early, and add a verification checkpoint every 2–3 tasks.
5. **Save and confirm** — Save to tasks/plan.md and tasks/todo.md (or the designated tracker), never overwriting an incomplete plan, and get human approval.

## Permissions (summarised from SKILL.md)

| Capability | Needed | Details |
|---|---|---|
| File writes | Limited | Writes only tasks/plan.md and the task list (default tasks/todo.md); no code during planning. |
| Command execution | Not required | Test and build commands are written into each task's verification, not run during planning. |
| Network outbound | Limited | Only when the project or user designates an external tracker (e.g. GitHub Issues, Jira, Linear), to create task items there. |

## SKILL.md frontmatter (YAML)

```yaml
---
name: planning-and-task-breakdown
description: Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
---
```

Home: https://www.myskills.tools/en/ · URL: https://www.myskills.tools/en/skills/planning-and-task-breakdown/