triple-verify

3 Approaches

E1 — Testing	E2 — Static	E3 — Build/Runtime
Unit/integration/e2e	Lint, 4R, secrets	Build, dry-run, schema
Tests pass, bug repro	No regressions	Build OK, runtime checks
Schema validate, PSSA	Lint, 4R review	Dry-run, -WhatIf

Workflow

Mode routing (keyword overrides):

• !ship/!listo → quality-gate → triple-verify (por zona) → commit-crafter → commit+push
• !fast → quality-gate → commit+push (skip verify)
• !check → quality-gate only (no commit)
• !draft → no gates
• (no keyword) → zona determina verify depth quality-gate ALWAYS mandatory in !ship/!fast/!check regardless of zone. Zone only affects triple-verify, NOT quality-gate. Zone routing (verify depth, when keyword didn't route):
• Verde → SKIP verify → quality-gate if commit
• Amarilla ≤10L → quality-gate
• Rojo/Amarilla >10L → TRIPLE VERIFY (E1+E2+E3 parallel)
• Fail → STOP + evidence · Pass → continue

Rules

1. 3 DISTINCT approaches: behavior + quality + compilation
2. Default-FAIL: no evidence of 3 steps → not verified
3. Build mandatory for compilable code
4. !ship = responsibility: quality-gate NEVER optional
5. capture-learnings (inline): run scripts/session-miner.ps1 -Mode scan -Json post-task or pre-commit. Parse JSON for new patterns → .learnings/. mem_save decisions/bugfixes to Engram. Skip if unavailable. Stage .learnings/.
6. Override: !ship --no-verify emergency only
7. Self-improvement override: difficulty levels from CYCLE.md override verify depth

Reference

docs/skills/triple-verify/reference.md

Anti-Rationalization

Rationalization	Red Flag	Verification
"2 de 3 enfoques bastan si coinciden"	Omitir un enfoque porque otros dos pasaron	Exigir SIEMPRE E1+E2+E3 distintos (behavior+quality+compilation), Default-FAIL si falta uno
"E2 static es suficiente para refactors"	Solo lint/4R sin tests ni build	Rojo/Amarilla >10L → E1+E2+E3 en paralelo; build mandatory si compilable, tests de repro obligatorios
"thresholds iguales para todas las zonas"	Misma profundidad verify para Verde y Rojo	Zone routing: Verde→SKIP, Amarilla ≤10L→quality-gate, Rojo/Amarilla >10L→TRIPLE VERIFY; quality-gate siempre en !ship

Red Flags

• Doing work without checking output format → STOP, re-read skill
• Second occurrence of same rationalization → force RED zone

Verification

• Output matches skill ## Output contract + file:line citaton
• cross-ref-check.ps1 → SKILL.md OK

Refs

Cross-Refs: trial-verify | testing-strategy