atomized-briefingWrite an implementation plan / worker briefing as atomized 2-5 minute steps with exact file paths, explicit Consumes/Produces interfaces, and zero placeholders — so a context-free executor (formation worker, spawned subagent, or future you) can run it without re-deriving intent. USE WHEN briefing a
calibrated-verificationEvery verification script, test, scanner, or matcher must ship with a calibration pair — a known positive it provably catches and a negative control it provably passes — and must print its denominator (scanned N / matched M / dropped K). "All clean" from an uncalibrated checker is indistinguishable
root-cause-debuggingFour-phase debugging protocol with one Iron Law: no fix without root-cause investigation first. Includes the 3-failed-fixes circuit breaker that escalates from "try another patch" to "question the architecture". USE WHEN hitting any bug, test failure, or unexpected behavior — and ESPECIALLY under ti
skill-tddAuthor or edit an agent skill using the TDD loop: run a baseline pressure scenario WITHOUT the skill (RED), write the minimal skill that fixes the observed failure (GREEN), then close the loopholes agents actually used (REFACTOR). USE WHEN creating a new SKILL.md, editing an existing one, or when a