agentleFS
yuusakuriyuusakuri/agent-skills/skills/job-stories/SKILL.md

job-stories

Skill2 starsChanged 10 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format.

    line 7
  2. Distinctive:

    Description: When [situation], I want to [motivation], so I can [outcome].

    line 32
  3. Distinctive:

    Description: When I'm preparing my weekly allowance for snacks (situation), I want to quickly see how much I've spent so far (motivation), …

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.