morning-triage

Morning triage — the loop's discovery move

A loop has five moves: discovery → handoff → verification → persistence → scheduling (see docs/20-loops.md). This skill is discovery — the move that finds the work. Skip it and you have the "blind loop": automated doing but a human still spends every morning deciding what to do. Discovery sets the ceiling on the whole loop — surface work of no value and the other four moves serve nothing.

The point is to let the loop find its own work, then stop exactly where a human should decide.

Read — the discovery inputs

Look at what changed since the last run (use gh and git; read-only):

• Failed CI since yesterday — gh run list --status failure --limit 30, read the failing step.
• Issues opened in the last 24h — gh issue list --search "created:>=<date>" --state open.
• Commits merged since the last run — git log --since=<last-run> --oneline.
• The previous state file — state/triage.md (so you don't re-discover handled work).

Judge — the part that sets the ceiling

For each candidate, decide — this is where judgment lives, don't skip it:

• Is it actionable now, or noise? (a timeout flake is noise; a real regression is work)
• Does it block a release? → priority.
• Is it already tracked in state/triage.md or an open issue/PR? → skip, don't duplicate.
• Is it deterministic (a script could decide it) rather than something needing a model? → prefer the deterministic path; keep the model for genuine judgment (the deterministic-gate principle).

Keep only what is worth a worktree today. A short, true list beats a long, padded one.

Write — the persistence output

Append each kept finding to state/triage.md (create it if absent) — one row, so tomorrow's run reads it back. The agent forgets; the repo does not.

| finding | source | priority | status |
|---|---|---|---|
| auth test flaky | CI #4821 | low | inbox |
| null deref on empty cart | issue #92 | high | handoff |
| stale dep: lodash | commit a3f1 | med | inbox |