Menu
Confirm the target contract's tests fail for the right reason before implementing — new work or rework, never a test defect.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | confirm-red-failure |
| description | Confirm the target contract's tests fail for the right reason before implementing — new work or rework, never a test defect. |
import pytest when the test used it for nothing else — run ruff and drop the unused import; that is a lint side-effect of un-marking, not a behaviour edit. Do not author tests; they already exist with full bodies.ImportError THEN new work; IF the source .py exists but is stale against the changed contract and an assertion fails THEN rework. Either is the right reason per [[software-craft/tdd]]..cache/<session_id>/journal.md (contract, the gap, the evidence) and fire reveals-gap. This routes back to plan, not green.Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.
Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.
Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis.
Funnel level 1 — establish the big picture with seven broad questions, applying CIT, Laddering, and CI Perspective throughout.
Squash-merge the feature commits into dev, regenerate docstrings, and verify the whole suite plus whole-suite stubtest are clean.
Publish the delivered batch as release notes, a PR to main, or a tagged release.