apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user asks to \"backlog this\", \"note this idea\", or \"track this for later\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill backlog --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill backlog -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill backlog -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill backlog -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill backlog -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill backlog -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill backlog -a windsurf -y
name: backlog description: "Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user asks to \"backlog this\", \"note this idea\", or \"track this for later\"."
Capture improvement opportunities discovered during work so they don't get silently dropped. Appends to the `.turbo/backlog.md` file of the repo an improvement concerns.
Each repo keeps its backlog at `.turbo/backlog.md` relative to that repo's root. Resolve that root with `git -C <repo path> rev-parse --show-toplevel`, except inside a linked worktree — where `git -C <repo path> rev-parse --git-dir` differs from `--git-common-dir` — in which case use the parent of the common dir, so the entry lands in the main checkout rather than in a worktree that is destroyed with its branch.
Gather from context or `$ARGUMENTS`:
When the criteria above clearly select one value, use it. Otherwise, use `AskUserQuestion` to confirm; default to `plan` if the user declines to choose.
When a target repo holds the legacy `.turbo/improvements.md`, carry it into that repo's `.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` in each target repo if it exists. Create it with the header below if it doesn't.
**File header** (only when creating new):
# Backlog Out-of-scope improvement opportunities captured during work sessions. Review periodically and pull items into active work when appropriate.
**Entry format:**
### <one-line summary> - **Type**: <direct | investigate | plan> - **Category**: <category> - **Where**: `<file path or area>` - **Why**: <brief rationale> - **Ceiling**: <limit the shipped approach accepts> - **Revisit**: <condition that makes the fuller version worth building> - **Paired with**: <repo> — <title of the counterpart entry> - **Noted**: <YYYY-MM-DD>
Include the Ceiling and Revisit lines when the entry records a deliberate simplification, the Revisit line alone when the entry waits on an outside event, and a Paired with line per counterpart when the entry is one half of a split; omit them otherwise. Append the new entry at the end of each target file.
Tell the user the improvement was noted and where each entry was written, or that it could not be persisted and is printed above.
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…
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,…
Run autonomous task execution using the codex CLI. Use when the user asks to \"codex exec\", \"run codex exec\", \"execute a task…
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.