apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Validate .turbo/backlog.md entries, recommend a working set, and run one lane: direct, investigate, or plan. Use when the user asks to \"implement the backlog\" or \"implement improvements\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill implement-backlog --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill implement-backlog -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill implement-backlog -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill implement-backlog -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill implement-backlog -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill implement-backlog -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill implement-backlog -a windsurf -y
name: implement-backlog description: "Validate .turbo/backlog.md entries, recommend a working set, and run one lane: direct, investigate, or plan. Use when the user asks to \"implement the backlog\" or \"implement improvements\"."
Validate improvements from `.turbo/backlog.md`, propose a specific working set based on the backlog's actual contents, and run one lane per session: direct, investigate, or plan. Mixing lanes in a single run tangles commits, so the skill processes exactly one lane each time. Entries outside the confirmed working set stay in the backlog for future runs.
When a working set and a lane were passed in, by the user or in a message from another session, start at Step 5 with them and create tasks for Steps 5 and 6 alone.
At the start, use `TaskCreate` to create a task for each step:
1. Read the backlog 2. Validate and classify 3. Recommend, confirm, and update the backlog 4. Brief the extra sessions 5. Run the chosen lane 6. Prune working-set entries from the backlog
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. If it does not exist, there are no backlog entries to implement; stop.
Parse all entries, extracting for each:
Improvements drift: files get renamed, code gets refactored, issues get fixed as side effects of other work. Before routing, validate each improvement and settle the Type of any entry whose Type is missing or wrong.
For each entry, verify whether the specific problem or opportunity described still exists. Do not rely on git log alone. Recent commits touching the same files do not mean the specific issue was addressed. Read the actual code and confirm:
1. **Files exist** — Do the referenced files/paths still exist? When one was renamed or its code moved, validate the entry at the current location instead. This check marks the entry stale only when the code it names is gone. 2. **Problem persists** — Read the relevant code sections. Is the exact issue or opportunity described in the entry still present? Check the specific claims: if the entry says a function is uncalled, verify it has no callers; if it says error handling is missing, check whether it was added. 3. **Revisit condition met** — For an entry carrying a Revisit field, check whether the recorded condition now holds. A shipped simplification is present by construction, so its presence alone says nothing about whether the fuller version is worth building yet. 4. **Stated scope matches the real gap** — For an entry claiming missing coverage, read what existing tests already pin before accepting its scope: a test that substitutes a test double at a boundary pins the behavior on one side of it and leaves the boundary itself unpinned, so a request to cover several variants often reduces to the single boundary they share. Before dropping an item on the grounds that an existing check covers it, confirm that the check pins that item through its own inputs or match patterns rather than inferring it from the check's name or description; an item no existing check pins stays in the entry's scope. Restate such an entry at its real scope, classify it Active, and use the restatement as its summary in Step 3. 5. **Claimed consequence holds** — For an entry claiming that two paths behave differently, that a change would alter observable behavior, or that the code as it stands leads to a stated outcome, verify the consequence itself rather than confirming only that the code it points at exists. For a claimed difference, between two paths or between the behavior before and after a change, read what each actually returns, exercising both when reading cannot settle it. For a claimed outcome, follow the path from the named code to that outcome and confirm nothing later on that path already stops it. When the claim is that nothing but the case it names reaches or relies on the named code, read that code's own tests: they surface dependents an entry written from a single path routinely omits, and turning up none leaves the claim unproven. When the named code is present but its stated consequence is false, restate the entry at the benefit it actually delivers, classify it Active, and use the restatement as its summary in Step 3; classify it Stale when no benefit survives.
Before using a restatement as an entry's summary in Step 3, confirm each fact it adds to the entry against the code, or against the dependency's shipped artifact when the fact concerns a dependency. When the fact is that a dependency provides a capability, also confirm that the dependency's documentation says the capability is available, since code present in the shipped artifact can be gated off, internal, or not yet public.
Classify each entry as:
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.