User Story
Productivityuser-storyUser Story is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Creates well-structured user stories for software development and project management. Use when the user asks to write, create, or format a user story, or needs to document requirements, features, or tasks in user story format.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/user-story/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/user-story, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
User Story Skill
Create clear, actionable user stories following industry best practices.
Guidelines
- Use the standard user story format: "As a [type of user], I want [goal] so that [reason/benefit]"
- Keep titles concise and descriptive
- Write a brief 1-2 sentence summary explaining the context
- Be concise - avoid over-doing it with too much detail
- Focus on user value and outcomes, not implementation details
Structure
Use the template provided in template.md to ensure consistency:
- Title: Brief, descriptive headline starting with "As a..."
- Summary: 1-2 sentences providing context
- Task List (optional): Use for highly technical, non-user-facing work
- Acceptance Criteria (optional): Use for user-facing stories to define what "done" looks like
Important: Stories typically have EITHER a task list OR acceptance criteria, not both. Choose based on the story type:
Best Practices
- Keep it simple: Don't over-engineer the story with unnecessary detail
- Make acceptance criteria specific and measurable (when included)
- Use "Given-When-Then" format sparingly and only when it adds clarity
- Keep stories focused on a single piece of value
- For task lists, list only essential implementation steps
- For acceptance criteria, list only what's needed to verify completion
Examples
User-Facing Story (Acceptance Criteria)
Title: As a user, I want to reset my password via email
Summary: Users who forget their passwords need a secure way to regain access to their accounts.
Acceptance Criteria:
- User can request password reset from login page
- System sends reset link to registered email
- Reset link expires after 24 hours
- User can set new password using valid link
Technical Story (Task List)
Title: As a developer, I want to upgrade the database schema
Summary: We need to migrate from the old schema to support new feature requirements.
Task List:
- Create migration script
- Test migration on staging environment
- Schedule maintenance window
- Execute migration on production
- Verify data integrity
Balanced Story (Both - Use Sparingly)
Title: As an admin, I want to export user data to CSV
Summary: Administrators need to extract user data for reporting and compliance purposes.
Task List:
- Implement CSV export endpoint
- Add data filtering options
Acceptance Criteria:
- Admin can select which fields to export
- System handles 10,000+ users
- File downloads automatically when ready
- Export includes timestamp and admin username in filename