apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
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\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill triage-backlog --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill triage-backlog -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill triage-backlog -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill triage-backlog -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill triage-backlog -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill triage-backlog -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill triage-backlog -a windsurf -y
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\"."
Decide, entry by entry, which improvements in `.turbo/backlog.md` are worth keeping.
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.
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:
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.
Use `AskUserQuestion`, one question per entry in number order, filling each call to its four-question limit:
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.
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.
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.
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…
Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…
Shared changelog conventions and formatting rules. Not typically invoked directly.
Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.