‹ 首页

job-stories

@phuryn · 收录于 1 周前 · 上游提交 1 周前★ 社区精选

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.

适合你,如果常用JTBD方法表达用户动机和场景

/ 通过 npx 安装 校验哈希
npx oh-my-skill add phuryn/pm-skills/job-stories
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- phuryn/pm-skills/job-stories
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify phuryn/pm-skills/job-stories
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
23265GitHub stars
~643上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 18468a9 · 表述以原文为准
它做什么

Claude 会按照「当[情境],我想[动机],以便[结果]」的格式生成工作故事,并附带6-8条验收标准。

什么时候触发

当你需要编写工作故事、创建JTBD风格的需求项,或表达用户情境和动机时触发。

装好后可以这样说
Claude会生成一个完整的工作故事示例。
Claude会输出多个工作故事及验收标准。
技能原文 SKILL.md作者撰写 · MIT · 18468a9

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
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:

  1. [Situation is properly recognized]
  2. [System enables the desired motivation]
  3. [Progress or feedback is visible]
  4. [Outcome is achieved efficiently]
  5. [Edge cases are handled gracefully]
  6. [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:

  1. Display Spending Summary with 'Weekly Spending Overview' section
  2. Real-Time Update when expense logged
  3. Progress Indicator (progress bar showing 0-100% of weekly budget)
  4. Remaining Budget Highlight in prominent color
  5. Detailed Spending Log with breakdown by category
  6. Notifications at 80% budget threshold
  7. Weekend-Specific Reminder at 90% by Thursday evening
  8. 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
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。