MaVoid-Team/user-stories
Agent-Skills/PM-Skills/skills/user-stories/SKILL.md
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
content-media
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add MaVoid-Team/Capital-Consultancy-Final 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: Apr 30, 2026, 3:31 PM14.8s1 file scanned
SKILL.md
- name:
- user-stories
- description:
- Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.
User Stories
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria. Generates stories with descriptions, design links, and acceptance criteria.
Use when: Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.
Arguments:
$PRODUCT: The product or system name$FEATURE: The new feature to break into stories$DESIGN: Link to design files (Figma, Miro, etc.)$ASSUMPTIONS: Key assumptions or context
Step-by-Step Process
- Analyze the feature based on provided design and context
- Identify user roles and distinct user journeys
- Apply 3 C's framework:
- Card: Simple title and one-liner
- Conversation: Detailed discussion of intent
- Confirmation: Clear acceptance criteria
- Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
- Use plain language a primary school graduate can understand
- Link to design files for visual reference
- Output user stories in structured format
Story Template
Title: [Feature name]
Description: As a [user role], I want to [action], so that [benefit].
Design: [Link to design files]
Acceptance Criteria:
- [Clear, testable criterion]
- [Observable behavior]
- [System validates correctly]
- [Edge case handling]
- [Performance or accessibility consideration]
- [Integration point]
Example User Story
Title: Recently Viewed Section
Description: As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.
Design: [Figma link]
Acceptance Criteria:
- The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
- It is not displayed for users visiting the first product page of their session.
- The current product itself is excluded from the displayed items.
- The section showcases product cards or thumbnails with images, titles, and prices.
- Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
- Clicking on a product card leads the user to the corresponding product page.
Output Deliverables
- Complete set of user stories for the feature
- Each story includes title, description, design link, and 4-6 acceptance criteria
- Stories are independent and can be developed in any order
- Stories are sized for one sprint cycle
- Stories reference related design documentation
Further Reading
- How to Write User Stories: The Ultimate Guide
Related Skills
MaVoid-Team/wwas
development
VerifiedTrustedCommunity
Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/test-scenarios
testing
VerifiedTrustedCommunity
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/summarize-meeting
testing
VerifiedTrustedCommunity
Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
SKILL.mdUpdated Apr 16, 2026
MaVoid-Team/stakeholder-map
development
VerifiedTrustedCommunity
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
SKILL.mdUpdated Apr 16, 2026