10x-tdd

Executes approved implementation plans phase by phase through the red-green-refactor test-first cycle.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Oskarovsky/Sprinter --skill 10x-tdd-oskarovsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-tdd
Source: https://github.com/Oskarovsky/Sprinter/tree/main/.cursor/skills/10x-tdd
Command: npx skills add https://github.com/Oskarovsky/Sprinter --skill 10x-tdd-oskarovsky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams with an approved implementation plan often struggle to execute it with true test-first discipline: tests get written after the code, phases lose track of progress, and non-testable work (scaffolding, config, infra) gets forced into awkward TDD loops. This Skill drives a plan from context/changes/<change-id>/plan.md to completion one phase at a time, writing a failing test before any production code, while keeping execution state in the plan's canonical Progress section. ## Core Features & Use Cases - Red-Green-Refactor Loop per Phase: For each eligible phase, writes one failing test (RED), implements the minimal code to pass it (GREEN), then refactors while staying green, with a focused budget of 2-5 tests per phase. - TDD Eligibility Gate: Before each phase, checks whether implementation is absent and whether the phase is test-first-able; redirects non-TDD'able phases (scaffolding, CI, styling) to /10x-implement and stops when code already exists. - Shared Progress Tracking: Mutates the same ## Progress section as /10x-implement, flipping checkboxes and writing back commit SHAs at phase end, so both skills can interleave on one plan. - Phase-End Commit Ritual: Runs the full test suite, gates on manual verification, stages files explicitly by path, and proposes Conventional-Commits messages with SHA write-back. - Use Case: Given an approved plan for an OAuth login feature, run the skill to TDD the token-validation phase, hand the Docker config phase off to /10x-implement, and resume test-first on the next phase without losing state. ## Quick Start Ask the AI to drive the approved plan for your change test-first by running /10x-tdd with your change-id, for example "/10x-tdd oauth-login phase 1".

Frequently Asked Questions about 10x-tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a plan test-first with TDD?

Invoke the skill with a change-id or plan path, such as /10x-tdd oauth-login phase 1. It reads the plan, writes a failing test for each behavior, adds the minimal code to pass it, refactors, and commits once per phase after the full suite is green.

What happens when a phase is not suitable for TDD?

The skill runs an eligibility gate before every phase. Scaffolding, CI config, styling, and other non-testable phases are redirected to /10x-implement with a clipboard-copied resume command, or implemented inline without test-first if you choose.

Can I use TDD if the implementation code already exists?

No. The skill stops when it detects existing implementation for a phase, because a failing test can no longer lead the code. It suggests running /10x-implement for that phase instead of writing retroactive tests.

Does this skill set up test runners or CI configuration?

No. It assumes a test runner like Vitest, Jest, Playwright, or pytest is already configured and only discovers existing conventions. If no runner exists, it stops and points you to set one up first.

How is progress tracked across phases and sessions?

Progress lives in the plan.md ## Progress section as the single source of truth. Steps flip from unchecked to checked as they complete, and the phase's commit SHA is appended at phase end, so you can clear context and resume anytime.