# Defining Stories

> Defining Stories is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Guides creation of user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features that need scope definition.

- Skill name: `defining-stories`
- Category: [Productivity](https://www.openparable.com/skill/productivity/1)
- Source: https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/design/defining-stories-kecbigmt-cc-plugins-0da31d9c/SKILL.md
- Repository: majiayu000/claude-skill-registry (498 GitHub stars when collected)

## 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
```

See [STORY_TEMPLATE.md](STORY_TEMPLATE.md) for structure.

## Epic Documents

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

See [EPIC_TEMPLATE.md](EPIC_TEMPLATE.md) for structure.

---

Source: https://www.openparable.com/skill/productivity/defining-stories (OpenParable). Cite the canonical URL above.
