Plan

Skill claude-world/director-mode-lite/skills/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.From its SKILL.md

Install

npx -y skills add claude-world/director-mode-lite --skill plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.3 KB, 275 tokens by cl100k_base, as published. Nobody here has run it

Task Planning

Create a detailed execution plan for the current task.

Process

Analyze Requirements
- What is the goal?
- What are the constraints?
- What resources are available?
Break Down Tasks
- Decompose into specific, actionable steps
- Each task should be completable independently
- Estimate relative complexity (small/medium/large)
Create Task List
- Use TodoWrite tool to track progress
- Mark priorities and dependencies
- Keep tasks granular
Identify Risks
- What could go wrong?
- What are the unknowns?
- What needs clarification?

Task Template

## 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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most plan spec skills give in 275 tokens

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

Ask one question at a timein 73 of 1360
Write the spec using the templatein 22 of 1360
Ask clarifying questions if neededin 19 of 1360, across 18 files
Wait for user confirmation before proceedingin 19 of 1360
Save plans to the plans directoryin 17 of 1360, across 13 files
Check for product marketing context firstin 16 of 1360, across 5 files
Read the plan file completelyin 16 of 1360
Order tasks by dependencyin 16 of 1360
Gather context from the conversationin 15 of 1360, across 9 files
Explore the codebase instead of askingin 15 of 1360, across 13 files
Wait for explicit user approvalin 14 of 1360, across 13 files
Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

Estimate relative complexity
Mark priorities and dependencies
Keep tasks granular and small
Identify risks and unknowns early
Update plan as you learn more

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.