plan
/plan
Break a complex task into an ordered, dependency-aware task list with estimates and verification steps. Use when a request spans multiple components or days, before starting large features, or when the user runs /plan.
- Author
- claude-world ↗
- Repository
- director-mode-lite ↗
- Licence
- MIT
- Last repository change
- 21.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Break a complex task into an ordered, dependency-aware task list with estimates and verification steps. Use when a request spans multiple components or days, before starting large features, or when the user runs /plan.
Original author description
Break a complex task into an ordered, dependency-aware task list with estimates and verification steps. Use when a request spans multiple components or days, before starting large features, or when the user runs /plan.
How it works
- Process
- Task Template
- Guidelines
SKILL.md preview
---
name: plan
description: Break a complex task into an ordered, dependency-aware task list with estimates and verification steps. Use when a request spans multiple components or days, before starting large features, or when the user runs /plan.
user-invocable: true
---
# Task Planning
Create a detailed execution plan for the current task.
## Process
1. **Analyze Requirements**
- What is the goal?
- What are the constraints?
- What resources are available?
2. **Break Down Tasks**
- Decompose into specific, actionable steps
- Each task should be completable independently
- Estimate relative complexity (small/medium/large)
3. **Create Task List**
- Track progress in the plan's checklist (use a task tool such as
TodoWrite only when the active CLI and model offer it)
- Mark priorities and dependencies
- Keep tasks granular
4. **Identify Risks**
- What could go wrong?
- What are the unknowns?
- What needs clarification?
---
## Task Template
```markdown
## Task: [Task Name]
### Goal
[What this task achieves]
### Steps
1. [ ] [Step 1]
2. [ ] [Step 2]
3. [ ] [Step 3]
### Dependencies
- Requires: [other tasks]
- Blocks: [dependent tasks]
### Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
```
---
## Guidelines
- Keep tasks small (completable in one session)
- Be specific about acceptance criteria
- Identify dependencies early
- Update plan as you learn more
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · claude-world/director-mode-lite | 100 | MIT |
| mlophez/polix-ai | 100 | Apache-2.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| duronext/jig | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| rjmurillo/ai-agents | 100 | MIT |
| xoai/sage | 100 | MIT |
| JoDi-27/JoDi-SDD | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2ec3f174b207 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100planning-and-task-breakdown
Decompose specs into small, ordered tasks with acceptance criteria and verification steps. Use when you have requirements and need an implementable plan or task list. Triggers: "break down tasks", "implementation plan", "task breakdown", "plan mode". - 100breakdown
Use when a feature with a spec and a plan needs its ordered task list: \"break this into tasks\", \"make the task list\", \"what are the steps to build this?\", \"generate tasks.md\", a feature folder with plan.md and no tasks.md, or a task list made stale by a spec or plan… - 100project-planner
Break a large or ambiguous project into a dependency-ordered task list with a Mermaid dependency diagram and critical-path analysis, using the Task tool suite (TaskCreate/TaskUpdate/TaskList). Trigger on "plan this project", "break this into tasks", "what's the dependency… - 100plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work. - 84bf-rebuild-plan
Use when brownfield analysis is done and the app must become an ordered rebuild backlog. - 98plan-to-tickets
Use when a large plan, PRD, feature, refactor, research plan, or multi-step coding task must be split into small ready-for-agent tickets with acceptance criteria, verification commands, blockers, and vertical tracer-bullet slices. Do not use for small tasks that should be…