ReddRadar
Agent skill
user-story
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/user-story
SKILL.md
Document Intelligence
This skill supports three modes: Create, Update, and Find.
Mode Detection
| Signal | Mode | Confidence |
|---|---|---|
| "update", "revise", "modify" in input | UPDATE | 100% |
File path provided (@path/to/story.md) |
UPDATE | 100% |
Story ID mentioned (US-2026-001) |
UPDATE | 100% |
| "create", "new", "draft" in input | CREATE | 100% |
| "find", "search", "list stories" | FIND | 100% |
| "the story", "the user story" | UPDATE | 85% |
| Just story description | CREATE | 60% |
Threshold: ≥85% auto-proceed | 70-84% state assumption | <70% ask user
Mode Behaviors
CREATE: Generate complete new user story using template below.
UPDATE:
- Read existing story (search if path not provided)
- Preserve unchanged sections exactly
- Update only sections mentioned by user
- Show diff summary: "Updated: [sections]. Unchanged: [sections]."
- Update status and metadata
FIND:
- Search paths below for user stories
- Present results: title, path, status, summary
- Ask: "Update one of these, or create new?"
Search Locations for User Stories
stories/backlog/requirements/stories/epics/
Write a User Story with acceptance criteria.
V2V Phase
Phase 3: Strategic Commitments - User stories are the atomic unit of requirements commitment.
Prerequisites: Feature spec or PRD with scope defined Outputs used by: Sprint planning, engineering implementation, QA verification
Output Structure
# User Story: [Brief Title]
**Story ID**: US-[YYYY]-[NNN]
**Epic**: [Parent epic]
**Owner**: [PM Name]
**Priority**: Must Have / Should Have / Nice to Have
**Status**: Draft / Ready / In Progress / Done
## Story
**As a** [user type/persona]
**I want to** [action/capability]
**So that** [benefit/value]
## Context
**Why This Matters**: [Business/user context]
**Current State**: [How it works today or doesn't exist]
**Desired State**: [How it should work]
## Acceptance Criteria
### Criterion 1: [Name]
**Given** [precondition/context]
**When** [action taken]
**Then** [expected result]
### Criterion 2: [Name]
**Given** [precondition/context]
**When** [action taken]
**Then** [expected result]
### Criterion 3: [Name]
**Given** [precondition/context]
**When** [action taken]
**Then** [expected result]
## Edge Cases
| Scenario | Expected Behavior |
|----------|-------------------|
| [Edge case 1] | [Behavior] |
| [Edge case 2] | [Behavior] |
| [Edge case 3] | [Behavior] |
## Error Handling
| Error Condition | User Message | System Behavior |
|-----------------|--------------|-----------------|
| [Error 1] | [Message] | [Behavior] |
| [Error 2] | [Message] | [Behavior] |
## Dependencies
- [Dependency 1]
- [Dependency 2]
## Design Notes
**UI/UX Considerations**: [Design notes]
**Accessibility**: [A11y requirements]
## Technical Notes
**Implementation Hints**: [Technical guidance]
**API Changes**: [If applicable]
## Definition of Done
- [ ] Code complete and reviewed
- [ ] Unit tests passing
- [ ] Integration tests passing
- [ ] Acceptance criteria verified
- [ ] Design QA passed
- [ ] Documentation updated
- [ ] Ready for release
Instructions
- Ask clarifying questions about the user and goal if unclear
- Reference any design or research documents via @file syntax
- Use Given/When/Then format for acceptance criteria
- Include edge cases and error handling
- Save in stories/ or backlog/ folder
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?