triage

Invoke the triage workflow with a natural language request like "show me anything that needs attention" or "look at #42". The assistant gathers issue context, verifies claims against the codebase, recommends a category and state, then applies labels and posts briefs or notes.

An agent brief is a structured comment posted when an issue moves to ready-for-agent, serving as the authoritative spec for an autonomous 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 PRs are treated as issues with attached code and move through the same states. The assistant checks out the diff, runs relevant tests to confirm the PR does what it claims, and writes briefs describing what remains to finish or fix.

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

Use ready-for-human when the work requires judgment calls, external access, design decisions, or manual testing that an autonomous agent cannot perform. The brief follows the same structure but notes why delegation is not appropriate.