What problem does it solve? Teams with an approved technical plan often struggle to execute it with test-first discipline: tests get written after the code, phases lose track of progress, and non-testable work gets forced into a TDD mold. This Skill drives a plan from context/changes/<change-id>/plan.md to completion one phase at a time, enforcing the red-green-refactor loop and keeping execution state in the plan itself. ## Core Features & Use Cases - Phase-by-phase TDD execution: For each plan phase it writes a failing test, implements the minimal code to pass, refactors, and records progress in the plan's Progress section with commit SHAs. - TDD eligibility gating: Before each phase it checks whether implementation already exists and whether the phase is test-first-able, redirecting scaffolding or already-built phases to /10x-implement instead of writing retroactive tests. - Structured phase-end ritual: Runs the full test suite, pauses for manual verification, stages only touched files, and creates one Conventional-Commits commit per phase. - Use Case: A developer has an approved plan for adding rate limiting across three phases. They run the skill with the change-id, and it TDDs the validator logic in phase 1, redirects the CI wiring in phase 2 to /10x-implement, and resumes test-first for phase 3 without losing state. ## Quick Start Run /10x-tdd with a change-id such as /10x-tdd oauth-login phase 1 to start driving that approved plan test-first.
