Skip to content

Tohuhono/Oberon / .agents/skills/triage

triage

Verified

Triage Oberon's GitHub issues and explicitly named PRs, verify requests, and write agent-ready briefs.

Triage

Use the gh CLI and ISSUES.md for GitHub operations and label roles.

Discover issues only. An explicitly named PR can also be triaged, regardless of author. Resolve issue and PR references with ISSUES.md; report lookup errors instead of treating them as missing items.

Every comment or issue posted to the issue tracker during triage must start with this disclaimer:

> *This was generated by AI during triage.*

Reference docs

Roles

Use the category and state roles defined in ISSUES.md. Every triaged item needs exactly one category and one state. Replace only conflicting category or state labels; preserve unrelated labels. If existing roles conflict, ask the maintainer before changing them.

For a PR, the same states read against the attached code: ready-for-agent means a brief is attached and an agent should take the next step on the diff; ready-for-human means it's ready for a human to merge.

State transitions: an unlabeled issue normally goes to needs-triage first; from there it moves to needs-info, ready-for-agent, ready-for-human, or wontfix. needs-info returns to needs-triage once the reporter replies. The maintainer can override at any time; flag transitions that look unusual and ask before proceeding.

Invocation

The maintainer invokes /triage and describes what they want in natural language. Interpret the request and act. Examples:

  • "Show me anything that needs my attention"
  • "Let's look at #42" (issue or PR)
  • "Move #42 to ready-for-agent"
  • "What's ready for agents to pick up?"

Show what needs attention

Query GitHub issues and present three buckets, oldest first:

  1. Unlabeled: never triaged.
  2. needs-triage: evaluation in progress.
  3. needs-info with reporter activity since the last triage notes: needs re-evaluation.

Show counts and a one-line summary per item. Let the maintainer pick.

Triage a specific issue or PR

  1. Gather context. Read the full issue or PR (body, comments, labels, author, dates; for a PR, the diff too). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using CONTEXT.md and ARCHITECTURE.md, respecting relevant ADRs under .agents/adr/. Run two checks against the codebase: (a) redundancy: search for an existing implementation of the requested behavior by domain concept (not just the request's wording), and report where you looked. If found, it's an already-implemented wontfix (step 5). (b) prior rejection: read .agents/out-of-scope/*.md when present and surface any record that resembles this request.

  2. Recommend. Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the request (including whether it's already implemented). Wait for direction.

  3. Verify the claim. Before any grilling, check that the claim holds up. For a bug, reproduce it from the reporter's steps. For a PR, inspect the diff and verify the claimed behavior. Protect current work before checking out a PR; stop if checkout would overwrite it. Follow TESTING.md for root reproduction commands and validation. Report what happened: confirmed (with code path), failed, or insufficient detail (a strong needs-info signal). A confirmed verification makes a much stronger agent brief.

  4. Grill (if needed). If the request needs fleshing out, call the Skill tool twice, for "grilling" and "domain-modeling", and grill it into shape a round of questions at a time, sharpening domain terms in CONTEXT.md and recording ADRs under .agents/adr/ as decisions land.

  5. Apply the outcome:

    • ready-for-agent: post an agent brief comment (AGENT-BRIEF.md).
    • ready-for-human: same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).
    • needs-info: post triage notes (template below).
    • For wontfix, close the issue or explicitly named PR, with the comment depending on why:
      • Already implemented: the change already exists in the codebase. Point to where it lives; do not write a rejection record for a built feature.
      • Rejected (bug): give a polite explanation, then close.
      • Rejected (enhancement): record the approved decision under .agents/out-of-scope/, link to it from a comment, then close (OUT-OF-SCOPE.md).
    • needs-triage: apply the role. Optional comment if there's partial progress.

Read back the item to confirm its category, state, comments, and open or closed status. Report failed operations explicitly rather than claiming the transition completed.

Quick state override

If the maintainer says "move #42 to ready-for-agent", trust them and apply the role directly. Confirm what you're about to do (role changes, comment, close), then act. Skip grilling. If moving to ready-for-agent without a grilling session, ask whether they want to write an agent brief.

Needs-info template

## Triage Notes

**What we've established so far:**

- point 1
- point 2

**What we still need from you (@reporter):**

- question 1
- question 2

Capture everything resolved during grilling under "established so far" so the work isn't lost. Questions must be specific and actionable, not "please provide more info".

Resuming a previous session

If prior triage notes exist on the issue or PR, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall