Triage

Triage

Move raw tracker requests to a maintainer-approved state and handoff. Triage owns classification, verification, shaping, approved state transitions, briefs, and rejected-enhancement memory. Tracker docs own transport, label mappings, the Ready-for-agent contract, and Mutation read-back. $implement and $parallel-implement own code changes and implemented closeout.

Spine

1. Load. Read docs/agents/issue-tracker.md and docs/agents/triage-labels.md before tracker access. If either is absent or incompatible with triage, recommend $repo-bootstrap and stop. Follow docs/agents/domain.md for codebase context and read docs/agents/engineering-contract.md before reproduction, checkout, or executable validation. Triage PRs only when the tracker enables them. A named PR bypasses only external-author discovery; a PR is an issue with attached code.

2. Choose. Read one branch completely:

   • ATTENTION-SCAN.md — show incoming work needing maintainer attention.
   • SPECIFIC-ITEM.md — verify, shape, recommend, and apply one outcome.
   • QUICK-OVERRIDE.md — apply an explicitly named state with reduced discovery.

   Read AGENT-BRIEF.md only when preparing a ready-for-agent or ready-for-human brief. Read OUT-OF-SCOPE.md only when screening, rejecting, or reconsidering an enhancement.

3. Run. Follow only the selected branch; its helper owns branch-specific discovery, sequence, and completion criterion. Treat valid $to-tickets output as ready; re-enter triage only for an explicit state or brief correction.

   For any mutation branch, keep exactly one mapped category role and one mapped state role; surface missing or conflicting roles before mutation. Mutate only an explicitly approved packet; any packet change requires fresh approval. A ready-for-agent outcome satisfies the tracker's Ready-for-agent contract and adds verification evidence.

   Prefix every posted issue or comment with:

   > *This was generated by AI during triage.*
   

4. Prove. Complete at the selected branch's criterion. An Attention Scan ends after its read-only criterion with tracker state unchanged. A mutation branch ends only after the approved packet is applied, read back, and returned as a triage packet confirming role invariants, disclaimer, required brief or rejected-enhancement record, shaping domain deltas, partial failures, skipped checks, and blockers.