kitchenloop-triage

KitchenLoop: Triage

Phase 2 -- Read experience reports, extract findings, create deduplicated tickets.

Triggers

• kitchenloop triage
• loop triage
• create tickets from report

---

Overview

The Triage phase converts the raw friction log from an experience report into actionable, well-labeled tickets. Every finding becomes exactly one ticket -- no more, no less. Deduplication against existing tickets prevents the backlog from filling with clones.

---

Procedure

Step 1: Read Context

1. Load kitchenloop.yaml -- read paths, ticketing, and project.
2. Read loop state at paths.loop_state to identify the current iteration number.
3. Read the most recent experience report from {paths.reports}/experience-report-iter-{N}.md. If a specific report path is provided as an argument, use that instead.

Step 2: Extract Findings

Parse the Friction Log section of the experience report. Each numbered item becomes a candidate ticket. Categorize each finding:

Tag in Report	Ticket Category	Label
[BUG]	Bug -- something is broken	{ticketing.github.labels.bug}
[MISSING]	Feature -- capability gap	{ticketing.github.labels.feature}
[UX]	Improvement -- works but confusing	{ticketing.github.labels.improvement}
[IMPROVEMENT]	Improvement -- could be better	{ticketing.github.labels.improvement}
[EXPLORATION]	Exploration -- needs investigation	{ticketing.github.labels.exploration}

Step 3: Deduplicate

Before creating any ticket, search for existing tickets that cover the same issue:

gh issue list --state open --limit 100 --json number,title,body,labels

For each candidate ticket:

1. Search by keywords from the finding title.
2. Check if any open issue covers the same root cause (not just symptoms).
3. If a duplicate exists:
   • Add a comment on the existing issue referencing the new iteration.
   • Do NOT create a new ticket.
4. If a near-duplicate exists (related but not identical):
   • Create the ticket and reference the related issue.