tobihagemann/turbo / codex/skills/triage-backlog
triage-backlog
VerifiedTriage .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 apply_patch. 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 call update_plan to mark this step completed and continue with the next step of the active workflow.
Remove from every entry its Validated line and the command lines nested under it, and write the backlog back.
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 request_user_input, one question per entry in number order, filling each call to its three-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 call update_plan to mark this step completed and continue with the next step of the active workflow.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |