pkking/job-stories
dotfiles/dot_config/skillshare/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 27, 2026
$ install --global
skillsauthnpx skillsauth add pkking/dotfiles 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%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 9:47 AM24.5s2 files 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
pkking/skill-creator
testing
VerifiedTrustedCommunity
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
SKILL.mdUpdated Jun 9, 2026
pkking/grill-me
testing
VerifiedTrustedCommunity
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
SKILL.mdUpdated Jun 5, 2026
pkking/find-skills
data-ai
VerifiedTrustedCommunity
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
SKILL.mdUpdated Jun 4, 2026
pkking/lfg
development
VerifiedTrustedCommunity
Run the full autonomous engineering pipeline end-to-end (plan, work, code review, test, commit, push, open PR, watch CI, fix CI failures until green). Use only when the user explicitly requests hands-off execution of a software task and provides a feature description; do not auto-route casual conversation here.
SKILL.mdUpdated May 9, 2026