Does this skill allow mock implementations?

The skill includes a critical anti-mock directive; mocks are allowed only in test files. Operational code must contain real implementations or raise a NotImplementedError.

Why does this skill use Git worktrees?

Worktrees provide complete environment isolation for subtasks, preventing code contamination across features and allowing for safe, parallel development.

Can I run multiple implementation tasks at once?

Yes, the skill is specifically designed to manage parallel subagents working in separate worktrees, which can increase implementation speed by up to 8x.

How does the TDD Implementer handle the RED phase?

The skill requires writing comprehensive unit, integration, and E2E tests that must fail initially to prove they are valid before any implementation code is written.

What are the blocking coverage thresholds?

Implementation is only marked complete if it achieves at least 80% line coverage and 70% branch coverage, with 100% coverage on critical paths.

TDD Implementer

Name: TDD Implementer
Author: turbobeest

byturbobeest

Security & Testing

Automates the test-driven development cycle through isolated Git worktrees and strict code coverage enforcement.

About

The TDD Implementer skill streamlines the software implementation phase by enforcing a rigorous RED-GREEN-REFACTOR workflow within dedicated Git worktrees. Designed for high-integrity development, it mandates specific coverage thresholds (80% line and 70% branch) and prohibits mock implementations in production code to ensure operational readiness. By leveraging parallel subagent execution, it enables complex features to be built in isolated environments simultaneously, preventing merge conflicts and significantly accelerating the delivery pipeline from specification to integration.

Key Features

Strict RED-GREEN-REFACTOR cycle enforcement for all code changes
Isolated implementation using per-task Git worktrees to prevent contamination
Anti-mock directive ensuring production-grade operational logic over simulations
0 GitHub stars
Mandatory coverage gates requiring 80% line and 70% branch coverage
Parallel subagent support for high-speed, concurrent task development

Use Cases

Scaling development velocity via parallel implementation in isolated worktrees
Building complex software features from detailed OpenSpec proposals
Enforcing high test coverage standards in mission-critical codebases

About

Key Features

Strict RED-GREEN-REFACTOR cycle enforcement for all code changes
Isolated implementation using per-task Git worktrees to prevent contamination
Anti-mock directive ensuring production-grade operational logic over simulations
0 GitHub stars
Mandatory coverage gates requiring 80% line and 70% branch coverage
Parallel subagent support for high-speed, concurrent task development

Use Cases

Scaling development velocity via parallel implementation in isolated worktrees
Building complex software features from detailed OpenSpec proposals
Enforcing high test coverage standards in mission-critical codebases