Index of every page on this site: llms.txt
All skills
am-will avatar

/planner

@9f954c3
by am.willam-will/codex-skills1k stars
60
Run it yourself

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

Use this Skill: https://skilld.dev/gh/am-will/codex-skills/planner

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈104 tokens for metadata: the name and description. ≈965 when used: this file.

Description uses 5.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈416 characters, or 5.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Planner Agent

Create detailed, phased implementation plans for bugs, features, or tasks.

Process

Phase 0: Research

  1. Investigate the codebase:

    • Architecture and patterns
    • Similar existing implementations
    • Dependencies and frameworks
    • Related components
  2. Analyze the request:

    • Core requirements
    • Challenges & edge cases
    • Security/performance/UX considerations

Phase 1: Clarify Requirements

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:

  1. Goals & success criteria
  2. Scope & non‑goals
  3. Users & core workflows
  4. Platforms & environments
  5. Tech constraints
  6. Data & integrations
  7. Auth & permissions
  8. Performance & reliability
  9. Testing & validation
  10. Ask any helpful question

Phase 2: Retrieve Documentation

When the plan involves any external library, API, framework, or service, use the Context7 skill to fetch the latest official docs before drafting tasks. This ensures version‑accurate steps, correct parameters, and current best practices. If no external dependencies apply, skip this phase.

Phase 3: Create Plan

Structure
  • Overview: Brief summary and approach
  • Sprints: Logical phases that build on each other
  • Tasks: Specific, actionable items within sprints
Sprint Requirements

Each sprint must:

  • Result in demoable, runnable, testable increment
  • Build on prior sprint work
  • Include demo/verification checklist
Task Requirements

Each task must be:

  • Atomic and committable (small, independent)
  • Specific with clear inputs/outputs
  • Independently testable
  • Include file paths when relevant
  • Include dependencies for parallel execution
  • Include tests or validation method

Bad: "Implement Google OAuth" Good:

  • "Add Google OAuth config to env variables"
  • "Install passport-google-oauth20 package"
  • "Create OAuth callback route in src/routes/auth.ts"
  • "Add Google sign-in button to login UI"

Phase 3: Save

Save the file

Generate filename from request:

  1. Extract keywords
  2. Convert to kebab-case
  3. Add -plan.md suffix

Examples:

  • "fix xyz bug" → xyz-bug-plan.md

Phase 4: Gotchas

AFTER it is saved. Identify potential issues & edge cases in plan. Address proactively. Where could smth go wrong? What about the plan is ambiguous? Missing step, dependency, or pitfall?

If any gotchas found, stop & ask up to 3 more questions. (either w/ request_user_input or directly)

Refine the plan if any additional useful info is provided.

Plan Template

# Plan: [Task Name]

**Generated**: [Date]
**Estimated Complexity**: [Low/Medium/High]

## Overview
[Summary of task and approach]

## Prerequisites
- [Dependencies or requirements]
- [Tools, libraries, access needed]

## Sprint 1: [Name]
**Goal**: [What this accomplishes]
**Demo/Validation**:
- [How to run/demo]
- [What to verify]

### Task 1.1: [Name]
- **Location**: [File paths]
- **Description**: [What to do]
- **Dependencies**: [Previous tasks]
- **Acceptance Criteria**:
  - [Specific criteria]
- **Validation**:
  - [Tests or verification]

### Task 1.2: [Name]
[...]

## Sprint 2: [Name]
[...]

## Testing Strategy
- [How to test]
- [What to verify per sprint]

## Potential Risks & Gotchas
- [What could go wrong]
- [Mitigation strategies]

## Rollback Plan
- [How to undo if needed]

Important

  • Think about full lifecycle: implementation, testing, deployment
  • Consider non-functional requirements
  • Show user summary and file path when done
  • Do NOT implement - only create the plan

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill acts as a project planner to generate implementation steps. It is generally safe but carries a minor risk related to processing external data which could potentially influence its output.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9f954c3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 10 months ago
  • Documentation
  • planning
  • project-management
  • tasks
  • sprints
  • implementation
  • requirements

README badge

README badge for am-will/codex-skills/planner

Creates phased implementation plans with sprints and atomic tasks by first researching the codebase and clarifying requirements, then fetching relevant documentation before structuring deliverables. Useful for breaking down features, bugs, or refactors into independently committable work units with clear acceptance criteria and validation methods.

Generated from the current SKILL.md.

Does this skill ask clarifying questions before creating a plan?
Yes. The skill requires Phase 1 to clarify requirements with the user by asking 5-10 questions across categories like goals, scope, tech constraints, and testing before researching documentation or drafting tasks.
Will this skill fetch documentation for external libraries and frameworks?
Yes. In Phase 2, the skill uses the Context7 skill to retrieve official documentation for any external libraries, APIs, frameworks, or services involved in the plan to ensure version-accurate steps and current best practices.
What format does the generated plan use?
The plan uses a sprint-based structure with an overview, prerequisites, multiple sprints (each with a goal and demo checklist), and atomic tasks with file paths, dependencies, acceptance criteria, and validation steps.
Does this skill actually implement the plan or just create it?
It only creates the plan. The skill explicitly does not implement—it generates a detailed, phased breakdown saved to a markdown file for you to execute.
What happens if the skill identifies gaps or risks in the plan?
In Phase 4, the skill identifies potential gotchas and edge cases. If issues are found, it stops and asks up to 3 additional clarifying questions to refine the plan.

Generated from the current SKILL.md. These answers refresh after source changes.