Generate JTBD job stories with acceptance criteria and design references.
npx skills add https://github.com/skytiger6724/qwen-skills --skill job-stories-skytiger6724
Please help me install this Agent Skill. Skill: job-stories Source: https://github.com/skytiger6724/qwen-skills/tree/main/job-stories Command: npx skills add https://github.com/skytiger6724/qwen-skills --skill job-stories-skytiger6724
Product managers and discovery teams need a reliable way to turn ambiguous feature ideas into outcome-focused job stories that clearly articulate the situation, motivation, and desired result, so they can build backlog items without guessing about user intent.
Create job stories for the new onboarding widget, naming situations, motivations, outcomes, and acceptance criteria while referencing the linked design files.
High-intent search queries and answers about installing and using this skill.
To write job stories for product discovery, use the "When [situation], I want to [motivation], so I can [outcome]" format. This shifts focus from user personas to capturing specific contexts, motivations, and desired outcomes for feature planning.
The best way to turn ambiguous feature ideas into backlog items is to generate job stories that capture user situations and motivations. This approach structures backlog items around measurable outcomes rather than guessing user intent.
To define acceptance criteria for JTBD job stories, list measurable outcomes and observable signals that validate each desired result. Ensure the criteria cover recognition, progress tracking, and safeguards to confirm the user outcome.
Yes, you can link design mockups to job stories during feature planning. Linking Figma flows or prototypes keeps the user situation, expected behavior, and desired results aligned with the visual context throughout discovery.
You need to use job stories for feature planning when you must describe user outcomes without relying on persona labels. They are essential for translating abstract feature concepts into structured backlog items with clear contexts and validation plans.
Include observable signals in job stories that validate the user outcome, such as recognition cues, progress indicators, and safeguard triggers. These measurable signals provide a concrete validation plan for each expected result.
kvnxiaoCreate per-ticket git worktrees and generate GitHub PRs for Linear tickets.
tarunccetGenerate JTBD job stories with measurable acceptance criteria from product context.
MaVoid-TeamCreate structured user job stories with acceptance criteria and design mockup links.
ch-m-nCreate visual user story maps from activities, steps, and tasks.
