skills.rest
lintendo
lintendoCOMMUNITY
Explore all skills by this author →
GitHub

user-story-writing

Create user stories with acceptance criteria from product requirements.

152|32|Updated Dec 29, 2025
Search Tags:#agile#backlog#product-management#acceptance-criteria#story-writing#story-splitting#user-story-writing
One-click install
npx skills add https://github.com/lintendo/Axhub-Make --skill user-story-writing-lintendo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story-writing
Source: https://github.com/lintendo/Axhub-Make/tree/main/skills/third-party/user-story-writing
Command: npx skills add https://github.com/lintendo/Axhub-Make --skill user-story-writing-lintendo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write effective user stories that capture requirements from the user's perspective, helping teams avoid ambiguity and ensuring clear acceptance criteria to guide development and define done.

Core Features & Use Cases

  • Provides a canonical user-story template (As a, I want to, So that) to align product, design, and engineering.
  • Guides the creation of acceptance criteria and links to reference guides (story refinement, story splitting, story estimation) to improve backlog quality.
  • Supports backlog refinement, sprint planning, and feature scoping by producing concise, testable stories with actionable outcomes.

Quick Start

Create a user story for a feature using the As a / I want to / So that template and specify acceptance criteria.

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 backlog refinement?▼

Generate user stories with clear acceptance criteria by applying the As a / I want to / So that template to product requirements, ensuring concise, testable stories with actionable outcomes for sprint planning.

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

Split large user stories by referencing dedicated story splitting guides that decompose broad product requirements into smaller, ready-to-implement stories with distinct acceptance criteria.

How do I structure acceptance criteria to avoid ambiguity in agile story writing?▼

Structure acceptance criteria explicitly alongside the As a / I want to / So that template to eliminate ambiguity, aligning product and engineering teams on a clear, testable definition of done.

Can I use the user story template for feature scoping before sprint planning?▼

Yes, you can use the canonical user story template for feature scoping to transform early product requirements into concise, structured stories with actionable outcomes before backlog refinement.

When should I use story estimation guides during product management?▼

Use story estimation guides during backlog refinement after drafting user stories, applying them alongside story refinement practices to improve overall backlog quality and development accuracy.

Related Skills

Explore More Product & Management Skills→
runchr-comrunchr-com

user-stories

Generate user stories with 3 C's, INVEST criteria, and acceptance criteria.

Official
Intermediate
hoavdchoavdc
21

codexkit-backlog-refiner

Transform raw backlog items into INVEST-compliant user stories with acceptance criteria.

Community
Intermediate
yuyuxinliyuyuxinli
1

user-story-splitting

Split large user stories into smaller deliverable stories using eight patterns.

Official
Intermediate
letehahaletehaha
70

PRD Generator

Generate engineer-focused PRD documents with predefined sections and kebab-case filenames.

Community
Advanced