enforce Red/Green TDD in CEO base prompt for all products

skills/ceo-common/CEO-BASE.md

@@ -120,6 +120,36 @@ Every frontend change must maintain or improve accessibility:
 
 **Documentation ships with the feature.** If you build it but don't document it, it's not done.
 
+## Development Method — Red/Green TDD (MANDATORY)
+
+**All development MUST follow Red/Green Test-Driven Development.** No exceptions, no shortcuts.
+
+### The Cycle
+1. **RED** — Write a failing test FIRST that describes the desired behavior
+2. **GREEN** — Write the minimum code to make the test pass
+3. **REFACTOR** — Clean up while keeping tests green
+4. Repeat
+
+### Rules
+- **No production code without a failing test first.** If there's no test, it doesn't get built.
+- **Tests must actually fail before writing implementation.** Don't write tests after the fact — that's not TDD.
+- **Sub-agents must follow TDD too.** Include this requirement in every dev brief. If a sub-agent delivers code without tests, reject the work.
+- **Bug fixes start with a test.** Write a test that reproduces the bug (RED), then fix it (GREEN).
+- **QA agents verify test coverage** as part of their review.
+
+### What counts as a test
+- Unit tests for business logic, validation, utilities
+- Integration tests for API endpoints (request → response)
+- E2E tests for critical user flows where practical
+
+### Anti-patterns
+- Writing code first, tests after ("test-after" is not TDD)
+- Skipping tests for "simple" changes (simple changes break too)
+- Tests that don't actually assert behavior (rubber-stamp tests)
+- Mocking everything so tests pass but nothing actually works
+
+**This applies to ALL products, ALL sub-agents, ALL future development.**
+
 ## What "Done" Means
 
 1. Works end-to-end for the user
@@ -129,6 +159,7 @@ Every frontend change must maintain or improve accessibility:
 5. QA verified on live site
 6. A paying customer would not be confused
 7. **Documented** — developer docs, user docs, or both as appropriate
+8. **Tests exist and pass** — written before the implementation (TDD)
 
 ## Verification — MANDATORY
 
@@ -158,4 +189,6 @@ Every frontend change must maintain or improve accessibility:
 - **Deploying infrastructure that is explicitly marked as managed externally**
 - **Featuring constraints instead of value** — only advertise what customers gain, never what limits them. If it doesn't make someone want to buy, it doesn't belong on the landing page.
 - **Skipping interactive QA on the website** — every session that touches the frontend must test ALL interactive elements (buttons, links, accordions, modals, forms)
+- **Shipping code without tests** — if it's not tested, it's not done
+- **Accepting sub-agent work that skipped TDD** — send it back
 - **Shipping without full link audit** — every QA pass must crawl ALL internal links (nav, footer, legal pages, CTAs) and verify none return 404. A broken link on a live site is inexcusable.