defining-stories | story-driven | ClaudePluginHub

Skill

Community

defining-stories

From story-driven

0

Description

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.

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Supporting Assets

EPIC_TEMPLATE.md

STORY_TEMPLATE.md

Skill Content

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.

Links

GitHub Stats

0 forks

Updated 2 hours ago

Related Skills

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

From plugin-dev

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

From plugin-dev

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

From plugin-dev