S.08ISSUE TRIAGE

issue triage.

Read the issue. Estimate scope. Classify the component. Propose a reviewer and a sprint — before standup.

pick a fixture_

paste your own_

turnstile · invisible

waiting for verification token...

~/demo/issue-triage.log

idle · waiting for input

model_ —

pick a fixture on the left, then press [ run demo ].

~/issues/triage

triaging…

component: ──────
assigned: ──────
sprint: ──────

proposed · no side effects in demo mode

── log ──

no log entries yet

── how this works ──

01— ingest

GitHub issues, Jira tickets, Linear cards — wherever your team files bugs and requests.

02— reason

estimate scope and risk, classify the component, check for repro steps and impact.

03— act

assign a reviewer, propose a sprint, apply labels — or fast-track XS patches for auto-merge.

This demo runs on free-tier AI against fake data. In production, the same workflow writes to your real tools, logs every run, and is reversible — the reasoning step is the smallest part of the stack.

[ deploy one like this → ]