- Installs
- 1.2K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/am-will/codex-skills --skill plan-harder- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads plan-harder automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Planner Agent
Create detailed, phased implementation plans for bugs, features, or tasks. You make phased implementation plans with sprints and atomic tasks.
Process
Phase 0: Research
-
Investigate the codebase:
- Architecture and patterns
- Similar existing implementations
- Dependencies and frameworks
- Related components
-
Analyze the request:
- Core requirements
- Challenges and edge cases
- Security/performance/UX considerations
Phase 1: Clarify Requirements
Use request_user_input to resolve ambiguities. Ask up to 10 targeted questions:
- Scope boundaries (in/out of scope)
- Technology/architectural constraints
- Priorities (critical vs nice-to-have)
- Edge case handling
- Success criteria
Phase 2: 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:
- Extract key words
- Convert to kebab-case
- Add
-plan.mdsuffix
Examples:
- "fix xyz bug" →
xyz-bug-plan.md - "implement google auth" →
google-auth-plan.md
Phase 4: Gotchas
AFTER it is saved. Identify potential issues and edge cases in the plan. Address them proactively. Where could something go wrong? What about the plan is ambiguous? Is there a missing step, dependency, or pitfall?
Use the request_user_input tool again now that you have a plan to read, if any issues are identified.
Update the plan if you have improvements.
Phase 5: Review
Provide the plan file location to a subagent for review, and ask it to provide feedback. Provide it useful context so it can make sound decisions. Explicitly tell it not to ask any questions. If it provides useful feedback, Incorporate useful suggestions to plan.
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]
- **Complexity**: [1-10]
- **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
FAQ
What does the plan-harder skill do?
Use when user specfically says 'plan harder'.
How do I install plan-harder?
Run npx skills add https://github.com/am-will/codex-skills --skill plan-harder in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/plan-harder/ (personal) or .claude/skills/plan-harder/ (project).
Which AI agents can use plan-harder?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is plan-harder safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains plan-harder?
It is published by am-will in am-will/codex-skills. It has 1,163 recorded installs.
More from am-will/codex-skills
frontend-design
am-will/codex-skills
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
frontend responsive design standards
am-will/codex-skills
Build responsive, mobile-first layouts using fluid containers, flexible units, media queries, and touch-friendly design that works across all screen sizes. Use this skill when creating or modifying UI layouts, responsive grids, breakpoint styles, mobile navigation, or any interface that needs to adapt to different screen sizes. Apply when working with responsive CSS, media queries, viewport settings, flexbox/grid layouts, mobile-first styling, breakpoint definitions (mobile, tablet, desktop), touch target sizing, relative units (rem, em, %), image optimization for different screens, or testing layouts across multiple devices. Use for any task involving multi-device support, responsive design patterns, or adaptive layouts.
context7
am-will/codex-skills
Fetch up-to-date library documentation via Context7 CLI. Use PROACTIVELY when: (1) Working with ANY external library (React, Next.js, Supabase, etc.) (2) User asks about library APIs, patterns, or best practices (3) Implementing features that rely on third-party packages (4) Debugging library-specific issues (5) Need current documentation beyond training data cutoff (6) AND MOST IMPORTANTLY, when you are installing dependencies, libraries, or frameworks you should ALWAYS check the docs to see what the latest versions are. Do not rely on outdated knowledge. Always prefer this over guessing library APIs or using outdated knowledge.
planner
am-will/codex-skills
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.
read-github
am-will/codex-skills
Read and search GitHub repository documentation via gitmcp.io MCP service. WHEN TO USE: - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
parallel-task
am-will/codex-skills
Only to be triggered by explicit /parallel-task commands.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.