
The planner skill breaks down implementation requests into detailed, phased plans with sprints and atomic tasks by first researching the codebase and clarifying requirements with the user, then retrieving relevant documentation and generating structured, actionable steps. It's designed for developers who need to organize complex features, bugs, or tasks into manageable, demoable increments with clear dependencies and validation methods. The skill solves the problem of vague or overwhelming project scope by forcing specificity at the task level and ensuring each sprint delivers testable, runnable progress.
$ npx -y skills add am-will/codex-skills --skill planner --agent claude-codeInstalls into .claude/skills of the current project.
Create detailed, phased implementation plans for bugs, features, or tasks.
Investigate the codebase:
Analyze the request:
Before doing ANY documentation search: clarify requirements with user. This will narrow and aid you in finding the right docs.
Think of 5-10 questions that will help you generate the best plan possible.
Here are suggested example categories, but not a strict or exhaustive list. You may ask anything helpful. Use best judgement & prioritize ambiguity and risk reduction:
Sponsors