先看看示例
作者提供的示例，实际效果取决于你的输入和使用工具。
输入
店员临时生病，群里找到了同事替班，但店长尚未确认；最终班表仍显示原排班。
输出
编辑示例 · 未运行
当我已经找到替班同事、需要确认明天由谁上班时，我想知道店长是否批准换班，以便按确定的安排到店。
验收：
- 未批准时明确显示“待店长确认”。
- 批准后原班次与替班人员对应关系一致。
- 拒绝时原班表保持有效，并能看到处理结果。
待确认：替班同事是否也必须确认。
方法说明
--- 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 ## 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 - [Jobs-to-be-Done Masterclass with Tony Ulwick and Sabeen Sattar](https://www.productcompass.pm/p/jobs-to-be-done-masterclass-with) (video course)