triage

Invoke the triage workflow in natural language, such as "show me anything that needs my attention" or "let's look at #42". The Skill reads the full issue, checks the codebase for existing implementations, recommends a category and state, and waits for your direction before applying labels or comments.

A good agent brief describes behavioral contracts and acceptance criteria rather than file paths or line numbers, which go stale. It states current versus desired behavior, names key types and interfaces, lists independently testable criteria, and declares explicit out-of-scope boundaries.

Yes, external pull requests are treated as issues with attached code and move through the same state machine. For PRs, the Skill additionally checks out the diff, runs relevant tests to verify claims, and writes briefs describing what remains to finish the existing change.

Rejected enhancements are recorded in a `.out-of-scope/` directory with one markdown file per concept, capturing the decision, reasoning, and links to prior requests. During triage, new issues are matched against these files so prior rejections are surfaced instead of 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 possible.