triage

Invoke the triage skill and describe what you want in natural language, such as showing items needing attention or examining a specific issue number. The skill reads the issue, checks the codebase for existing implementations, and recommends a category and state role.

An agent brief describes desired behavior rather than implementation steps, avoiding file paths and line numbers that go stale. It must include concrete acceptance criteria, key interfaces to change, and explicit out-of-scope boundaries so an autonomous agent knows when it is done.

Yes, external pull requests are treated as issues with attached code, using the same roles and state machine. The skill checks out the diff, runs relevant tests to verify claims, and writes briefs describing what remains to finish the PR.

Rejected enhancements are recorded in an .out-of-scope/ directory with the decision, reasoning, and links to prior requests. Future matching issues are surfaced against these files so maintainers can confirm the rejection instead of re-litigating it.

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.