What is manage-backlog?

A backlog manager for keeping product work in shared Markdown files. A backlog is an ordered list of planned work, where each item includes its goal, acceptance checks, tasks, and estimate.

Use it to add, refine, split, assign, estimate, or reorder product backlog items.

It keeps work items consistent and makes vague or oversized requests visible before development starts.

manage-backlog — Skill for Claude Code by atman-33/workhub

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 atman-33/workhub --skill manage-backlog

Clone the repo

git clone --depth 1 https://github.com/atman-33/workhub

Made for: Claude Code.

Or install team-ops, the plugin that ships this one along with the rest of its 13 skills.

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/atman-33/workhub/manage-backlog/github.svg)](https://agentmods.dev/skills/atman-33/workhub/manage-backlog)

Your own site

<a href="https://agentmods.dev/skills/atman-33/workhub/manage-backlog"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/manage-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/atman-33/workhub/manage-backlog"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/manage-backlog.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 512 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.00512
Opus 5.5	$0.00023	$0.00205
Sonnet 5.5	$0.00011	$0.00102
Haiku 4.5	$0.00006	$0.00051

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

Security

Grade A, and why

manage-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 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.

plugins/team-ops/skills/manage-backlog/SKILL.md · 59 lines

What it actually says

Manage the product backlog

The backlog is Markdown in the shared folder (SSoT): projects/<p>/backlog/product-backlog.md (ordered overview) + items/<id>-<slug>.md (one PBI = one file).

PBI file schema

---
id: P-0012          # per-project, sequential; next id = max existing + 1
title: ...
status: todo        # todo | doing | review | done
points: 3           # from project.json sprint.pointScale
sprint: ""          # sprint folder name once committed (plan-sprint sets it)
assignee: ""
repos: []           # repo names this PBI touches (from project.json)
created: <date>
updated: <date>
---

## Story
As a <user>, I want <capability>, so that <value>.

## Acceptance Criteria
- [ ] ...

## Tasks
- [ ] ...

## Notes

Operations

Add: assign the next id, create items/<id>-<slug>.md, add a row to product-backlog.md at the position the user wants (order = table order).
Refine: fill missing story/AC/points; keep AC testable and concrete. Flag items that are vague or exceed the largest point value, and propose splits.
Split: new ids for the parts; the original becomes done with a note pointing at its children, or is reworded as one of the parts.
Reorder / status: edit the overview table; status changes also update the item file's frontmatter (status, updated). done is normally set by humans at review — don't mark items done unilaterally.

Rules

Content in the team content language (<content-language>); id/status values stay as-is.
Never renumber existing ids. Never delete an item file — status and the overview table carry the lifecycle.
Append one activity-log line summarizing the batch of edits.

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 First seen · 59 lines · 57 tokens per session scan A dc0bac6dfb2e

Subscribe to this mod's changes

manage-backlog is a skill published in the GitHub repository atman-33/workhub (3 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 512 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-09-03.

Claude Code Project management claude-code-plugin cross-platform desktop-app developer-tools obsidian

expo-launchpad-status

Show the current expo-launchpad pipeline state — phase, round, next role, pause reason — read-only.

SummerRiversound/expo-launchpad · 27 tokens

tasknotes

This skill should be used when the user asks to 'create a task', 'add a TODO', 'plan a sprint', 'organize tasks', 'track time', 'setup Kanban', 'create task from code', 'sync tasks with sprint', 'pomodoro session', 'start pomodoro', 'time estimate', or mentions TaskNotes, task management, or project planning in…

parisgroup-ai/imersao-ia-setup · 106 tokens

issue-hygiene

How to write an issue somebody can act on, how to triage a pile of them, and the label vocabulary that stays useful. Use when filing, triaging, labelling, closing or linking issues.

Mikedev115/Aetox · 47 tokens

aetox-slice

Decomposes a technical specification or plan into vertical tracer-bullet tickets. Calculates directed dependency graphs (DAG), schedules prefactoring first, applies expand-contract sequencing for wide refactors, quizzes the user on ticket granularity, and emits atomic per-ticket files sized for optimal agent context…

Mikedev115/Aetox · 64 tokens

project-consolidation

Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. Apps-arena, GitHub-loom), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project…

linxule/memex-plugin · 133 tokens

roadmap-update

Produit un document de roadmap dans output/ en croisant l'état actuel des epics beads avec les décisions et priorités documentées dans le wiki. Applique les règles anti-lissage — ne jamais compléter avec des connaissances d'entraînement, citer le wiki pour chaque affirmation de scope ou de priorité. Triggers — mettre…

evb87-tech/corpus · 94 tokens