user-story-templates

Convert product requirements into As-a/I-want/So-that user stories with acceptance criteria.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill user-story-templates-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story-templates
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/agents/plugins/ai-pm-copilot/skills/user-story-templates
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill user-story-templates-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams avoid vague, implementation-heavy, or untestable requirements by providing ready-to-use user story formats and acceptance criteria patterns that make planning and delivery smoother.

Core Features & Use Cases

  • User story templates: Standard As-a/I-want/So-that story structure to keep requirements user-focused and outcome-driven.
  • Acceptance criteria formats: Given-When-Then, checklist, and MoSCoW options to ensure requirements are verifiable and cover error/edge cases.
  • Story splitting guidance: Practical patterns for breaking large stories into smaller vertical slices.
  • Story quality validation (INVEST): A checklist to confirm stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable.
  • Use cases: Requirement engineering, backlog refinement, sprint planning, and communicating clear expectations to development teams.

Quick Start

Use this skill to generate a user story and acceptance criteria for a feature you are planning, then verify it passes INVEST.

Frequently Asked Questions about user-story-templates

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

FAQPage Schema
How do I write user stories with testable acceptance criteria?

Writing user stories with testable acceptance criteria involves structuring requirements into As-a/I-want/So-that formats and applying Given-When-Then, checklists, or MoSCoW rules to ensure edge cases are verifiable during backlog refinement.

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

Splitting large user stories for sprint planning requires applying proven patterns to break oversized work into smaller vertical slices, then validating each slice against INVEST principles to ensure the stories remain estimable and testable.

When should I use Given-When-Then versus a checklist for acceptance criteria?

Given-When-Then is used for acceptance criteria when you need structured BDD-style verification for complex logic, while checklists are used for simpler feature requirements to ensure all conditions are clearly verified without overhead.

How does INVEST validation improve agile planning and requirement communication?

INVEST validation improves agile planning by checking that user stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable, which prevents vague requirements and ensures development teams receive clear, actionable work items.

Can I use these user story templates for technical debt and bug fixes?

These user story templates can be used for technical debt, bug fixes, spikes, and epic breakdowns by converting implementation-heavy requirements into clear, outcome-driven stories with verifiable acceptance criteria.

What are the limitations of using standard user story formats for requirement engineering?

Standard user story formats for requirement engineering become limiting when teams overly rely on templates without validating against INVEST principles, risking vague or untestable requirements if appropriate acceptance criteria formats are not selected.