Skip to main content
skill CX Codex

backlog · nschurmann — Claude Code skill: what it does, how to install

The backlog skill for Claude Code turns ideas or features into a list of short, vertical user stories. It slices requirements into independent units of work.

MIT ★ 265 updated 2026-11-11

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add nschurmann/hola-ai --skill backlog -a claude-code
Open on GitHub

What backlog does

This tool structures project requirements into actionable user stories. The agent listens to your concept, asks about high-impact decisions, and generates an ordered list of tasks.

Each story delivers end-to-end value across all system layers. The skill restricts the output to 15 stories, omitting acceptance criteria, estimates, or technical implementation details.

The initial story defines the stack, followed by a minimal walking skeleton. Upon completion, the agent offers to save the context and stack configuration to your project instructions file.

What it helps with

  • Break down ideas into user stories
  • Define MVP task lists
  • Create task structures without technical bloat

Example prompts for the agent

  • Break [idea description] into user stories using backlog
  • Help me create a backlog for [feature]

How to install backlog

1Skills CLI (Vercel)

npx skills add nschurmann/hola-ai --skill backlog -a claude-code

2Manually: put the files in place

~/.claude/skills/backlog/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/backlog/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about backlog

How to install backlog in Claude Code?

Run npx skills add nschurmann/hola-ai --skill backlog -a claude-code in your project terminal.

What does the backlog skill do?

It converts software feature descriptions into vertical user stories, focusing on user benefits rather than technical details.

What is required to use backlog?

The skill requires no external dependencies but relies on a clear, initial feature description from the user.

Source text

SKILL.md · MIT
---
name: backlog
description: Turns a software idea or a discussed feature into a backlog of short, vertical user stories. No acceptance criteria or implementation.
disable-model-invocation: true
---

# Backlog

Your job is to help me split what I tell you into user stories. I bring the requirements; you order and slice them.

## Conversation

1. Listen to the idea or feature. It's an open discussion, you may use diagrams to understand the idea better.
2. Your purpose is to understand better the idea, there's no need to push back yet.
2. Never discuss architecture, stack, patterns or any implementation details.
3. Ask which decisions would be expensive to change later. Only identify them, don't design them.
4. Propose the backlog. I adjust it.

## Rules

- **Don't invent requirements.** Only split what I told you. If you see a gap, ask; don't fill it.
- **Each story delivers value on its own** and cuts through every layer of the system. Never split by layer.
- **No technical stories.** The actor is never the developer or the system. Infrastructure gets built inside the first story that needs it.
- **Few stories.** 10–15 max. I'd rather add than cut.
- **One line per story.** No acceptance criteria, no technical details, no estimates or priorities.
- The first story is always stack definition. The second story is always the smallest one usable end to end (walking skeleton).

## Output format

```markdown
## Context
<one or two lines: what it is and who it's for>
Expensive decisions: <the ones that apply, or "none">

## Backlog
1. As a <actor>, I want <action>, so that <benefit>.
2. As a <actor>, I want <action>, so that <benefit>. Requires: #1
```

Add `Requires: #N` only when a story makes no sense without another.

When done, offer to save the context and stack in the project's agent instructions file. The stories go to my tracker or issue tool; don't save them to files unless I ask.

© nschurmann · MIT · nschurmann/hola-ai

Similar skills

All skills for Agent setup: memory, context, orchestration →

backlog by other authors comes first.

backlog sammcj Tracks bugs and features in local Markdown files or GitHub Issues. Keeps backlogs tidy without drafting heavy PRDs or specifications. CX Codex +1 ★ 173repo stars backlog-plan microsoft backlog-plan plans backlog work in Azure DevOps, GitHub, and Jira without modifying remote trackers. Generates local plan files for sprints, triage, and task handoffs. CX Codex +1 ★ 1,627repo stars 02-user-stories AI-Driven Dev 02-user-stories turns an epic, product brief or PRD into ordered user stories with acceptance criteria, then checks whether they are ready to build. CX Codex +1 ★ 571repo stars writing-user-stories nicepkg writing-user-stories — a skill that teaches agents to write user stories in standard format: persona, action, and benefit. Triggers when you need to define requirements from the user's perspective. CX Codex +1 1installs om-backlog open-mercato om-backlog turns a product brief or a spec into a tracker tree: epics, stories with acceptance criteria, tasks. Shows the whole tree and waits before writing. CX Codex +1 2,300installs backlog-capture mvschwarz backlog-capture — a skill for Claude Code and five other coding agents that turns rough notes into structured backlog entries. Fire it after meetings or calls to grab an idea before it slips away. CX Codex +1 ★ 8,928repo stars backlog-management microsoft backlog-management is a Claude Code skill that defines shared backlog conventions for Azure DevOps, GitHub, and Jira. It structures PRD decomposition, triage, sprint planning, and task synchronization. CX Codex +1 ★ 1,627repo stars

From the same set3

Project sponsors

Companies that keep this analytics open