Planning
Skill huzaifa525/claude-code-optimizer/templates/.claude/skills/planning
Optimize Claude Code token usage — 22 skills, 8 hooks, 6 rules. One npm install. Zero manual steps. Cut costs by 67%.
npx -y skills add huzaifa525/claude-code-optimizer --skill planningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a task requires 5+ steps, multiple file changes, or cross-session progress tracking. Auto-activates for complex multi-step work.
SKILL.md
1.5 KB, as published. Nobody here has run it
When working on a complex task, create and maintain a persistent plan in task_plan.md at the project root.
When to Activate
- Task requires 5+ tool calls or file changes
- Multiple files need to be created or modified
- Task has dependencies between steps
- User explicitly asks to plan
Plan Format
Create task_plan.md with this structure:
# Task: [description]
## Status: In Progress | Completed | Blocked
## Steps
- [x] Step 1: [completed step]
- [ ] Step 2: [current step] ← CURRENT
- [ ] Step 3: [next step]
- [ ] Step 4: [future step]
## Key Files
- [file] → [what needs to change]
## Decisions Made
- [decision and why]
## Blockers
- [any blockers]
Rules
- Create plan BEFORE starting work — write task_plan.md first
- Update after each step — mark completed, move CURRENT marker
- Track decisions — record why you chose an approach
- Note blockers — if stuck, write it down
- Read plan on resume — if task_plan.md exists, read it first to continue where you left off
- Delete on completion — remove task_plan.md when all steps are done
On Session Resume
If task_plan.md exists:
- Read it
- Find the CURRENT step
- Continue from there
- Update progress as you go