← ClaudeAtlas

implement-backloglisted

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".
tobihagemann/turbo · ★ 421 · Code & Development · score 89
Install: claude install-skill tobihagemann/turbo
# Implement Backlog 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. Resolve the repo root as Step 1 does, read each working-set entry in full from `.turbo/backlog.md` under it, and run the lane with each entry's full text alongside what was passed in. When an entry is not there, run the lane with what was passed in for it. ## Task Tracking 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 ## Step 1: Read 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 lega