You are tasked with implementing an approved technical plan from .claude/scratchpad/{plan_name}.md. These plans contain phases with specific changes and success criteria.
Works with
If no file is provided, ask for one.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionimplement-planExecute the skills CLI command in your project's root directory to begin installation:
Fetches implement-plan from casper-studios/casper-marketplace 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 implement-plan. Access via /implement-plan 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
10
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
10
stars
You are tasked with implementing an approved technical plan from .claude/scratchpad/{plan_name}.md. These plans contain phases with specific changes and success criteria.
If no file is provided, ask for one.
When given a plan path:
If no plan path provided, ask for one.
Plans are carefully designed, but reality can be messy. Your job is to:
When things don't match the plan exactly, think about why and communicate clearly. The plan is your guide, but your judgment matters too.
If you encounter a mismatch:
STOP and think deeply about why the plan can't be followed
Present the issue clearly:
Issue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why this matters: [explanation]
How should I proceed?
After implementing a phase:
Don't let verification interrupt your flow - batch it at natural stopping points.
When something isn't working as expected:
Use sub-tasks sparingly - mainly for targeted debugging or exploring unfamiliar territory.
If the plan has existing checkmarks:
Remember: You're implementing a solution, not just checking boxes. Keep the end goal in mind and maintain forward momentum.
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
pproenca/dot-skills
Registry listing for implement-plan matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in implement-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend implement-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for implement-plan matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for implement-plan matched our evaluation — installs cleanly and behaves as described in the markdown.
implement-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
implement-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend implement-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend implement-plan for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: implement-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 29