flpbalada/fb-skills

user-story-fundamentals

Write clear user stories with user, capability, benefit, and testable acceptance criteria.

First seen May 4, 2026

Installation

$ npx skills add flpbalada/fb-skills --skill user-story-fundamentals

Summary

  • Write clear user stories with user, capability, benefit, and testable acceptance criteria.
  • Use when creating or improving backlog items, Given/When/Then criteria, INVEST checks, and user-centered requirements; avoid for roadmap hierarchy, broad requirement audits, or effort sizing.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from flpbalada/fb-skills · top by installs.

npx skills add flpbalada/fb-skills

Browse all from flpbalada/fb-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,952 B
  • docs SUMMARY.md 313 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 10 installs

SKILL.md

User Story Fundamentals

Goal

Describe who needs what and why. Make completion testable.

Story Format

As a [user type],
I want [capability],
so that [benefit].

Rules

  • Name a real user or actor.
  • Describe capability, not implementation.
  • State value in the so that clause.
  • Add acceptance criteria.
  • Keep stories small enough for one sprint.
  • Split stories that are too large, vague, or dependency-heavy.
  • Separate acceptance criteria from definition of done.

INVEST Check

  • Independent: can be delivered separately.
  • Negotiable: details can change.
  • Valuable: clear user or business value.
  • Estimable: team can size it.
  • Small: fits a sprint.
  • Testable: clear pass/fail criteria.

Acceptance Criteria

Use concrete Given/When/Then statements:

Given [context],
when [action],
then [outcome].

Cover:

  • Happy path.
  • Empty or missing data.
  • Invalid input.
  • Permission or role differences.
  • Error states.

Splitting Methods

  • Workflow step.
  • User role.
  • Data operation: create, read, update, delete.
  • Happy path then edge cases.
  • Platform or channel.
  • Permission level.
  • Release slice.

Resources

Output

As a [user],
I want [capability],
so that [benefit].

- Given [context], when [action], then [outcome].

- Dependencies:
- Non-goals:
- Estimate: