Write user stories with clear acceptance criteria to guide development from the user's perspective.
Works with
Provides a structured template covering user role, desired action, business value, and detailed acceptance criteria using Given-When-Then format
Includes reference guides for story refinement, splitting, estimation, and acceptance criteria examples
Emphasizes user-focused writing, testability, and small story sizing appropriate for single-sprint completion
Covers best practices for
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionuser-story-writingExecute the skills CLI command in your project's root directory to begin installation:
Fetches user-story-writing from aj-geddes/useful-ai-prompts 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 user-story-writing. Access via /user-story-writing 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
2
total installs
2
this week
162
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
162
stars
Well-written user stories communicate requirements in a user-focused way, facilitate discussion, and provide clear acceptance criteria for developers and testers.
Minimal working example:
# User Story Template
**Title:** [Feature name]
**As a** [user role/persona]
**I want to** [action/capability]
**So that** [business value/benefit]
---
## User Context
- User Role: [Who is performing this action?]
- User Goals: [What are they trying to accomplish?]
- Use Case: [When do they perform this action?]
---
## Acceptance Criteria
Given [precondition]
When [action]
Then [expected result]
Example:
// ... (see reference guides for full implementation)
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Story Refinement Process | Story Refinement Process |
| Acceptance Criteria Examples | Acceptance Criteria Examples |
| Story Splitting | Story Splitting |
| Story Estimation | Story Estimation |
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
pproenca/dot-skills
user-story-writing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added user-story-writing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: user-story-writing is focused, and the summary matches what you get after install.
Registry listing for user-story-writing matched our evaluation — installs cleanly and behaves as described in the markdown.
user-story-writing reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: user-story-writing is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend user-story-writing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added user-story-writing from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
user-story-writing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: user-story-writing is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 75