MaVoid-Team/job-stories
Agent-Skills/PM-Skills/skills/job-stories/SKILL.md
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add MaVoid-Team/Capital-Consultancy-Final job-storiesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
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%
Error
VirusTotalMulti-engine malware detection
70%
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 20, 2026, 8:17 AM233.8s1 file scanned
SKILL.md
- name:
- job-stories
- description:
- Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.
Job Stories
Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format. Generates stories with detailed acceptance criteria focused on user situations and outcomes.
Use when: Writing job stories, expressing user situations and motivations, creating JTBD-style backlog items, or focusing on user context rather than roles.
Arguments:
$PRODUCT: The product or system name$FEATURE: The new feature to break into job stories$DESIGN: Link to design files (Figma, Miro, etc.)$CONTEXT: User situations or job scenarios
Step-by-Step Process
- Identify user situations that trigger the need
- Define motivations underlying the user's behavior
- Clarify outcomes the user wants to achieve
- Apply JTBD framework: Focus on the job, not the role
- Create acceptance criteria that validate the outcome is achieved
- Use observable, measurable language
- Link to design mockups or prototypes
- Output job stories with detailed acceptance criteria
Story Template
Title: [Job outcome or result]
Description: When [situation], I want to [motivation], so I can [outcome].
Design: [Link to design files]
Acceptance Criteria:
- [Situation is properly recognized]
- [System enables the desired motivation]
- [Progress or feedback is visible]
- [Outcome is achieved efficiently]
- [Edge cases are handled gracefully]
- [Integration and notifications work]
Example Job Story
Title: Track Weekly Snack Spending
Description: When I'm preparing my weekly allowance for snacks (situation), I want to quickly see how much I've spent so far (motivation), so I can make sure I don't run out of money before the weekend (outcome).
Design: [Figma link]
Acceptance Criteria:
- Display Spending Summary with 'Weekly Spending Overview' section
- Real-Time Update when expense logged
- Progress Indicator (progress bar showing 0-100% of weekly budget)
- Remaining Budget Highlight in prominent color
- Detailed Spending Log with breakdown by category
- Notifications at 80% budget threshold
- Weekend-Specific Reminder at 90% by Thursday evening
- Easy Access and Navigation to detailed breakdown
Output Deliverables
- Complete set of job stories for the feature
- Each story follows the 'When...I want...so I can' format
- 6-8 acceptance criteria focused on outcomes
- Stories emphasize user situations and motivations
- Clear links to design and prototypes
Further Reading
- Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar (video course)
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/user-stories
content-media
VerifiedTrustedCommunity
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.
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