emperor-tdd
Emperor Time TDD iron law. Use BEFORE writing or editing production code for a feature, bugfix, refactor, or behavior change. No production code without a failing probe first. Delete implementation wr
SKILL.mdskills/emperor-tdd/SKILL.md
GitHubTDD Iron Law (Emperor Time)
NO PRODUCTION CODE WITHOUT A FAILING PROBE FIRST.
This is Vow of Evidence applied to code. Superpowers names the same law. Emperor Time is stricter on one point: the prediction is written in the claim ledger before the command runs, and the fail/pass tails are quoted.
MUST — red-green-refactor checklist first
Before any production code for a G1 criterion, open
skills/emperor-tdd/red-green-refactor.md
(Chain Jail leaf from Superpowers test-driven-development → The Iron Law
/ Red-Green-Refactor only)
and/or run scripts/emperor tdd (prints the mechanical TDD / STEP / MUST card).
No jumping to production code without Step 2 FAIL observed and quoted.
Do not load whole test-driven-development; ET + emperor-tdd orchestrate.
MUST — writing-good-tests when authoring or changing tests
When writing or changing a test (mocks, helpers, expectations, cleanup), open
skills/emperor-tdd/writing-good-tests.md
(Chain Jail leaf from Superpowers test-driven-development → Name the Break /
Exercise the Real Thing / Gate Function / Mutation Check only)
and/or run scripts/emperor good-tests (prints the mechanical GOOD / PRIN /
GATE / MUST card).
No mirror assertions. No change detectors. No mock-existence checks.
Do not load whole test-driven-development; ET + emperor-tdd orchestrate.
Hard rules
- Run
scripts/emperor tdd→ quoteTDD checklist=yes. Advance steps withscripts/emperor tdd --advance N N+1(skips fail). Jumping to prod →scripts/emperor tdd --reject-prod(HARD-GATE exit 1). 1b. When writing/changing tests: runscripts/emperor good-tests→ quoteGOOD checklist=yes. Mirror →scripts/emperor good-tests --reject-mirror(HARD-GATE exit 1). Change-detector →--reject-change-detector. - Write the probe (test or command) that must fail if the change is absent.
- Ledger a HYPOTHESIS row with the predicted signal.
- Run it. Watch it FAIL. Quote the tail. If it passes, the probe is wrong — fix the probe, not the product.
- Smallest change that makes that probe pass. Nothing else.
- Run it. Watch it PASS. Quote the tail. Then run the project suite.
- Refactor only while the probe stays green.
- If you already wrote implementation first: delete it. Delete means delete. Replay steps 2–7. Keeping it "as reference" is a vow breach.
Trivial doc/typo tasks: the probe may be grep / render, not a unit test.
The law still holds: observe absence, then change, then observe presence.
Work-order Tasks already encode this as Expected: FAIL then Expected: PASS. Follow that file. Do not invent a second sequence.