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.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
EPIC_TEMPLATE.mdSTORY_TEMPLATE.md| 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.
As a [role], I want [capability], so that [benefit].
- [ ] **Given** [precondition], **When** you [action], **Then** [expected result]
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.
File: docs/stories/<YYYYMMDDTHHMMSS>_<name>.story.md
date -u +"%Y%m%dT%H%M%S" # Generate timestamp
See STORY_TEMPLATE.md for structure.
Directory: docs/stories/<YYYYMMDD>_<epic-name>/
File: <YYYYMMDDTHHMMSS>_<epic-name>.epic.md
See EPIC_TEMPLATE.md for structure.