triage

Files (4)

• AGENT-BRIEF.md
• OUT-OF-SCOPE.md
• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Triage

Move issues on the project issue tracker through a small state machine of triage roles.

If the issue-tracker config includes external pull requests, triage them too. **A PR is an issue with attached code.** It uses the same roles and states, with the differences marked below. Resolve a bare `#42` to an issue or PR per the tracker config.

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

- [AGENT-BRIEF.md](AGENT-BRIEF.md). How to write durable agent briefs
- [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md). How the `.out-of-scope/` knowledge base works

## Roles

Two **category** roles:

- `bug`. Something is broken
- `enhancement`. New feature or improvement

Five **state** roles:

- `needs-triage`. Maintainer needs to evaluate
- `needs-info`. Waiting on reporter for more information
- `ready-for-agent`. Fully specified, ready for an AFK agent
- `ready-for-human`. Needs human implementation
- `wontfix`. Will not be actioned

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.

Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.

These are canonical role names. The actual label strings used in the issue tracker may differ. Run `setup` if the mapping is missing.

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 the issue tracker 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.

When PRs are in scope, include external PRs in these buckets and tag each line `[PR]` or `[issue]`. Discovery surfaces only *external* PRs (the tracker config defines who counts as external). A collaborator's in-flight PR is not triage work. This filter is discovery-only; an explicitly named PR is always triaged regardless of author.

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, and dates. Read the diff for a PR.
   - Parse prior triage notes so you do not ask resolved questions again.
   - Explore the codebase using the project's domain glossary. Respect ADRs in the area.
   - Check for **redundancy**. Search by domain concept for an existing implementation of the requested behavior, and report where you looked. If found, classify it as an already-implemented `wontfix` in step 5.
   - Check for **prior rejection**. Read `.out-of-scope/*.md` and report any similar request.

2. **Recommend.** Tell the maintainer your category and state recommendation with reasoning. Include a brief codebase summary and whether the request is already implemented. Wait for direction.

3. **Verify the claim.** Before any planning, check that the claim holds up. For a bug, reproduce it from the reporter's steps. For a PR, confirm the diff does what it claims. Check it out, run the relevant tests or commands. 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. **Plan if needed.** Run `lets-plan-code` and `domain-modeling` together. Resolve one question at a time, sharpen domain terms, and update `CONTEXT.md` or ADRs after each decision.

5. **Apply the outcome:**
   - `ready-for-agent`. Post an agent brief comment ([AGENT-BRIEF.md](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).
   - `wontfix`. Close, with the comment depending on *why*:
     - **Already implemented.** The change already exists in the codebase. Point to where it lives; do **not** write to `.out-of-scope/` (that KB is for *rejected* requests, not built ones).
     - **Rejected (bug).** Polite explanation, then close.
     - **Rejected (enhancement).** Write to `.out-of-scope/`, link to it from a comment, then close ([OUT-OF-SCOPE.md](OUT-OF-SCOPE.md)).
   - `needs-triage`. Apply the role. Optional comment if there's partial progress.

## 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 planning. If moving to `ready-for-agent` without a planning session, ask whether they want to write an agent brief.

## Needs-info template

```markdown
## 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 planning 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.

From terebentina/skills, MIT.

More from terebentina/skills