job-stories SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

job-stories from phuryn/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add phuryn/pm-skills/job-stories@git:20260303.a372bee

Pins git:20260303.a372bee in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
phuryn/pm-skills
Path
pm-execution/skills/job-stories/SKILL.md
Versions recorded
2
Latest version
git:20260303.a372bee, committed Mar 3, 2026
First version recorded
Mar 1, 2026
Size
2,969 bytes
Repository stars
28,158
License
MIT

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 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].
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dg3lzuksytblffmx/69f75264b311418a1ebaf06c9872ed1271203cfc6316466fcb99cc948ade800b.json

Then /plugin install job-stories@markdownregistry-dg3lzuksytblffmx in Claude Code. It installs git:20260303.a372bee, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add phuryn/pm-skills/job-stories@sha256:69f75264b311418a

The line at the top of this page pins the label git:20260303.a372bee, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_dg3lzuksytblffmx.svg)](https://markdownregistry.com/a/art_dg3lzuksytblffmx)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in phuryn/pm-skills/job-stories since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of job-stories from somewhere else? Ask it: where did my job-stories come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 2 versions of this file, between Mar 1, 2026 and Mar 3, 2026, about one every day.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260303.a372bee latest2026-03-03 a372bee 2,969 BA view · diff
git:20260301.77dbdfa2026-03-01 77dbdfa 3,034 BA view

Copies

Copies in other repositories

1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds the newest version.

A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.

Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (2969 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

phuryn/pm-skills · 28,158 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_dg3lzuksytblffmx
GET https://markdownregistry.com/api/v1/resolve?ref=phuryn/pm-skills/job-stories
GET https://markdownregistry.com/api/v1/blob/69f75264b311418a1ebaf06c9872ed1271203cfc6316466fcb99cc948ade800b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from phuryn/pm-skills

AGENTS.md AGENTS.md file
phuryn/pm-skills · AGENTS.md
git:20260604.2b4e4dc · audit A · 28,158 stars
CLAUDE.md CLAUDE.md file
phuryn/pm-skills · CLAUDE.md
git:20261108.67ee404 · audit A · 28,158 stars
code-review SKILL.md skill
phuryn/pm-skills · pm-ai-shipping/skills/code-review/SKILL.md · Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and…
git:20261029.53f3494 · audit A · 28,158 stars
intended-vs-implemented SKILL.md skill
phuryn/pm-skills · pm-ai-shipping/skills/intended-vs-implemented/SKILL.md · Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and…
git:20261029.53f3494 · audit A · 28,158 stars
shipping-artifacts SKILL.md skill
phuryn/pm-skills · pm-ai-shipping/skills/shipping-artifacts/SKILL.md · Moved to phuryn/product-engineering, where it is maintained in the ai-shipping plugin; this copy says where it went and…
git:20261029.53f3494 · audit A · 28,158 stars
ab-test-analysis SKILL.md skill
phuryn/pm-skills · pm-data-analytics/skills/ab-test-analysis/SKILL.md · Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and…
git:20260303.a372bee · audit A · 28,158 stars
cohort-analysis SKILL.md skill
phuryn/pm-skills · pm-data-analytics/skills/cohort-analysis/SKILL.md · Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level…
git:20260303.a372bee · audit A · 28,158 stars
sql-queries SKILL.md skill
phuryn/pm-skills · pm-data-analytics/skills/sql-queries/SKILL.md · Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects…
git:20260303.a372bee · audit A · 28,158 stars
brainstorm-okrs SKILL.md skill
phuryn/pm-skills · pm-execution/skills/brainstorm-okrs/SKILL.md · Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use…
git:20260303.a372bee · audit A · 28,158 stars
create-prd SKILL.md skill
phuryn/pm-skills · pm-execution/skills/create-prd/SKILL.md · Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background…
git:20261009.6058e29 · audit A · 28,158 stars
dummy-dataset SKILL.md skill
phuryn/pm-skills · pm-execution/skills/dummy-dataset/SKILL.md · Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON…
git:20260303.a372bee · audit A · 28,158 stars
live-polls SKILL.md skill
phuryn/pm-skills · pm-execution/skills/live-polls/SKILL.md · A poll or vote in a meeting, workshop or training: 'run a quick poll', dot-voting, a confidence vote, a word cloud, a…
git:20261108.b017977 · audit A · 28,158 stars

Every file in phuryn/pm-skills

Other files named job-stories

job-stories SKILL.md skill
akillness/jeo-skills · .agent-skills/job-stories/SKILL.md · Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed…
git:20260919.9f2a908 · audit A · 60 stars

Browse by kind, by grade A, or by owner.