snag

What problem does it solve?

When you encounter an unexpected defect, bug, or regression mid-development work, it is tempting to jump straight to a quick first-draft patch that may miss the root cause, introduce new issues, or waste effort on a problem that needs a larger dedicated effort. This skill eliminates that reflex by interposing a triage step between flaw discovery and any fix work.

Core Features & Use Cases

• Size-based triage: Rates flaws by blast radius and judgment required (not line count) into trivial, small/medium, or large categories.
• Three routing paths: Sends trivial issues to zero-ceremony immediate fixes, small/medium issues to a structured 5-gate remediation process with optional sub-agent delegation, and large issues to tracked work via /log followup or /start-project.
• Use case: If you are working on JellyRock and spot a regression in the playback OSD, invoke /snag to get a clear triage and next steps instead of guessing at a patch.

Quick Start

Invoke the /snag skill the moment you spot an unexpected defect mid-work to receive a triage of its size and the correct next steps before drafting any fix.