Agent skill

Triage Improvements

by tobihagemann in tobihagemann/turbo

Triage the improvements backlog at .turbo/improvements.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop.

MITAuto-check passedProduct & Project Management

Install Triage Improvements

skills CLI
$ npx skills add tobihagemann/turbo --skill triage-improvements -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tobihagemann/turbo triage-improvements --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/triage-improvements .claude/skills/triage-improvements && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
triage-improvements
GitHub stars
408
Token cost
~963 tokens
SKILL.md length
534 words
Files
1
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Triage the improvements backlog at .turbo/improvements.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop.

  • Works in 4 steps: Read the Backlog and Merge Duplicates → Assess Each Entry → Decide Keep or Drop → …
  • The user asks to triage improvements
  • SKILL.md covers Step 1: Read the Backlog and…, Step 2: Assess Each Entry, Step 3: Decide Keep or Drop and Step 4: Report
  • Calls git

What it does

Triage Improvements is an agent skill from tobihagemann/turbo. Triage the improvements backlog at .turbo/improvements.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop. Use when the user asks to "triage improvements", "triage the backlog", "clean up the backlog", "clean up improvements", "groom the backlog", "prune the improvements backlog", or "go through the backlog with me".

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering User stories. It works with Git. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.

When your agent uses it

  • The user asks to triage improvements
  • Triage the backlog
  • Clean up the backlog
  • Clean up improvements

Example prompts

  • “triage improvements”
  • “triage the backlog”
  • “clean up the backlog”
  • “/triage-improvements”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Read the Backlog and Merge Duplicates
  2. Assess Each Entry
  3. Decide Keep or Drop
  4. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 931eda5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Triage Improvements loads about 963 tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~963

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tobihagemann/turbo at commit 931eda5, republished under its MIT licence (© tobihagemann). 534 words, ~963 tokens.

Download SKILL.mdSave it as .claude/skills/triage-improvements/SKILL.md (or your agent's skills folder).
name
triage-improvements
description
Triage the improvements backlog at .turbo/improvements.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop. Use when the user asks to "triage improvements", "triage the backlog", "clean up the backlog", "clean up improvements", "groom the backlog", "prune the improvements backlog", or "go through the backlog with me".

Triage Improvements

Decide, entry by entry, which improvements in .turbo/improvements.md are worth keeping.

Step 1: Read the Backlog and Merge Duplicates

Read .turbo/improvements.md, relative to the repo root resolved 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 the file does not exist or holds no entries, present "No improvements to triage." Then call update_plan to mark this step completed and continue with the next step of the active workflow.

Merge entries that cover the same improvement into one entry that keeps every detail either held, write the merged entries back, and output which ones were merged. Update each Paired with line in counterpart entries that names a title the merge retired.

Number the remaining entries in file order.

Step 2: Assess Each Entry

Work from each entry's own text. Read the code an entry names only when its text is too thin to say what the entry is for.

For each entry, settle the two parts its question in Step 3 carries, without outputting them yet:

  • Story — one sentence naming who benefits and what they get, in plain language a reader who has not seen the code can follow. When nothing changes for the person using the software, tell it from the maintainer's side: what the entry simplifies.
  • Recommendation — keep or drop, with a one-line reason.

Recommend keeping an entry that serves a goal the person using the software actually has, fixes a problem that was observed, or simplifies existing code. Recommend dropping one that is theoretical or was never observed, is decoration, would be resolved by another entry's fix, or adds machinery no requirement demands. For an entry carrying a Revisit line, apply these criteria to the fuller version it describes as though its condition held; the condition being unmet is no ground to drop it. When the entry's text settles neither, recommend neither and name what is unclear.

Show full SKILL.md (205 more words)Show less

Step 3: Decide Keep or Drop

Use request_user_input, one question per entry in number order, filling each call to its three-question limit:

  • Header — #<number>
  • Question — the entry's summary, then its story, then what is unclear when Step 2 recommended neither, ending with "Keep or drop?"
  • Options — Keep and Drop. Place the recommended one first with "(Recommended)" appended and put the reason in its description. In the other's description, say what choosing it gives up. When neither is recommended, list Keep first unlabeled and say in each description what choosing it gives up.

After each call, delete the entries the user dropped from .turbo/improvements.md. When a dropped entry carries a Paired with line, remove that reference from each counterpart entry it names. When an answer asks a question or gives an instruction in place of a choice, act on it, then ask about that entry again when keep or drop is still open.

Repeat until every entry is decided.

Step 4: Report

Delete .turbo/improvements.md when no entries remain. Output the entry count as read and the count remaining, followed by the summaries of the dropped and merged entries.

Then call update_plan to mark this step completed and continue with the next step of the active workflow.

© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in codex/skills/triage-improvements of tobihagemann/turbo.

Open the folder on GitHubat commit 931eda5

Compare with similar skills

Triage Improvements next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Triage Improvements compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Triage Improvements this skilltobihagemann/turbo408—~963Automated safety check: PassMIT
Atomic Spec Orchestratorultralisp/ultralisp258—~3.4kAutomated safety check: PassNone
Execute Issuelbedner/aegis-stack143—~1.1kAutomated safety check: PassMIT
Task Reviewer ChorusChorus-AIDLC/Chorus1.2k—~5.3kAutomated safety check: PassAGPL-3.0
Acceptance Criteria Checkshopsys/shopsys350—~1kAutomated safety check: PassCustom licence
Bmad Handoffaj-geddes/claude-code-bmad-skills488—~2kAutomated safety check: PassCustom licence

Similar skills

  • Atomic Spec Orchestrator

    ultralisp/ultralisp

    AI-агент — эксперт-оркестратор разработки по методологии Atomic Spec.

    258 GitHub stars~3.4k tokensUpdated 28 days ago
    Product & Project ManagementAuto-check passed
  • Execute Issue

    lbedner/aegis-stack

    A skill your agent uses when handed a GitHub issue (number or URL) to execute end to end.

    143 GitHub stars~1.1k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Task Reviewer Chorus

    Chorus-AIDLC/Chorus

    Read-only adversarial Chorus task reviewer — independently verifies an implementation against its acceptance criteria and posts a single structured VERDICT comment.

    1.2k GitHub stars~5.3k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright.

    350 GitHub stars~1k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed
  • Bmad Handoff

    aj-geddes/claude-code-bmad-skills

    Emits a dev-tool-agnostic handoff manifest from ready-for-dev stories so an external dev plugin or runner can pick up and execute the work.

    488 GitHub stars~2k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

More from tobihagemann/turbo

All 81 skills in this repo
  • Consult Oracle

    tobihagemann/turbo

    Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.

    408 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Fetch PR Comments

    tobihagemann/turbo

    Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.

    408 GitHub stars~967 tokensUpdated 2 days ago
    Auto-check passed
  • Recall Rationale

    tobihagemann/turbo

    Recall why a past change was made by locating the Claude Code transcript that produced it.

    408 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed
  • Resolve PR Comments

    tobihagemann/turbo

    Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.

    408 GitHub stars~3.8k tokensUpdated 2 days ago
    Auto-check passed
  • Resolve PR Comments

    tobihagemann/turbo

    Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.

    408 GitHub stars~3.8k tokensUpdated 2 days ago
    Auto-check passed
  • Assess Technical Debt

    tobihagemann/turbo

    Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.

    408 GitHub stars~2.8k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Triage Improvements

What does Triage Improvements do?

Triage the improvements backlog at .turbo/improvements.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop. Triage Improvements is an agent skill from tobihagemann/turbo.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop.

When should I use Triage Improvements?

Triage Improvements fits situations like: the user asks to triage improvements; triage the backlog; clean up the backlog; clean up improvements.

How do I install Triage Improvements in Claude Code?

Run `npx skills add tobihagemann/turbo --skill triage-improvements -a claude-code`. Or copy the skill folder (codex/skills/triage-improvements in tobihagemann/turbo) into .claude/skills/triage-improvements in your project. Claude Code loads it when a task matches its description.

How do I install Triage Improvements in Codex?

Run `npx skills add tobihagemann/turbo --skill triage-improvements -a codex`. Or copy the skill folder (codex/skills/triage-improvements in tobihagemann/turbo) into .agents/skills/triage-improvements in your project. Codex loads it when a task matches its description.

Can I use Triage Improvements in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill triage-improvements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-improvements, .gemini/skills/triage-improvements, .github/skills/triage-improvements and .opencode/skills/triage-improvements in your project.

What does Triage Improvements need to run?

Going by SKILL.md and its folder, Triage Improvements needs the command-line tools its instructions call (git).

Does Triage Improvements access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Triage Improvements safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Triage Improvements use?

Triage Improvements is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Triage Improvements use?

About 963 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Triage Improvements?

Skills that share tags, products or a category with Triage Improvements: Atomic Spec Orchestrator (ultralisp/ultralisp, 258 stars), Execute Issue (lbedner/aegis-stack, 143 stars), Task Reviewer Chorus (Chorus-AIDLC/Chorus, 1.2k stars) and Acceptance Criteria Check (shopsys/shopsys, 350 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triage Improvements?

tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 408 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.

Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.