7a336e6e/Defining User Stories
product/defining-user-stories/SKILL.md
Translate high-level requirements into specific, value-focused user stories with acceptance criteria.
$ install --global
skillsauthnpx skillsauth add 7a336e6e/skills Defining User StoriesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
4
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 26, 2026, 2:03 AM141.6s1 file scanned
SKILL.md
- name:
- Defining User Stories
- description:
- Translate high-level requirements into specific, value-focused user stories with acceptance criteria.
Defining User Stories
Goal
Capture what needs to be built from the user's perspective, ensuring every feature delivers specific value.
When to Use
- After
planner/project-planning. - Before
architect/analyzing-requirements. - When the "Why" of a feature is unclear.
Instructions
1. The Standard Format
Use the "Connextra" template:
As a <role>, I want to <action>, So that <value/benefit>.
2. INVEST Criteria
Ensure stories are:
- Independent
- Negotiable
- Valuable
- Estimable
- Small
- Testable
3. Acceptance Criteria (Gherkin-ish)
Define "Done" clearly.
- "Verify that the user can see their profile picture."
- "Verify that entering an invalid email shows an error."
4. Splitting Stories
If a story is too big (Epic), split it.
- Workflow Steps: Create Account -> Verify Email -> Set Password.
- Data Variations: Standard User vs Admin User.
- Interface: Web vs Mobile.
Constraints
✅ Do
- DO: Focus on the user benefit, not the technical implementation.
- DO: Write acceptance criteria before writing code.
- DO: Keep stories small enough to complete in 1-2 days.
❌ Don't
- DON'T: Write "As a developer, I want to migrate the database..." (That's a chore, not a story).
- DON'T: Include technical jargon in the story title ("Implement GET /api/users").
- DON'T: Leave acceptance criteria ambiguous ("Make it fast").
Output Format
- Updates to
tasks.md(Stories become tasks). requirements/user_stories.md(optional).
Dependencies
planner/project-planning/SKILL.md
Related Skills
7a336e6e/Test Driven Development
development
VerifiedTrustedCommunity
Implement features using the Red-Green-Refactor cycle to ensure testability and correctness from the start.
1SKILL.mdUpdated Mar 25, 2026
7a336e6e/task-tracking
data-ai
VerifiedTrustedCommunity
Manage the `tasks.md` ledger with strict locking and collision avoidance protocols to allow multiple agents to work in parallel safely.
1SKILL.mdUpdated Mar 25, 2026
7a336e6e/git-workflow
development
VerifiedTrustedCommunity
The git-workflow skill defines branching conventions, commit message formats, and pull request standards that all agents must follow for consistent version control.
1SKILL.mdUpdated Mar 25, 2026
7a336e6e/environment-config
development
VerifiedTrustedCommunity
The environment-config skill standardizes how agents manage environment variables, secrets, and application configuration across local development and deployed environments.
1SKILL.mdUpdated Mar 25, 2026