- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill backlog -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill backlog -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill backlog -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add tobihagemann/turbo --skill backlog -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/tobihagemann/turbo/tree/HEAD/claude/skills/backlogFrom the publisher
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:
direct, investigate, or plan — see criteria belowrefactor, performance, reliability, readability, testing, docs, dx (developer experience), or feature/implement.When the criteria above clearly select one value, use it. Otherwise, use AskUserQuestion to confirm; default to plan if the user declines to choose.
.turbo/backlog.md of the repo whose files its Where names, which may not be the current repo.AskUserQuestion to ask where it is cloned, offering as the alternative to note its entry in the backlog of the repo root resolved in Step 1. Given a path, route the entry to the repo at that path. Without one, say that the checkout was not found and append the entry to that backlog, naming the repo it was meant for..turbo/, which is gitignored and is destroyed with the worktree.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.
trivial or standard, rewrite the Type to direct or plan respectively so the file converges on current vocabulary..turbo/ directory, use AskUserQuestion to confirm the location before creating one.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\
---name: backlogdescription: Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task…---# claude/skills/backlog/SKILL.mdOverview
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\".
FAQ
Download claude/skills/backlog/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/tobihagemann/turbo.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.