Agent skill

defining-stories

Create user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features.

Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/defining-stories

SKILL.md

Defining Stories

Epic vs Story

Document Purpose When to Create
Epic Design document defining scope and technical approach Starting a larger feature
Story Incremental deliverable with acceptance criteria As needed during development

Agile approach: Stories emerge during development. Create each story when ready to implement.

User Story Format

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

Acceptance Criteria

markdown
- [ ] **Given** [precondition], **When** you [action], **Then** [expected result]
  • Focus on user-observable behavior
  • Include happy paths AND error cases
  • Leave checkboxes unchecked (PO checks them)

Verification Approach

Define how criteria will be verified:

Project Type Options
CLI Direct command execution
API curl/httpie, API testing tools
Web UI E2E tests, browser MCP tools
Mobile Device/emulator, MCP tools
Library Unit/integration tests

If MCP tools or skills for testing are available, use them. If unsure, ask PO.

Story Log

File: docs/stories/<YYYYMMDDTHHMMSS>_<name>.story.md

bash
date -u +"%Y%m%dT%H%M%S"  # Generate timestamp

Use the story-template skill for structure.

Epic Documents

Directory: docs/stories/<YYYYMMDD>_<epic-name>/ File: <YYYYMMDDTHHMMSS>_<epic-name>.epic.md

Use the epic-template skill for structure.

Expand your agent's capabilities with these related and highly-rated skills.

Didn't find tool you were looking for?

Be as detailed as possible for better results