Menu
TDD: enforce RED-GREEN-REFACTOR in coding engine dispatches.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Branch, commit, push, and open PRs with humanized messages, then monitor GitHub Actions CI. Per-project autonomy gating; blocks direct pushes to the default branch and pushes with a dirty tree. Never auto-merges.
Dispatch patterns for Claude Code as the coding engine. Default harness. Implementation dispatches go through dispatch_coder.py (writes the dispatch receipt the commit gate requires).
Testing strategy, TDD enforcement, spec compliance, and regression checks.
Write implementation plans: bite-sized tasks for coding engine dispatch.
Automated fix loop for failed Quality/Reviewer checks. Parses failures, builds escalating prompts, dispatches through the active harness up to 3 times.
Run independent, file-disjoint plan tasks concurrently, each isolated in its own git worktree + branch. Collects per-task results; never auto-merges.
| name | test-driven-development |
| description | TDD: enforce RED-GREEN-REFACTOR in coding engine dispatches. |
| version | 2.0.0 |
| author | Hermes Coder (adapted from obra/superpowers) |
| license | MIT |
| platforms | ["linux","macos","windows"] |
| metadata | {"hermes":{"tags":["testing","tdd","development","quality","red-green-refactor"],"related_skills":["writing-plans","subagent-driven-development","requesting-code-review"]}} |
Write the test first. Watch it fail. Write minimal code to pass.
Core principle: If you didn't watch the test fail, you don't know if it tests the right thing.
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
Every coding engine dispatch that produces code MUST include TDD instructions.
Write one minimal test showing what should happen. Clear name, tests real behavior, one thing.
MANDATORY. Never skip. Run the test, confirm it fails because the feature is missing.
Write the simplest code to pass the test. Nothing more.
Run the specific test (pass), then run ALL tests (no regressions).
After green: remove duplication, improve names, extract helpers. Keep tests green.
Next failing test for next behavior.
Every implementation prompt to the coding engine must include TDD instructions. Consult the active harness skill (under skills/harness/) for the exact dispatch syntax. The TDD prompt template:
<feature> using strict TDD:
<test-file><test-command><full-test-command>git add <files> && git commit -m '<message>'"After the coding engine completes, verify TDD was followed:
If the coding engine skipped TDD (wrote code before tests), re-dispatch with explicit TDD enforcement.
| Excuse | Reality |
|---|---|
| "Too simple to test" | Simple code breaks. Test takes 30 seconds. |
| "I'll test after" | Tests passing immediately prove nothing. |
| "Need to explore first" | Fine. Throw away exploration, start with TDD. |
| "Test hard = complex" | Hard to test = hard to use. Simplify the design. |
Test first, always
Watch it fail
Minimal code to pass
Run all tests
No exceptions without user approval