skills.rest
MrAlexisCord
MrAlexisCordCOMMUNITY
Explore all skills by this author →
GitHub

user-story-writing

Generate user stories with acceptance criteria in standard agile format.

Updated Mar 14, 2026
Search Tags:#requirements#product management#acceptance criteria#agile#user stories#scrum
One-click install
npx skills add https://github.com/MrAlexisCord/chatbot-prototype --skill user-story-writing-mralexiscord
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story-writing
Source: https://github.com/MrAlexisCord/chatbot-prototype/tree/main/.agents/skills/user-story-writing
Command: npx skills add https://github.com/MrAlexisCord/chatbot-prototype --skill user-story-writing-mralexiscord

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you write effective user stories with clear acceptance criteria, ensuring everyone understands requirements from the user's perspective.

Core Features & Use Cases

  • User Story Formulation: Guides you to write stories in the standard "As a... I want to... So that..." format.
  • Acceptance Criteria: Provides templates and examples for defining clear, testable acceptance criteria.
  • Use Case: When planning a new feature, use this Skill to draft user stories that clearly communicate the desired functionality and how to verify its completion to the development team.

Quick Start

Use the user-story-writing skill to generate a user story for a login feature.

Frequently Asked Questions about user-story-writing

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

FAQPage Schema
How do I write user stories with clear acceptance criteria for agile development?▼

Write user stories using the standard "As a... I want... So that..." format to capture requirements, then define clear, testable acceptance criteria to verify feature completion for agile development teams.

What is the INVEST criteria for user stories and when should I split them?▼

INVEST criteria ensures user stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. You should split large user stories into smaller, manageable development tasks to maintain agile development velocity.

How do I format acceptance criteria so developers can easily test feature requirements?▼

Format acceptance criteria using provided templates to establish clear, testable requirements. This approach ensures the development team understands the desired functionality and exactly how to verify its completion from a user perspective.

Can I use this approach to capture product management requirements for a Scrum team?▼

Yes, this approach captures product management requirements by formulating user stories from the user's perspective. It facilitates Scrum and agile development by providing clear, testable requirements for the development team.

What is the best way to structure a user story for a new feature login?▼

The best way to structure a user story is using the "As a [user], I want [action], so that [value]" format. This ensures the new feature login requirement clearly communicates desired functionality to developers.

Related Skills

Explore More Product & Management Skills→
mmartinsolivmmartinsoliv

prd

Create structured product requirements documents with user stories and success metrics.

Community
Intermediate
devCharuzudevCharuzu

agile-product-owner

Organize Agile backlog management and sprint execution with user stories and capacity planning.

Community
Advanced
dralgorhythmdralgorhythm
111

estimating-work

Estimate development effort using story points and T-shirt sizing.

Community
Intermediate
jellydnjellydn
114

ralph

Convert Markdown or text PRDs into Ralph's prd.json format.

Community
Intermediate