A workflow for taking a software user story from a team tracker through implementation, verification, review, pull-request creation, and ticket updates. A user story is a description of work and its acceptance conditions.

Use it with an issue reference such as PROJ-1234, ENG-42, or #123. It helps fetch the ticket, plan the work, implement it, run applicable tests and quality checks, review the result, open a pull request, and update the tracker.

It keeps the work connected to the original ticket and makes the required checks explicit before the change is handed off. It can work across programming languages and frameworks by following the repository's own instructions.

work-story — Skill for Claude Code by theam/claude-dev-kit

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add theam/claude-dev-kit --skill work-story

Clone the repo

git clone --depth 1 https://github.com/theam/claude-dev-kit

Made for: Claude Code.

Or install fullstack-dev-kit, the plugin that ships this one along with the rest of its 1 skill, 5 commands, 9 agents, 3 hooks, 3 MCP servers, 1 plugin.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/theam/claude-dev-kit/work-story/github.svg)](https://agentmods.dev/skills/theam/claude-dev-kit/work-story)

Your own site

<a href="https://agentmods.dev/skills/theam/claude-dev-kit/work-story"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/work-story/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/theam/claude-dev-kit/work-story"><img src="https://agentmods.dev/badge/skills/theam/claude-dev-kit/work-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,474 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.01474
Opus 5.5	$0.00023	$0.00590
Sonnet 5.5	$0.00011	$0.00295
Haiku 4.5	$0.00006	$0.00147

Measured 1mo ago against content hash 6ff4d86844f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

work-story scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

codex/skills/work-story/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Work Story (orchestration)

You are the story orchestrator. Input: an issue key from the team's tracker. Output: a pull request that satisfies the story's acceptance criteria with verified quality gates, and a tracker ticket that reflects it. You run every step yourself, in order — invoke the kit's other skills as the steps below call for them; there is no separate orchestrator process here.

If no issue reference is given, ask for one — don't guess. Accept the shapes the configured tracker uses (PROJ-1234 Jira, ENG-42 Linear, #123 GitHub/Azure).

Stack-agnostic. Carry no assumptions about language, framework, or test runner. Read the repo's AGENTS.md / CLAUDE.md and .claude/ for build/test/lint/coverage commands and conventions, and follow them exactly; when silent, detect conventions from the repo — never impose a stack. The always-on rules in instructions/secure-coding.md and instructions/testing-standards.md bind every step.

1. Context

If .claude/dev-kit.json is missing, run dev-kit-setup first (one-time bootstrap: tracker, project/team, field IDs).
Run issue-fetch for the ticket and show the summary.
If the ticket references Figma, run figma-fetch and summarize the UI intent.
Read the repo's project instructions and load the baseline stack profile (instructions/stacks/<id>.md for the stacks in .claude/dev-kit.json); the repo's own instructions always win, the profile fills gaps.

2. Plan — WAIT FOR APPROVAL

Validate assumptions against the running product when feasible (boot the app / exercise the flow) before writing the plan. Then present, in the chat, the ticket summary and a full plan — Understanding, Affected areas, numbered Implementation steps, Test plan, Open questions — and wait for the user's explicit approval. Write no code until they approve (unless the invocation says the plan is pre-approved, e.g. an automated run).

3. Implement

Follow the repo's conventions and architecture. Keep the diff scoped to the story — no opportunistic refactors.
Update every side of any changed contract (payload/route/enum/schema/validation) together.
For user-facing frontend work, write accessible markup as you go (semantic HTML, labels, alt, keyboard/focus) — cheaper than fixing it at review.

Read the full file on GitHub · 96 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · +3 lines 6ff4d86844f4
1mo ago Changed · +13 lines 51fc5b3b5f49
1mo ago Changed · +6 lines fb266a6dc311
2mo ago First seen · 74 lines · 57 tokens per session scan A 6dad72c896f3

Subscribe to this mod's changes

work-story is a skill published in the GitHub repository theam/claude-dev-kit (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,474 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Code review Git and workflow Project management ai-agents claude-code-plugin developer-tools jira

next-issue

Work the next open item on the issue.

liatrio-labs/claude-code-gauntlet · 12 tokens

settle

Settle the released work items: show the rule changes their spec.md files state, grouped by the section each names and in merge order, write each section of the policy documents (docs/ unless Policy root names another) as its group's latest decision, checked against the code, decide every open row of their records…

MichaelYcJo/SpecSeal · 138 tokens

work-story