agentsclimarketplace
Sign in

Triage review

Skill vergil-project/vergil-claude-plugin/skills/triage-review

Groom the triage intake queue — review uncurated issues and route each into the epic/task model. Use when the human asks to "review triage", "groom the backlog", "process the triage queue", "what's in triage", or wants the periodic (roughly weekly) intake pass. Collects every `triage`-labelled issue across the org and walks the human through dispositioning them one at a time.From its SKILL.md

Install
npx -y skills add vergil-project/vergil-claude-plugin --skill triage-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, as published. Nobody here has run it

Triage review

Overview

triage-capture fills a lossless net of triage-labelled issues. This skill empties it: a human-in-the-loop pass that routes each uncurated issue into the epic/task model, so the queue stays small and nothing rots. Run it on a cadence (weekly-ish) or whenever the queue feels heavy.

When to use

"review triage", "groom the backlog", "process the triage queue", "what's in triage", "let's do intake".

Workflow

  1. Collect the queue (cross-repo). Gather every triage issue across the org's managed repos and vergil-project/.github:

    vrg-gh issue list --repo <owner>/<repo> --label triage \
  --json number,title,url,body

    Run per repo (or via search) and assemble one list. Report the count.

  2. Disposition each issue, one at a time. Present the issue, recommend a disposition, and let the human confirm before acting. Pick exactly one:

    DispositionAction
    DropDuplicate / wontfix / already done → close it.
    Assign to an existing epicIt's a task in an initiative → native-link it under that epic.
    Route to the standing epicSmall ad-hoc work → native-link under the repo's Ad-hoc maintenance standing epic.
    Promote to a new epicA real seed → start superpowers:brainstorming to create a finite epic; this issue becomes/links to it.

    Prefer assigning to an existing epic over the standing bucket ("a forgotten to-do in that project").

  3. Apply the disposition:

    • Link (assign / route): vrg-epic-link --epic <owner>/.github#<EPIC> --task <owner>/<repo>#<N> to create the native sub-issue link.
    • Remove the triage label (it has entered the model): vrg-gh issue edit <N> --repo <owner>/<repo> --remove-label triage (add a kind label if missing).
    • Drop: closing an issue is a human action — agents are denied issue close. Tell the human to close it (or do it via ! vrg-gh issue close …).

  4. Stop when the queue is empty (or the human calls it). Report what was assigned, routed, promoted, and dropped.

Notes

  • Deeper automation of this grooming (batch auto-close, stale detection) is tracked separately; this skill is the human-in-the-loop version.
  • "Promote to a new epic" is the on-ramp into the formal path — it's how a dog-walk seed becomes a planned initiative.
  • Removing triage is what moves an issue into the model; until then it stays exempt from the every-task-needs-an-epic rule.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.