10x-tdd

What problem does it solve? Executing a multi-phase implementation plan with test-first discipline is hard to sustain manually: tests get written after the code, progress tracking drifts, and commits mix unrelated changes. This Skill drives an approved plan from context/changes/<change-id>/plan.md through strict red-green-refactor cycles, one phase at a time, with enforced progress tracking and per-phase commits. ## Core Features & Use Cases - Phase-by-phase TDD execution: For each plan phase, writes a failing test first, then minimal production code to pass it, then refactors while staying green. - Eligibility gating: Before each phase, checks that the implementation is absent and the phase is genuinely testable; redirects scaffolding, config, or already-implemented phases to /10x-implement. - Shared progress state: Mutates the same ## Progress section in plan.md as /10x-implement, so phases can be interleaved between the two skills without losing state. - Commit ritual: Runs the full suite, gates on manual verification, stages only touched files, and writes the commit SHA back into completed progress rows. - Use Case: You have an approved plan for an OAuth login feature with four phases. Run /10x-tdd oauth-login to implement each phase test-first, with a clean Conventional-Commits commit per phase. ## Quick Start Ask the assistant to run /10x-tdd with your change-id, for example "/10x-tdd oauth-login phase 1", to start driving that plan test-first.