A system for managing development tasks across session TODOs, workspace checklist files, and external issue trackers. An issue tracker is a tool for recording and following software tasks or bugs.

Use it to classify incoming work, create or update issues, synchronize task status, prioritize items, and prune stale backlog entries.

It keeps tasks organized across temporary work, local planning files, and shared team records. It also provides common rules for priorities and task states.

backlog — Skill by es6kr

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.

agentmods

npx agentmods add skills/es6kr/skills/backlog

Any agent

npx skills add es6kr/skills --skill backlog

Clone the repo

git clone --depth 1 https://github.com/es6kr/skills

Made for: Claude Code, Codex.

Or install es6kr, the plugin that ships this one along with the rest of its 32 skills, 5 hooks.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00181	$0.00782
Opus 5	$0.00090	$0.00391
Sonnet 5	$0.00036	$0.00156
Haiku 4.5	$0.00018	$0.00078

Measured 2d ago against content hash e84aec1545fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d ago.

The scan reads SKILL.md. This mod also ships 12 executable files (scripts/intake.py, scripts/plane_bulk_update.py, scripts/plane_client.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/backlog/SKILL.md · 66 lines

How it starts

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

Backlog

Unified backlog lifecycle management and orchestration across multiple storage layers (session WIP, markdown checklist files, and issue trackers).

Overview

The backlog skill provides a consistent operational interface for capturing, classifying, synchronizing, prioritizing, and maintaining backlogs across software development lifecycles.

Incoming Task / Request
  ├─ In-Session Short-Lived  ──→ /wip (Session Task API / TodoWrite)
  ├─ Workspace Markdown File ──→ /fix-plan (fix_plan.md / checklist.md)
  └─ Team-Shared External    ──→ Issue Tracker (GitHub Issues / Forge / Secondary Trackers)

Topics

Topic	Description	Guide
`prune`	Demote lower-priority items (P2/P3) and stale entries to preserve lean active focus sections	prune.md
`comment`	Post follow-up notes and nested review findings as comments on parent issues	comment.md
`create`	Create issues and intake items via API with fallback mechanisms	create.md

Default Invocation (`/backlog`)

When invoked with no arguments, the backlog skill runs the standard health and synchronization pipeline:

Sync: Poll external status for linked issues and pull requests to update resolved items.
Priority Triage: Re-evaluate urgency and blockers across active items.
Hygiene & Prune: Identify bloated or stale tasks exceeding active capacity.
Summary Report: Output an actionable breakdown of immediate priority candidates.

Configuration

Option	Default	Description
`--file=<path>`	`fix_plan.md`	Target markdown checklist path for local operations
`--role=<pm\|deep\|impl>`	(unset)	Execution role profile filter for pipeline scoping
`--secondary-sync=<skill>:<topic>`	(unset)	Abstract receiver contract for non-GitHub backlog synchronization

Cross-Workspace & Secondary Trackers

Vendor-specific and proprietary tracker integrations (e.g. Jira, Plane, internal enterprise backlogs) are decoupled from this public core skill through abstract Receiver Contracts (--secondary-sync). Private multi-repo orchestrators handle proprietary endpoints without polluting public skill schemas.

Read the full file on GitHub · 66 lines

Files

What ships with it

17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 66 lines · 181 tokens per session scan A e84aec1545fb

Subscribe to this mod's changes

backlog is a skill published in the GitHub repository es6kr/skills (2 stars, last pushed 3d ago), licensed MIT. It adds 181 tokens to every session and 782 once invoked, about $0.0009 per session on Opus 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-31.

Project management

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens