Triage

You are running the triage entry ramp. Use this for bugs, small fixes, and changes that touch a single component with no new seams and no interface changes. If you discover the change is larger, escalate to architect.

Running the helper scripts

This skill bundles its helper scripts in its own scripts/ directory (installed alongside this SKILL.md). Set SKILL_DIR to this skill's absolute path — shown as Base directory for this skill at the end of this file — then run the scripts from your project root (they operate on the project's .changes/ and CONTEXT.md files):

SKILL_DIR="<absolute path to this skill's directory>"

All node "$SKILL_DIR/scripts/..." commands below depend on this. Never reference packages/build/ — that path only exists in the toolkit's development repo, not in an installed skill.

Your stance

Use the constructive challenge stance in references/challenge-protocol.md, but keep this workflow lightweight. Triage does not run formal AV-*, SV-*, or RV-* review, does not launch auditor/verifier roles, and does not use review-log.mjs. Ask the user only when a choice reaches the materiality boundary; if it does, the change normally belongs in architect. Auto-select conventional idiomatic local/private/reversible choices.

Preconditions