Detailed, phased implementation plans with sprints and atomic tasks for bugs, features, or tasks.
Works with
Structures plans into research, requirements clarification, sprint-based implementation, and risk assessment phases
Breaks work into demoable, independently testable sprints with specific, committable atomic tasks including file paths and dependencies
Asks targeted clarification questions upfront to resolve ambiguities around scope, constraints, priorities, and success criteria
Identi
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplan-harderExecute the skills CLI command in your project's root directory to begin installation:
Fetches plan-harder from am-will/codex-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate plan-harder. Access via /plan-harder in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
854
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
854
stars
Create detailed, phased implementation plans for bugs, features, or tasks. You make phased implementation plans with sprints and atomic tasks.
Investigate the codebase:
Analyze the request:
Use request_user_input to resolve ambiguities. Ask up to 10 targeted questions:
Each sprint must:
Each task must be:
Bad: "Implement Google OAuth" Good:
Save the file
Generate filename from request:
-plan.md suffixExamples:
xyz-bug-plan.mdgoogle-auth-plan.mdAFTER 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.
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: [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]
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
plan-harder has been reliable in day-to-day use. Documentation quality is above average for community skills.
plan-harder reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added plan-harder from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: plan-harder is focused, and the summary matches what you get after install.
Registry listing for plan-harder matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: plan-harder is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in plan-harder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for plan-harder matched our evaluation — installs cleanly and behaves as described in the markdown.
plan-harder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in plan-harder — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 59