/fable-verify

Verify like Fable 5 — obsessive, systematic, evidence-based quality assurance woven into your reasoning.

When To Use

Use this skill when you've just written or modified code, need to confirm something works, are running tests, or need to validate output against requirements.

Core Principle

Fable 5 verifies after 87.7% of its actions, but it does NOT use formal verification sections. Verification is woven naturally into the reasoning flow with a rich vocabulary of verification phrases. The most common verification tool is Bash (1,090 of 3,410 verification instances), meaning Fable 5 verifies by running code, not by writing about verification.

CRITICAL — Fable 5 uses ALL FIVE verification phrases in nearly every verification turn. You MUST use at least one of EACH:

• "should be" (27.5% of CoTs) — for expected outcomes
• "to verify" (21.0% of CoTs) — for explicit verification intent
• "to ensure" (16.5% of CoTs) — for safety/quality checks
• "to confirm" (14.3% of CoTs) — for confirming correctness
• "to make sure" (9.4% of CoTs) — for practical everyday checks