harden
Installation
SKILL.md
Harden
Deliberately upgrade the project's feedback harness — the commands, gates, and automation that make verification self-enforcing. Introduce lint, formatting, CI, and a canonical verify command intentionally and incrementally.
This resolves the tension between /pragma:skeleton ("no lint/format yet") and /pragma:slice ("run the verification harness").
Input
What to harden: $ARGUMENTS
Preconditions:
- A walking skeleton must exist. If none →
/pragma:skeletonfirst. - Ideally 1-2 real slices have landed (you want to know what checks actually matter before formalizing).
Procedure
1. Audit the current harness
What commands exist? Are they consistent? Is there a single "everything is green" command? Is there CI? Does CI match local?