Skip to content
Development
Skill

/triage-backlog

Triage .turbo/backlog.md: merge duplicates and decide with the user what to keep or drop. Use when the user asks to \"triage the backlog\", \"clean up the backlog\", or \"groom the backlog\".

From plugin
turbo
42074 skills

Claude Code

$ npx -y skills add tobihagemann/turbo --skill triage-backlog --agent claude-code

SKILL.md

triage-backlog.SKILL.md
name: triage-backlog
description: "Triage .turbo/backlog.md: merge duplicates and decide with the user what to keep or drop. Use when the user asks to \"triage the backlog\", \"clean up the backlog\", or \"groom the backlog\"."

Triage Backlog

Decide, entry by entry, which improvements in `.turbo/backlog.md` are worth keeping.

Step 1: Read the Backlog and Merge Duplicates

Resolve the repo root with `git rev-parse --show-toplevel`, except inside a linked worktree — where `git rev-parse --git-dir` differs from `--git-common-dir` — in which case use the parent of the common dir.

When that root holds the legacy `.turbo/improvements.md`, carry it into `.turbo/backlog.md` before reading, with the Write or Edit tool. When `.turbo/backlog.md` does not exist, write the legacy content there with its `# Improvements` header changed to `# Backlog`. Otherwise, append each legacy entry that `.turbo/backlog.md` does not already hold word for word. Once `.turbo/backlog.md` holds every legacy entry, delete the legacy file. When the write or the deletion is refused, tell the user what is left to do.

Read `.turbo/backlog.md` under that root. When it does not exist or holds no entries, present "No backlog entries to triage." Then use the TaskList tool and proceed to any remaining task.

Merge entries that cover the same improvement into one entry that keeps every detail either held, write the merged entries back, and output which ones were merged. Update each **Paired with** line in counterpart entries that names a title the merge retired.

Number the remaining entries in file order.

Step 2: Assess Each Entry

Work from each entry's own text. Read the code an entry names only when its text is too thin to say what the entry is for.

For each entry, settle the two parts its question in Step 3 carries, without outputting them yet:

  • **Story** — one sentence naming who benefits and what they get, in plain language a reader who has not seen the code can follow. When nothing changes for the person using the software, tell it from the maintainer's side: what the entry simplifies.
  • **Recommendation** — keep or drop, with a one-line reason.

Recommend keeping an entry that serves a goal the person using the software actually has, fixes a problem that was observed, or simplifies existing code. Recommend dropping one that is theoretical or was never observed, is decoration, would be resolved by another entry's fix, or adds machinery no requirement demands. For an entry carrying a **Revisit** line, apply these criteria to the fuller version it describes as though its condition held; the condition being unmet is no ground to drop it. When the entry's text settles neither, recommend neither and name what is unclear.

Step 3: Decide Keep or Drop

Use `AskUserQuestion`, one question per entry in number order, filling each call to its four-question limit:

  • **Header** — `#<number>`
  • **Question** — the entry's summary, then its story, then what is unclear when Step 2 recommended neither, ending with "Keep or drop?"
  • **Options** — **Keep** and **Drop**. Place the recommended one first with "(Recommended)" appended and put the reason in its description. In the other's description, say what choosing it gives up. When neither is recommended, list **Keep** first unlabeled and say in each description what choosing it gives up.

After each call, delete the entries the user dropped from `.turbo/backlog.md`. When a dropped entry carries a **Paired with** line, remove that reference from each counterpart entry it names. When an answer asks a question or gives an instruction in place of a choice, act on it, then ask about that entry again when keep or drop is still open.

Repeat until every entry is decided.

Step 4: Report

Delete `.turbo/backlog.md` when no entries remain. Output the entry count as read and the count remaining, followed by the summaries of the dropped and merged entries.

Then use the TaskList tool and proceed to any remaining task.

Read more
@tobihagemann
Ships withturbo

A human-gated agentic software factory for Claude Code and Codex: you decide what to build and judge the result; skills shape, build, polish, ship, and learn.

Stars on GitHub

Momentum

stars in total
420
Star history of tobihagemann/turbo on GitHub, a chart by star-history.com

Other skills on turbo.

apply-turbo-handoffs

apply-turbo-handoffs

Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…

@tobihagemann@tobihagemannInstall Skill
apply-findings

apply-findings

Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…

@tobihagemann@tobihagemannInstall Skill
assess-technical-debt

assess-technical-debt

Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…

@tobihagemann@tobihagemannInstall Skill
backlog

backlog

Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…

@tobihagemann@tobihagemannInstall Skill
code-style

code-style

Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…

@tobihagemann@tobihagemannInstall Skill

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react6d252k
@facebook@facebookInstall Skill

Questions about triage-backlog.

Which coding agents can use triage-backlog?
triage-backlog installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.