What problem does it solve? It turns an approved SPEC SDD document into working code through disciplined test-driven development, ensuring every test maps to a numbered requirement or acceptance criterion instead of ad-hoc implementation. ## Core Features & Use Cases - SPEC-driven TDD loop: Reads .specs/SPEC-{YYYYMMDD}-{feature}.md files and executes one vertical slice per requirement (RF-###) or acceptance criterion (AC-###) using red-green-refactor cycles. - Spec validation script: Includes scripts/validate_spec.py to verify the SPEC file exists, has Approved status, and contains numbered requirements before execution begins. - Testing guidance references: Ships reference docs on mocking at system boundaries, testing public seams, refactoring candidates, deep modules, and interface design. - Use Case: A developer has an approved SPEC for a new checkout feature and asks the assistant to implement it; the skill writes one failing test per requirement, implements the minimum code to pass, refactors while green, and reports progress per slice in Portuguese. ## Quick Start Ask the assistant to execute the approved SPEC for your feature using test-driven development, for example by saying "run TDD from the spec for the checkout feature".
