
User Story Writer
Transform feature ideas into testable user stories with acceptance criteria
What You Can Do
You can take rough feature ideas, product specifications, or backlog items and transform them into independently valuable, testable user stories that teams can develop against immediately. The skill grounds each story in specific user personas, defines verifiable acceptance criteria, identifies edge cases and risks, and establishes clear out-of-scope boundaries to prevent scope creep. This creates a conversation contract between product, design, and engineering that eliminates ambiguity.
Features
writes stories from the perspective of specific user types with clear motivations and context
generates verifiable, testable conditions that are free of ambiguity
flags boundary conditions, security considerations, and integration points that could break the story
explicitly states what the story does NOT include to prevent scope creep
ensures each story delivers measurable user value without depending on other stories
highlights dependencies, technical risks, and assumptions that teams should validate
structures stories to be easily validated through acceptance tests
Example Output
Input: "We need to improve the search function"
Output:
User Story: As a content researcher, I want to filter search results by publication date so that I can find recent articles relevant to my current project without manually reviewing outdated sources.
Acceptance Criteria:
- Date filter dropdown appears on search results page
- User can select from: Last 7 days, Last 30 days, Last 90 days, Custom range
- Results are sorted by date (most recent first) when filter is applied
- Filter state persists when user navigates and returns to results
- "No results" message displays if filter matches zero items
Edge Cases:
- What happens if user selects a future date in custom range?
- How should system handle articles with missing/invalid publication dates?
- Performance impact if filtering 500k+ articles?
Out of Scope:
- Advanced search operators or boolean queries
- Saved search filters
- Natural language date parsing ("last Tuesday")
What's Included
- SKILL.md: Complete user story writing instruction file with activation contexts and workflows
- User Story Template: Pre-formatted markdown template with persona, narrative, acceptance criteria, edge cases, and out-of-scope sections
- Persona Definition Checklist: Guide for identifying and documenting user personas (role, goals, pain points, context)
- Acceptance Criteria Framework: Structured approach to writing testable, unambiguous criteria using Gherkin-style examples
- Scope Management Worksheet: Tool for defining story boundaries and preventing scope creep
Who It's For
- Product managers — decomposing feature requests into development-ready stories that prevent miscommunication
- Scrum masters and agile coaches — facilitating backlog refinement and ensuring stories meet definition of ready
- Engineering leads — translating vague requirements into concrete, testable acceptance criteria for teams
- UX/product designers — grounding user stories in behavioral context and user motivations
- QA and test engineers — identifying edge cases and generating test scenarios from acceptance criteria
Best For
- Converting feature requests into backlog items ready for sprint planning
- Decomposing large, vague epics into smaller independently-valuable stories
- Refining stories that lack clear acceptance criteria or testability
- Identifying and documenting scope boundaries to prevent mid-sprint creep
- Building conversation contracts between product, design, and engineering teams







