triage

Invoke the triage workflow with a natural language request like "show me anything that needs my attention" or "let's look at #42". The assistant reads the issue, checks the codebase for redundancy and prior rejections, then recommends a category and state before applying labels and comments.

An agent brief is a structured comment posted when an issue moves to ready-for-agent, serving as the authoritative specification for an autonomous coding agent. It describes desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing fragile file paths or line numbers.

Yes, external pull requests are treated as issues with attached code and move through the same state machine. The assistant checks out the diff, runs relevant tests to verify claims, and writes briefs describing what remains to be finished on the existing code.

Rejected enhancement requests are recorded as concept files in a .out-of-scope/ directory with the decision, reasoning, and prior issue links. During triage, new requests are matched against these files by concept similarity so prior rejections are surfaced instead of re-litigated.

Issues requiring judgment calls, external access, design decisions, or manual testing go to ready-for-human. The brief uses the same structure as an agent brief but notes why the work cannot be delegated to an autonomous agent.