loom-test-driven-developmentlisted

# loom-test-driven-development Test-driven development is a Loom execution playbook for behavioral claims. It turns the intended behavior into a failing check, drives the smallest change to green, and preserves the red/green story as evidence when the ticket will rely on it. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-specs`, `loom-tickets`, `loom-ralph`, `loom-evidence`, and `loom-audit`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. TDD is usually expressed as `Verification Posture: test-first` in the ticket or ticket-owned Ralph worker run. ## Use This Playbook When Use this playbook when: - implementing new behavior or changing existing behavior - fixing a bug that can be reproduced with a check - adding edge-case handling - changing logic that could regress - a ticket acceptance criterion can be proved with an executable check Skip it for prose-only edits, static content, or configuration changes with no behavioral claim. ## Route Use this route: ```text contract -> red -> green -> refactor -> evidence -> audit-ready ``` ## Contract Start from the behavior contract: - spec `REQ-*` and `SCN-*` when the behavior is durable - ticket `ACC-*` when the claim is scoped to the work unit - bug report, reproduction, or evidence record when fixing a defect If expected behavior is unclear, route to `loom-specs` before writing tests. ##