keel-triagelisted

# keel-triage Use this skill when the user asks to run the keel command `triage` (e.g. `keel triage ...`, `triage <args>`, or `/keel:triage`). It reads every project value from `.keel/project.yaml` via the `keel` CLI. # /keel:triage ## Live progress — stamp this run (required) So this run shows live on `keel-visual`'s board, record it with `keel activity` **as you go**. This command's phases are: `config` → `find` → `tier` → `classify` → `rank` → `apply` → `summary`. Pick one stable `--run-id` for the whole run (e.g. `triage-<issue-or-pr>`): - **Right now, before the work below**, stamp the first phase: `keel activity .keel/project.yaml --root . --write --command triage --run-id "$RUN" --phase config` - Re-run with the next `--phase` (`find`, …) **as you advance** through the flow. - At the end: `keel activity .keel/project.yaml --root . --run-id "$RUN" --done` Treat this like any other contractual step — do not skip it. The one allowed exception is a core too old to ship `keel activity` (keel < 1.6.0): then skip it silently and never block the command. ## Command step evidence Every numbered step in this command is contractual. Complete the step, record the evidence it asks for, or explicitly mark it `N/A — <reason>` before moving on. If a step has an external side effect such as a GitHub comment, issue, review, report, branch, or PR, the side effect must be posted or written through the selected transport and cited in the final summary. Never silently skip a step