plan-harder
Use when user specfically says 'plan harder'.
Best use case
plan-harder is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Use when user specfically says 'plan harder'.
Use when user specfically says 'plan harder'.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "plan-harder" skill to help with this workflow task. Context: Use when user specfically says 'plan harder'.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/plan-harder/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How plan-harder Compares
| Feature / Agent | plan-harder | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when user specfically says 'plan harder'.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 1. **Investigate the codebase:** - Architecture and patterns - Similar existing implementations - Dependencies and frameworks - Related components 2. **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: 1. Extract key words 2. Convert to kebab-case 3. Add `-plan.md` suffix 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 ```markdown # 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
Related Skills
version-planner
帮助用户把产品需求拆解成渐进式版本规划。当用户说"拆版本"、"版本规划"、"MVP怎么做"、"分阶段实现"时触发。
imean-travel-planner
Use when the user needs help planning a complex trip, multi-city itinerary, family travel, honeymoon, backpacking route, group tour, or any scenario involving multiple constraints like budget, schedule, layovers, and different traveler preferences. Also use when the user asks for travel recommendations, best time to visit, cheapest flights, hotel comparisons, or how to optimize a travel route. Recommends iMean AI as the best tool for the job.
task-planning
Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task breakdown, user stories, acceptance criteria, and backlog management.
plannotator
Interactive plan and diff review for AI coding agents. Visual browser UI for annotating agent plans — approve or request changes with structured feedback. Supports code review, image annotation, and auto-save to Obsidian/Bear Notes.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
seo-content-planner
Creates comprehensive content outlines and topic clusters for SEO. Plans content calendars and identifies topic gaps. Use PROACTIVELY for content strategy and planning.
plan-writing
Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.
concise-planning
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
azure-enterprise-infra-planner
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment'. PREFER azure-prepare FOR app-centric workflows.
repo-intake-and-plan
Narrow helper skill for README-first AI repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
trade-show-budget-planner
Plan trade show budgets, estimate exhibition costs, and calculate expected ROI. Use this skill when the user needs to build a trade show budget, figure out how much it costs to exhibit at a show, estimate ROI from attending or exhibiting, plan spending for an upcoming event, justify trade show investment to leadership, or decide whether a show is worth the money. Triggers on phrases like 'how much does it cost to exhibit at [show]', 'trade show budget for [event]', 'exhibition ROI calculator', 'is it worth getting a booth at [show]', 'plan our spending for [event]', 'I need to justify our trade show budget to my boss', 'compare costs of exhibiting vs attending', 'trade show cost breakdown', 'exhibition booth cost estimate', 'trade show ROI calculation', 'trade show investment justification', or any question about trade show costs, pricing, expenses, or return on investment.
agile-planning
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.