tdd-workflowlisted

# Test-Driven Development Workflow The methodology of TDD: RED-GREEN-REFACTOR, which test to write when, and the coverage policy. Language-neutral by design — it does not carry framework mechanics. ## Relationship to language-specific testing skills This skill is the **methodology**. For framework-specific mechanics, pair it with the matching skill rather than duplicating their guidance here: | Need | Skill | | ------------------------------------------------------- | ---------------------- | | Vitest / Jest, mocking (`vi.mock`, MSW), async patterns | **typescript-testing** | | Table-driven tests, subtests, benchmarks, fuzzing | **golang-testing** | | E2E journeys, artifacts, flake quarantine | **e2e-runner** agent | If you are reaching for a mock, a matcher, or a test-runner flag, you want one of those — not this skill. The `/tdd`, `/go-test`, and `/test-coverage` commands drive this workflow. ## When to Activate - Writing new features or functionality - Fixing bugs or issues - Refactoring existing code ## Core Principles ### 1. Tests BEFORE Code ALWAYS write tests first, then implement code to make tests pass. A test written after the implementation tends to assert what the code _does_, not what it _should do_ — it locks in bugs instead of catching them. ### 2. Coverage Requirements **This section is the single source of truth for the coverage policy.** Other skills, a