gaia-triagelisted

# gaia-triage Triage has three workstreams — GitHub issue hygiene, skill-batch intake review, and the cross-repo prioritization sweep. Run them independently or together depending on what the user asks for. All three produce documented, auditable decisions rather than silent changes. This skill absorbed `favorchurch/rock-steward`'s `rock-triage` (2026-09-01): its impact sizing, priority matrix, four-step inspection, and prioritized-matrix output landed here as **Workstream 3** rather than shipping as a second, competing triage skill. There is one `gaia-triage`. Its priority ladder is the `P0`-`P4` ladder `/gaia-meta-audit` and `/gaia-meta-sweep` already use — one vocabulary, not two. Triage is **not** cartography. Sorting a backlog of known work is this skill; planning an effort too big for one session as a map of decision tickets is `/wayfinder`. Taking one triaged issue end-to-end to a PR is `/gaia-issue-resolver`. --- ## Headquarters **Every issue lives on `gaia-research/gaia-skill-tree`**, regardless of which repo the fix lands in. One tracker for the whole org. ```bash export GAIA_HQ=gaia-research/gaia-skill-tree ``` Tag the target repo on the issue when the work lands elsewhere — a line at the top of the body, `**Target repo:** \`gaia-research/gaia-skill-heaven\``, matching the `/wayfinder` convention. Cross-repo references use the full `gaia-research/<repo>#<n>` form; a bare `#<n>` always resolves to HQ. --- ## Classification taxonomy Every triaged issue get