tdd-claude-code 0.4.0 → 0.4.2

package/README.md

@@ -30,14 +30,12 @@ You use `/tdd:*` commands for everything. Never touch `/gsd:*` directly.
 /tdd:new-project          New project from scratch
        OR
 /tdd:init                 Add TDD to existing codebase
-/tdd:coverage             Analyze gaps, write retro tests (optional)
+/tdd:coverage             Write tests for existing code (optional)
     ↓
-/tdd:discuss 1            Shape how phase 1 gets built
-/tdd:plan 1               Create task plans
-/tdd:build 1              Write tests → implement → tests pass  ← TDD happens here
-/tdd:verify 1             Human acceptance testing
-    ↓
-...repeat for each phase...
+/tdd:discuss              Shape how it gets built
+/tdd:plan                 Create task plans
+/tdd:build                Write tests → implement → tests pass  ← TDD happens here
+/tdd:verify               Human acceptance testing
     ↓
 /tdd:complete             Tag release
 ```
@@ -60,11 +58,11 @@ You run one command. Tests get written before code. Automatically.
 | `/tdd:new-project` | Start project with test infrastructure |
 | `/tdd:init` | Add TDD to existing codebase |
 | `/tdd:coverage` | Analyze gaps, write tests for existing code |
-| `/tdd:discuss [N]` | Capture implementation preferences |
-| `/tdd:plan [N]` | Create task plans |
-| `/tdd:build <N>` | **Write tests → implement → verify** |
-| `/tdd:verify [N]` | Human acceptance testing |
-| `/tdd:status [N]` | Check test pass/fail |
+| `/tdd:discuss` | Capture implementation preferences |
+| `/tdd:plan` | Create task plans |
+| `/tdd:build` | **Write tests → implement → verify** |
+| `/tdd:verify` | Human acceptance testing |
+| `/tdd:status` | Check test pass/fail |
 | `/tdd:progress` | Where am I? |
 | `/tdd:quick` | Ad-hoc task with tests |
 | `/tdd:complete` | Tag release |

package/bin/install.js

@@ -26,7 +26,7 @@ ${c.cyan}  ████████╗██████╗ ██████
      ╚═╝   ╚═════╝ ╚═════╝${c.reset}
 `;
 
-const VERSION = '0.4.0';
+const VERSION = '0.4.2';
 
 const COMMANDS = [
   'new-project.md',

package/build.md

@@ -14,9 +14,11 @@ This is the core TDD command. Tests before code, automatically.
 ## Usage
 
 ```
-/tdd:build <phase_number>
+/tdd:build [phase_number]
 ```
 
+Phase number is optional. Defaults to 1.
+
 ## Process
 
 ### Step 1: Load Plans
@@ -32,61 +34,60 @@ Check what's already set up:
 - `spec/` directory → RSpec
 - None found → Set up based on PROJECT.md stack (see framework defaults below)
 
-### Step 3: Write Tests (Spawn Test Writer Agents)
+### Step 3: Plan Tests for Each Task
 
-For each plan, spawn an agent with this prompt:
+Before writing any tests, create a test plan for each task in the phase.
 
-<agent_prompt>
-You are a TDD Test Writer. Write failing tests that define expected behavior BEFORE implementation.
+For each task in the plan:
 
-## Context
+1. **Read the task** — understand what behavior is being specified
+2. **Identify test cases:**
+   - Happy path (expected inputs → expected outputs)
+   - Edge cases mentioned in `<action>`
+   - Error conditions from `<verify>`
+3. **Create test plan entry**
 
-<project>
-{PROJECT.md contents}
-</project>
+Create `.planning/phases/{phase}-TEST-PLAN.md`:
 
-<plan>
-{Current PLAN.md contents}
-</plan>
+```markdown
+# Phase {N} Test Plan
 
-<test_framework>
-{Detected or default framework}
-</test_framework>
+## Task: {task-id} - {task-title}
 
-<existing_tests>
-{List any existing test files for patterns, or "None - this is a new project"}
-</existing_tests>
+### File: tests/{feature}.test.ts
 
-## Your Task
+| Test | Type | Expected Result |
+|------|------|-----------------|
+| user can log in with valid credentials | happy path | returns user object |
+| login rejects invalid password | error | throws AuthError |
+| login rejects empty email | edge case | throws ValidationError |
 
-For each `<task>` in the plan:
+### Dependencies to mock:
+- database connection
+- email service
 
-1. **Understand the task** — What behavior is being specified?
+---
 
-2. **Write test file(s)** that cover:
-   - Happy path (expected inputs → expected outputs)
-   - Edge cases mentioned in `<action>`
-   - Error conditions from `<verify>`
-   
-3. **Make tests runnable NOW** — even though implementation doesn't exist:
-   - Import from where the code WILL be (path in `<files>`)
-   - Tests should FAIL, not ERROR from missing imports
-   - Use mocks/stubs where needed for dependencies
-
-4. **Use clear test names** that describe expected behavior:
-   ```
-   ✓ "user can log in with valid credentials"
-   ✓ "login rejects invalid password with 401"
-   ✓ "login returns httpOnly cookie on success"
-   ✗ "test login" (too vague)
-   ```
-
-## Test File Patterns
+## Task: {task-id-2} - {task-title-2}
+...
+```
+
+### Step 4: Write Tests One Task at a Time
+
+**For each task in the test plan, sequentially:**
+
+#### 4a. Write test file for this task
+
+Follow the project's test patterns. Test names should describe expected behavior:
+```
+✓ "user can log in with valid credentials"
+✓ "login rejects invalid password with 401"
+✗ "test login" (too vague)
+```
 
 **Vitest/Jest (TypeScript):**
 ```typescript
 import { describe, it, expect } from 'vitest'
-// Import from where code WILL exist
 import { login } from '../src/auth/login'
 
 describe('login', () => {
@@ -106,7 +107,6 @@ describe('login', () => {
 **pytest (Python):**
 ```python
 import pytest
-# Import from where code WILL exist
 from src.auth import login
 
 def test_login_returns_user_for_valid_credentials():
@@ -118,28 +118,40 @@ def test_login_raises_for_invalid_password():
         login("user@test.com", "wrong")
 ```
 
-## Output
+#### 4b. Run this test file
 
-Create test files following the project's structure. Common locations:
-- `tests/{feature}.test.ts`
-- `src/{feature}/__tests__/{feature}.test.ts`
-- `tests/test_{feature}.py`
-- `spec/{feature}_spec.rb`
+```bash
+npm test -- tests/auth/login.test.ts   # vitest
+pytest tests/test_login.py              # pytest
+```
+
+Verify:
+- ✅ Tests execute (no syntax errors)
+- ✅ Tests FAIL (not pass, not skip)
+- ❌ If import errors, add mocks/stubs and retry
+
+#### 4c. Commit this test file
+
+```bash
+git add tests/auth/login.test.ts
+git commit -m "test: add login tests (red) - phase {N}"
+```
 
-After creating each test file, run it and confirm it FAILS (not errors).
+#### 4d. Move to next task
 
-## Critical Rules
+Repeat 4a-4c for each task in the test plan.
 
+**Critical Rules:**
 - Tests must be **syntactically valid** and **runnable**
 - Tests must **FAIL** because code doesn't exist yet
 - Tests must NOT **ERROR** from import issues — mock if needed
 - Do NOT write any implementation code
 - Do NOT skip or stub out the actual assertions
-</agent_prompt>
+- **One task at a time, verify, commit, then next**
 
-### Step 4: Verify All Tests Fail (Red)
+### Step 5: Verify All Tests Fail (Red)
 
-Run the test suite:
+Run the full test suite:
 ```bash
 npm test          # or vitest run, pytest, etc.
 ```
@@ -150,7 +162,7 @@ Check output:
 - ❌ If tests error on imports, add mocks and retry
 - ❌ If tests pass, something's wrong — investigate
 
-### Step 5: Create Test Summary
+### Step 6: Create Test Summary
 
 Create `.planning/phases/{phase}-TESTS.md`:
 
@@ -180,13 +192,13 @@ Status: ✅ All tests failing (Red)
 | session persists across requests | 01-task-2 |
 ```
 
-### Step 6: Execute Implementation (Green)
+### Step 7: Execute Implementation (Green)
 
 Call `/gsd:execute-phase {phase_number}`
 
 GSD's executor implements the code. Tests provide concrete pass/fail targets.
 
-### Step 7: Verify All Tests Pass (Green)
+### Step 8: Verify All Tests Pass (Green)
 
 After execution completes, run tests again:
 ```bash
@@ -197,7 +209,7 @@ Check output:
 - ✅ All tests PASS → Continue to verify
 - ❌ Some tests fail → Report which tasks need fixes
 
-### Step 8: Update Test Summary
+### Step 9: Update Test Summary
 
 Update `.planning/phases/{phase}-TESTS.md`:
 

package/coverage.md

@@ -125,12 +125,79 @@ Start writing tests now?
 
 **If "Yes":**
 
-For each file, write tests that capture current behavior:
-1. Read the source file
-2. Identify exported functions/classes
-3. Write tests for each public interface
-4. Run tests to verify they pass (code already exists)
-5. Mark item complete in backlog
+Write tests using GSD-style execution — one file at a time with verification and commits.
+
+#### For each file in the backlog (sequentially):
+
+**a) Plan tests for this file**
+
+Read the source file and create test plan:
+```markdown
+## File: src/services/payment.ts
+
+### Exports:
+- createCharge(amount, customerId)
+- refundCharge(chargeId)
+- getPaymentHistory(customerId)
+
+### Test cases:
+| Function | Test | Type |
+|----------|------|------|
+| createCharge | creates charge for valid customer | happy path |
+| createCharge | rejects negative amount | edge case |
+| createCharge | handles Stripe API error | error |
+| refundCharge | refunds existing charge | happy path |
+| refundCharge | fails for invalid chargeId | error |
+```
+
+**b) Write test file**
+
+Create tests that capture current behavior:
+```typescript
+import { describe, it, expect } from 'vitest'
+import { createCharge, refundCharge } from '../src/services/payment'
+
+describe('createCharge', () => {
+  it('creates charge for valid customer', async () => {
+    const result = await createCharge(1000, 'cust_123')
+    expect(result.id).toBeDefined()
+    expect(result.amount).toBe(1000)
+  })
+
+  it('rejects negative amount', async () => {
+    await expect(createCharge(-100, 'cust_123'))
+      .rejects.toThrow()
+  })
+})
+```
+
+**c) Run tests for this file**
+
+```bash
+npm test -- tests/services/payment.test.ts
+```
+
+Verify:
+- ✅ Tests PASS (code already exists)
+- ❌ If tests fail, investigate — either test is wrong or found a bug
+
+**d) Commit this test file**
+
+```bash
+git add tests/services/payment.test.ts
+git commit -m "test: add payment service tests"
+```
+
+**e) Update backlog**
+
+Mark item complete in `.planning/TEST-BACKLOG.md`:
+```markdown
+- [x] src/services/payment.ts - payment processing logic ✅
+```
+
+**f) Move to next file**
+
+Repeat a-e for each file in the backlog.
 
 ### 7. Report Summary
 

package/help.md

@@ -16,10 +16,12 @@ TDD-first workflow powered by GSD. You use `/tdd:*` for everything — tests hap
 
 | Command | What It Does |
 |---------|--------------|
-| `/tdd:discuss [N]` | Capture implementation preferences for phase N |
-| `/tdd:plan [N]` | Research and create task plans for phase N |
-| `/tdd:build <N>` | **Write tests → implement → verify tests pass** |
-| `/tdd:verify [N]` | Human acceptance testing |
+| `/tdd:discuss` | Capture implementation preferences |
+| `/tdd:plan` | Research and create task plans |
+| `/tdd:build` | **Write tests → implement → verify tests pass** |
+| `/tdd:verify` | Human acceptance testing |
+
+Phase number optional. Defaults to 1.
 
 ### Navigation
 
@@ -48,20 +50,14 @@ TDD-first workflow powered by GSD. You use `/tdd:*` for everything — tests hap
 /tdd:new-project          New project from scratch
        OR
 /tdd:init                 Existing codebase
-/tdd:coverage             Analyze gaps, write retro tests (optional)
-    ↓
-/tdd:discuss 1            Shape how phase 1 gets built
-/tdd:plan 1               Create task plans
-/tdd:build 1              Write tests → implement → tests pass
-/tdd:verify 1             Human acceptance testing
+/tdd:coverage             Write tests for existing code (optional)
     ↓
-/tdd:discuss 2            Repeat for each phase...
-/tdd:plan 2
-/tdd:build 2
-/tdd:verify 2
+/tdd:discuss              Shape how it gets built
+/tdd:plan                 Create task plans
+/tdd:build                Write tests → implement → tests pass
+/tdd:verify               Human acceptance testing
     ↓
 /tdd:complete             Tag release
-/tdd:new-milestone        Start v2
 ```
 
 ## What Happens in `/tdd:build`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tdd-claude-code",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "description": "TDD workflow for Claude Code - wraps GSD",
   "bin": {
     "tdd-claude-code": "./bin/install.js"