Defining Stories
Productivitydefining-storiesDefining 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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/design/defining-stories-kecbigmt-cc-plugins-0da31d9c/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/defining-stories, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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
- [ ] **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
date -u +"%Y%m%dT%H%M%S" # Generate timestamp
See STORY_TEMPLATE.md for structure.
Epic Documents
Directory: docs/stories/<YYYYMMDD>_<epic-name>/
File: <YYYYMMDDTHHMMSS>_<epic-name>.epic.md
See EPIC_TEMPLATE.md for structure.