business-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, o
SKILL.mdresources/agent-presets/skills/business-job-stories/SKILL.md
GitHubApp 执行约定
先读取本技能正文及任务所需的本地参考资源。使用中文;工作目录由任务提供,仅读取用户提供、当前任务授权的资料。正文中的 $ARGUMENTS 及斜杠命令表示用户任务输入,不调用 Claude 专用命令。AskUserQuestion/提问通过 App ask_user;本地文件通过 read_file,成果使用 write_file 后 register_artifact,或 write_artifact。相对资源路径以本 SKILL.md 所在目录为起点。若技能读取结果含目录,按该目录构建资源绝对路径。
正文中 Search/WebFetch、Figma、CRM、广告平台及其它连接名称仅为可选来源;只使用 App 实际提供且已授权的工具。没有连接时从上传材料完成流程,把缺少的外部验证列出,不安装运行时插件或扫描用户全局配置。默认输出 Markdown/CSV 草稿;Office、图表、HTML、PNG 或图像生成只在对应工具和运行库可用时执行。不得擅自发送邮件、发表内容、签约、创建发票、修改线上商品或花费广告预算。
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