Apply test-driven development
conducty-tddskillsetup L1★0
Sheshiyer/skill-clusters ↗What it does
Test-driven development at orchestrator (verification-first) and implementer (red-green-refactor) levels
Best for
Feature development where verification is continuous and acceptance criteria are unambiguous before coding starts.
Inputs
- · Feature acceptance criteria
- · Prompt for implementer
- · Test harness or example
Outputs
- · Test-passing code
- · Unit tests, acceptance tests
Requires
- · LLM/Claude API
- · Bash/CLI
- · HTTP/REST API
- · Database
- · Runtime (Python/Node)
Preconditions
- · Acceptance criteria written before code
- · Verification command defined
- · Test framework set up
Failure modes
- · Tests written after code (skips red phase)
- · Verification step is subjective (hard to gate)
- · Coverage drops if refactor omitted
Trust signals
- · Red→Green→Refactor cycle enforced
- · Orchestrator TDD (verification-first planning)