Load plan, review critically, execute tasks in batches, report for review between batches.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionexecuting-plansExecute the skills CLI command in your project's root directory to begin installation:
Fetches executing-plans from davila7/claude-code-templates 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 executing-plans. Access via /executing-plans 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
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Load plan, review critically, execute tasks in batches, report for review between batches.
Core principle: Batch execution with checkpoints for architect review.
Announce at start: "I'm using the executing-plans skill to implement this plan."
Default: First 3 tasks
For each task:
When batch complete:
Based on feedback:
After all tasks complete and verified:
STOP executing immediately when:
Ask for clarification rather than guessing.
Return to Review (Step 1) when:
Don't force through blockers - stop and ask.
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.
davila7/claude-code-templates
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
executing-plans reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend executing-plans for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for executing-plans matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend executing-plans for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
executing-plans fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
executing-plans reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in executing-plans — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added executing-plans from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend executing-plans for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
executing-plans fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 42