Claude-code-optimizer plan
Use when the user wants to plan a feature, design an implementation approach, or break down a complex task before coding.
install
source · Clone the upstream repo
git clone https://github.com/huzaifa525/claude-code-optimizer
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/huzaifa525/claude-code-optimizer "$T" && mkdir -p ~/.claude/skills && cp -r "$T/templates/.claude/skills/plan" ~/.claude/skills/huzaifa525-claude-code-optimizer-plan && rm -rf "$T"
manifest:
templates/.claude/skills/plan/SKILL.mdsource content
Create an implementation plan for: $ARGUMENTS
Steps
-
Understand the requirement — break down what needs to be built
-
Explore the codebase — find related code, patterns, and conventions
-
Identify all changes needed:
- New files to create
- Existing files to modify
- Tests to add
- Config changes
-
Map dependencies — what must be done before what
-
Output structured plan:
<!-- Skill by Huzefa Nalkheda Wala | github.com/huzaifa525 | claude-code-optimizer -->## Implementation Plan: [feature] ### Overview [1-2 sentence description of what will be built] ### Tasks #### Phase 1: [Foundation] - [ ] Task 1: [description] - Files: [file1, file2] - Pattern: follow [existing-file] as reference - [ ] Task 2: [description] - Files: [file1] - Depends on: Task 1 #### Phase 2: [Core Logic] - [ ] Task 3: [description] - Files: [file1, file2, file3] - Depends on: Task 1, Task 2 #### Phase 3: [Testing & Polish] - [ ] Task 4: Write tests - Files: [test files] - Depends on: Phase 2 - [ ] Task 5: Update docs - Files: [CLAUDE.md, README] ### Files Map | File | Action | Purpose | |------|--------|---------| | [path] | Create/Modify | [what changes] | ### Reference Code - [existing-file] → follow this pattern for [X] - [existing-file] → follow this pattern for [Y] ### Risks - [potential issues and mitigations] ### Estimated Scope - [X] files to create - [Y] files to modify - [Z] tests to add