/job-stories
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.
One skill from pm-skills.
shell
$ npx -y skills add phuryn/pm-skills --skill job-stories --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/job-stories
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
Stats
Stars24,320
Forks2,501
LicenseMIT
SKILL.md
job-stories.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 1. **Identify user situations** that trigger the need 2. **Define motivations** underlying the user's behavior 3. **Clarify outcomes** the user wants to achieve 4. **Apply JTBD framework:** Focus on the job, not the role 5. **Create acceptance criteria** that validate the outcome is achieved 6. **Use observable, measurable language** 7. **Link to design mockups** or prototypes 8. **Output job stories** with detailed acceptance criteria
