# Triage

> Triage udecode/plate and udecode/plate-private issues and run their fixes from one entry. With no argument it records every new or changed issue in the triage focus, next work until launch, then cards the fix runs of triaged issues. An argument triages one issue or a label, records each stale or new issue and then cards the triage chips, fixes an issue, a domain or the next domain, or records a teammate's beta retest.

- Skill: `udecode/triage` (Agent Skill)
- Install (CLI): `npx get-skill add udecode/triage`
- Raw SKILL.md: https://api.skillmd.com/api/skills/udecode/triage/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: udecode (https://skillmd.com/u/udecode)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/udecode/triage

---


# Triage

Handle $ARGUMENTS.

The argument is the request after the word `triage`, so `/triage fix next` is `triage fix next` and `/triage` alone is `triage`. Run the Triage playbook, `.agents/playbooks/triage.md`, in full. Its Entry points table maps the request to its scope and its end. Load `pstack:poteto-mode` first, follow the steps of the pstack playbook the Triage playbook `extends` with its deltas applied, and run `check-playbooks.mjs` as `AGENTS.md`'s How work runs says, because this entry skips poteto-mode's routing.

