Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
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
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
Submit your Claude Code skill and start earning
epx add davila7/claude-code-templates --skill writing-plansCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionwriting-plansExecute the skills CLI command in your project's root directory to begin installation:
epx add davila7/claude-code-templates --skill writing-plansFetches writing-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:
.cursor/skills/writing-plans
Restart Cursor to activate writing-plans. Access via /writing-plansin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
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.
grill-me
mattpocock/skills · Productivity · same category
nutritional-specialist
ailabs-393/ai-labs-claude-skills · Productivity · same category
premortem
parcadei/continuous-claude-v3 · Productivity · same category
write-a-prd
mattpocock/skills · Productivity · same category
clean-code-principles
asyrafhussin/agent-skills · Productivity · same category
web-accessibility
supercent-io/skills-template · Productivity · same category
We added writing-plans from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
writing-plans is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
writing-plans fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for writing-plans matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend writing-plans for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
writing-plans reduced setup friction for our internal harness; good balance of opinion and flexibility.
writing-plans fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in writing-plans — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: writing-plans is focused, and the summary matches what you get after install.
writing-plans is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 43