Triage

A skill for quickly assessing a design system's state and recommending which skills to run first, in what order, and why. Prevents the overwhelm of running all 40 skills when 3–5 would surface the critical findings.

Context

Design System Ops has 40 skills across 5 categories: audit, validate, document, govern, and communicate. Running all of them is comprehensive but overwhelming — especially for a team encountering the plugin for the first time. The triage skill reads the system's current state and produces a prioritised run plan: which skills to run first, which to skip for now, and which to return to later.

The triage skill is intentionally lightweight. It should take no more than 5 minutes of input-gathering and produce a run plan in under a minute. The value is in sequencing, not in depth — the subsequent skills provide the depth.

Boundaries

This skill produces a run plan — it does not run other skills itself. If the user wants a full automated sweep, point them to the /full-diagnostic agent instead. If the system has a single well-defined problem ("our tokens are a mess"), skip triage and go directly to the relevant skill. Triage is for when the team does not know where to start, not when they already know.

Step 1: Quick system scan

Gather the minimum information needed to assess the system's state. This is NOT a full audit — it is a triage scan.