defining-user-stories | story | ClaudePluginHub

Skill

Community

defining-user-stories

0

Description

Guides creation of user stories and epics with acceptance criteria. Use when defining new features, writing Given-When-Then criteria, creating story logs, or breaking down large features into epics and stories.

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 User Stories

User Story Format

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

Guidelines:

Keep scope minimal but meaningful
Focus on user-visible behavior, not implementation
One story = one independently deliverable increment

Acceptance Criteria (Given-When-Then)

- [ ] **Given** [precondition], **When** you [action], **Then** [expected result]

Guidelines:

Focus on user-observable behavior
Include happy paths AND error cases
Leave checkboxes unchecked (product owner checks them)

Story Log Creation

File Naming

UTC timestamp format: <YYYYMMDDTHHMMSS>_<story-name>.story.md

date -u +"%Y%m%dT%H%M%S"

Location

Epic-related: docs/stories/<YYYYMMDD>_<epic-name>/<timestamp>_<story-name>.story.md
Standalone: docs/stories/<timestamp>_<story-name>.story.md

Template

See STORY_TEMPLATE.md for complete story log structure.

Epic Documents

For multi-story features:

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

See EPIC_TEMPLATE.md for epic structure.

Example

### User Story
**As a CLI user, I want to initialize my workspace as a Git repository,
so that I can sync my notes to GitHub.**

### Acceptance Criteria

#### 1. Initialization
- [ ] **Given** a workspace without Git, **When** you run `sync init <url>`,
      **Then** a Git repository is initialized

#### 2. Error Cases
- [ ] **Given** an invalid URL, **When** you run `sync init <url>`,
      **Then** an error message explains the problem

Links

GitHub Stats

0 forks

Updated 6 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