verification-discipline Skill

Source

• Creator: microsoft
• Repository: microsoft/amplifier-bundle-skills
• Skill file: skills/verification-discipline/SKILL.md

What it does

Use when verifying that completed work actually works. Auto-surface during /verify mode, post-implementation review, or before claiming a task is done. Teaches the discipline of testing outcomes vs implementation, the unit/integration/smoke gradient, and what "done" actually means.

Skill instructions

Verification Discipline The Principle Unit tests verify that code-as-written behaves as-written. Smoke and integration tests verify that the system achieves the intended outcome. Those are different questions. You need both. "All unit tests pass" is necessary. It is rarely sufficient. A finding from the field: four consecutive integration-blocking bugs, all of which passed unit tests, all of which would have been caught by a five-minute smoke test on a fresh environment. The bugs were not exotic — they were the cost of declaring "done" too early. The Four Failure Modes 1. Tests written from the implementation outward miss scenarios the code doesn't anticipate. The engineer writes code, then writes tests that exercise the code as written. The tests ask "does this code do what I wrote it to do?" They don't ask "what scenarios does the system need to handle?" 2. Mocks verify shape, not behavior. A mocked dependency returns the value you told it to return. That tells you nothing about whet