user-story-mapping-backlog

user-story-mapping-backlog is a skill for Claude Code, Codex from hamzabellouch/agent-skills. It costs 70 tokens per session (968 once invoked), scanned A, original, MIT.

A product-planning guide for turning large features into small, testable user stories. It covers user story maps, backlog refinement, sprint planning, Given-When-Then acceptance criteria, and WSJF prioritisation, a way to rank work by value and effort.

In plain words
What is it for?
Use it to break down epics, plan sprint slices, write acceptance criteria, and order engineering work. It is for teams organising a product backlog and deciding what to release first.
Why use it?
It helps teams replace vague feature ideas with work that can be understood, prioritised, and built in stages. It also makes the expected behaviour clearer before implementation starts.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to break down epics, plan sprint slices, write acceptance criteria, and order engineering work. It is for teams organising a product backlog and deciding what to release first.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hamzabellouch/agent-skills/user-story-mapping-backlog
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 hamzabellouch/agent-skills --skill user-story-mapping-backlog
Clone the repo
git clone --depth 1 https://github.com/hamzabellouch/agent-skills

Made for: Claude Code, Codex.

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.

agentmods badge for user-story-mapping-backlog

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/user-story-mapping-backlog/github.svg)](https://agentmods.dev/skills/hamzabellouch/agent-skills/user-story-mapping-backlog)
Your own site
<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/user-story-mapping-backlog"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/user-story-mapping-backlog/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.

agentmods 80×15 button for user-story-mapping-backlog

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzabellouch/agent-skills/user-story-mapping-backlog"><img src="https://agentmods.dev/badge/skills/hamzabellouch/agent-skills/user-story-mapping-backlog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 968 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.00968
Opus 5.5 $0.00028 $0.00387
Sonnet 5.5 $0.00014 $0.00194
Haiku 4.5 $0.00007 $0.00097

Measured 7d ago against content hash 550122b271d1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

user-story-mapping-backlog 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 7d 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.

Business/Product_Management_and_Ops/user-story-mapping-backlog/SKILL.md · 91 lines

How it starts

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

User Story Mapping & Backlog Refinement Skill Guide

This skill governs the breakdown of high-level feature initiatives into vertically sliced, testable user stories with rigorous acceptance criteria.


1. User Story Mapping Visual Framework

[ Backbone / Activities ]     (Discover)       -->      (Configure)     -->     (Checkout)
                                  |                          |                      |
[ Walking Skeleton (Release 1) ]  |-- Browse Catalog         |-- Select Variant     |-- Pay via Card
                                  |                          |                      |
[ Enhancements (Release 2) ]      |-- Filter by Price        |-- Add Custom Text    |-- Apple / Google Pay
                                  |                          |                      |
[ Future Scope (Release 3) ]      |-- AI Recommendations     |-- 3D Preview AR      |-- Split Payment

2. Production User Story Format & Gherkin Criteria

A. INVEST-Compliant Story Definition

  • Independent: Can be developed and deployed without hard blockers from other stories.
  • Negotiable: Focuses on the essence of the problem, allowing implementation flexibility.
  • Valuable: Delivers demonstrable value to the end user or business.
  • Estimable: Scoped small enough to be sized with reasonable engineering confidence.
  • Small: Fits comfortably within a single sprint iteration (1 to 3 days of dev time).
  • Testable: Has unambiguous acceptance criteria with binary pass/fail verification.

B. Production Story Example with Gherkin BDD

### US-402: Automatic Retry on Transient Payment Gateway Failures

**As a** customer making an online purchase,  
**I want** the payment service to automatically retry temporary network interruptions with Stripe,  
**So that** my transaction does not fail due to momentary carrier or network drops.

---

#### Technical Scope & Acceptance Criteria (Gherkin BDD)

```gherkin
Feature: Payment Gateway Transient Failure Retries

Read the full file on GitHub · 91 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.

  1. 7d ago First seen · 91 lines · 70 tokens per session scan A 550122b271d1

Subscribe to this mod's changes

user-story-mapping-backlog is a skill published in the GitHub repository hamzabellouch/agent-skills (8 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 968 once invoked, about $0.0003 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-10-10.

Related

Other skills, from other repositories

spec-create

Create a structured feature specification with self-contained task files organized into parallel execution batches. Use this skill when the user says "create a spec", "plan this feature", "write up an implementation plan", "break this into tasks", or after any planning conversation where the user wants to capture…

benjaminthomas/spec-driven-dev · 118 tokens

polya-plan

Phase 2 of the Pólya Heuristic Coder: Devising a Plan, Land and Expand Strategy, Vertical Tracer Bullets, Expand-Contract Pattern, Contingency Plan B, Task Sizing, and The Pause Rule (docs/plan/{slug}-plan.md).

GulajavaMinistudio/awesome-copilot-id · 63 tokens

to-prd

Optional Phase 0.5 of the Pólya Heuristic Coder: Product Requirements Document (PRD) detailing User Stories, SMART Acceptance Criteria, Personas, and Business Goals.

GulajavaMinistudio/awesome-copilot-id · 41 tokens

architectural-engineering-manager

Use when a task needs the judgment of an Architecture/Engineering firm or department manager — pricing a project fee (lump sum vs. hourly vs. % of construction cost), staffing a project against backlog, evaluating scope creep on a fixed-fee job, managing professional liability exposure, or deciding whether to pursue a…

wonsukchoi/domain-experts · 73 tokens

compensation-benefits-manager

Use when a task needs the judgment of a Compensation and Benefits Manager — designing or evaluating a pay structure/leveling system, benchmarking compensation against market, deciding on a benefits package tradeoff, or auditing for pay equity issues. Narrower and more specialized than the broader hr-people-manager…

wonsukchoi/domain-experts · 72 tokens

computer-systems-analyst

Use when a task needs the judgment of a Computer Systems Analyst — running requirements elicitation and gap analysis against a target system, writing a feasibility study for a build-vs-buy-vs-customize decision, designing a system integration approach (point-to-point vs middleware vs API-led), scoping data-migration…

wonsukchoi/domain-experts · 85 tokens