loom-intake-triagelisted

# loom-intake-triage Intake triage is a front-door playbook for incoming work. It classifies reports, gathers enough context to decide the next route, and turns ready work into Loom tickets or records without letting external trackers become the live execution ledger. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-tickets`, `loom-evidence`, `loom-research`, `loom-specs`, `loom-knowledge`, `loom-constitution`, `loom-ralph`, and `loom-audit`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. External issues, labels, and comments can transport work. Loom tickets carry live execution state. ## Use This Playbook When Use this playbook when: - a bug report or feature request arrives - an external issue needs classification or response - a maintainer asks what needs attention - a report may be ready for a ticket-owned worker run - an issue needs more information from the reporter - a request should be rejected with durable rationale - external labels or states need reconciliation with Loom tickets Skip it when the work already has a ready Loom ticket and no intake decision remains. ## Route Use this route: ```text collect -> classify -> investigate -> decide -> brief -> record -> synchronize ``` ## Collect Read the full report before deciding. Collect: - reporter claim and desired outcome - current behavior and expected behavior - comments, att