skills.rest
ryan-nguyen-01
ryan-nguyen-01COMMUNITY
Explore all skills by this author →
GitHub

skill-role-write-user-stories

Convert ambiguous requirements into structured user stories with acceptance criteria.

4|Updated Mar 31, 2026
Search Tags:#epics#backlog#user-stories#business-analysis#acceptance-criteria#story-splitting#moscow
One-click install
npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill skill-role-write-user-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-role-write-user-stories
Source: https://github.com/ryan-nguyen-01/agent-platform/tree/main/.claude/skills/skill-role-write-user-stories
Command: npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill skill-role-write-user-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps business analysts and product teams convert vague requirements into well-structured, backlog-ready user stories with precise acceptance criteria and test scenarios.

Core Features & Use Cases

  • Provides templates for User Stories using the As a / I want / So that format, including Given/When/Then acceptance criteria.
  • Guidance on MoSCoW prioritization and a strong DoD to ensure testability and stakeholder alignment.
  • Techniques for splitting large epics into actionable stories that fit sprint planning.

Quick Start

Draft a single User Story example in the standard format: As a [role], I want to [action], So that [value], with Given/When/Then acceptance criteria.

Frequently Asked Questions about skill-role-write-user-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert vague requirements into ready-to-backlog user stories?▼

To convert vague requirements into user stories, use standard templates like As a / I want / So that, paired with Given/When/Then acceptance criteria to ensure clarity, testability, and backlog readiness.

What is the best way to split large epics into actionable user stories for sprint planning?▼

Splitting large epics into actionable user stories requires applying story splitting patterns to break down dependencies, ensuring each story fits sprint planning while maintaining Definition of Done coverage.

How does MoSCoW prioritization work when structuring a product backlog?▼

MoSCoW prioritization categorizes backlog items into Must have, Should have, Could have, and Won't have, ensuring stakeholder alignment and guiding the sequence of user story implementation.

How do I write acceptance criteria that ensure comprehensive test coverage for business analysis?▼

Acceptance criteria ensure test coverage by using the Given/When/Then format, enforcing a strong Definition of Done to validate that user stories meet stakeholder expectations and testability standards.

Can I use standard user story templates for complex business analysis workstreams?▼

Yes, standard user story templates enforce consistency across complex business analysis workstreams by structuring epics, dependencies, and MoSCoW prioritization into clear, testable deliverables.

Related Skills

Explore More Product & Management Skills→
deanpetersdeanpeters
6.4k

roadmap-planning

Plan strategic roadmaps from dispersed inputs into quarterly epics.

Community
Intermediate
nashirabbashnashirabbash

task-planning

Break down features into INVEST-based user stories and backlog tasks.

Community
Intermediate
michsindlingermichsindlinger
1

backlog-organization

Organize product backlogs with MoSCoW prioritization and sprint planning.

Community
Intermediate
bychrisrbychrisr

aiox-po

Manage product backlogs and user story lifecycles with automated validation and prioritization.

Community
Advanced