triage

Triage classifies unchecked captures from CAPTURES.md into structured work items like quick-fixes, new beads, deferrals, or reopens. It evaluates each capture against policy and enriches them with context and acceptance criteria for autonomous agent execution.

Triage streamlines backlog management by reading your capture list, evaluating urgency and context, and coordinating with the beads system. It ensures every item receives clear acceptance criteria, context, and candidate actions to maintain visible progress.

Captures are classified into quick-fix, new-bead, inject, reopen, defer, or out-of-scope categories. The process reads prior decisions from DECISIONS.md and references recent activity to maintain continuity while generating actionable work items.

Yes, triage enriches captures by adding context and acceptance criteria required for autonomous agent work. It coordinates with the beads system via the br CLI to create and update work items, ensuring each capture includes clear candidate actions.

Triage works by coordinating with the beads system when available, but it can independently classify captures from CAPTURES.md. It reads prior decisions and evaluates each item against policy to generate structured work items with robust guidance on escalation and status updates.

Deferring captures categorizes them as out-of-scope or lower priority based on urgency and context evaluation. This approach keeps your backlog clean by ensuring only actionable items with clear acceptance criteria progress, while deferrals maintain context for future reassessment.