Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

implement-backlog

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 · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add tobihagemann/turbo --skill implement-backlog

About this skill


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"."

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.

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 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:

  • Summary (the ### heading)
  • Type (direct, investigate, or plan; may be missing in older entries — trivial and standard are accepted as legacy aliases for direct and plan)
  • Category
  • Where (file paths or areas)
  • Why (rationale)
  • Ceiling and Revisit (present when the entry records a deliberate simplification; Revisit alone when the entry waits on an outside event)
  • Noted (date)
  • Validated (present when an earlier run recorded what the entry's verdict rested on)

Step 2: Validate and Classify

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.

Reuse an Earlier Validation

Before validating, note the root of the checkout whose code this step reads (git rev-parse --show-toplevel) and its commit (git rev-parse --short HEAD). The path check for a commit and a set of repo-relative paths passes when git -C <root> diff --quiet <commit> -- <paths> exits 0 and git -C <root> ls-files --others --exclude-standard -- <paths> prints nothing.

For each entry carrying a Validated line, run the path check with its recorded commit and paths, and run each command nested under it from that root. When the path check passes and every command prints its recorded output, whatever its exit status, classify the entry with its recorded verdict and skip the rest of this step for it. Otherwise, including when a command cannot run, validate the entry in full.

Validate

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
Read the complete source ↗