tdd-claude-code 0.2.0 → 0.3.0

package/README.md

@@ -27,7 +27,9 @@ npx tdd-claude-code --local    # this project only
 You use `/tdd:*` commands for everything. Never touch `/gsd:*` directly.
 
 ```
-/tdd:new-project          Describe your idea, get test infrastructure
+/tdd:new-project          New project from scratch
+       OR
+/tdd:init                 Add TDD to existing codebase
     ↓
 /tdd:discuss 1            Shape how phase 1 gets built
 /tdd:plan 1               Create task plans
@@ -55,6 +57,7 @@ You run one command. Tests get written before code. Automatically.
 | Command | What It Does |
 |---------|--------------|
 | `/tdd:new-project` | Start project with test infrastructure |
+| `/tdd:init` | Add TDD to existing codebase |
 | `/tdd:discuss [N]` | Capture implementation preferences |
 | `/tdd:plan [N]` | Create task plans |
 | `/tdd:build <N>` | **Write tests → implement → verify** |

package/bin/install.js

@@ -26,10 +26,11 @@ ${c.cyan}  ████████╗██████╗ ██████
      ╚═╝   ╚═════╝ ╚═════╝${c.reset}
 `;
 
-const VERSION = '0.2.0';
+const VERSION = '0.3.0';
 
 const COMMANDS = [
   'new-project.md',
+  'init.md',
   'discuss.md',
   'plan.md',
   'build.md',

package/help.md

@@ -4,11 +4,17 @@ TDD-first workflow powered by GSD. You use `/tdd:*` for everything — tests hap
 
 ## Commands
 
-### Core Workflow
+### Getting Started
 
 | Command | What It Does |
 |---------|--------------|
 | `/tdd:new-project` | Start new project with test infrastructure |
+| `/tdd:init` | Add TDD to existing codebase |
+
+### Core Workflow
+
+| 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** |
@@ -38,7 +44,9 @@ TDD-first workflow powered by GSD. You use `/tdd:*` for everything — tests hap
 ## Workflow
 
 ```
-/tdd:new-project          Describe your idea, set up project + tests
+/tdd:new-project          New project from scratch
+       OR
+/tdd:init                 Existing codebase
     ↓
 /tdd:discuss 1            Shape how phase 1 gets built
 /tdd:plan 1               Create task plans
@@ -81,6 +89,7 @@ TDD commands call GSD internally:
 | TDD Command | Calls |
 |-------------|-------|
 | `/tdd:new-project` | `/gsd:new-project` + test setup |
+| `/tdd:init` | scan + test setup (no GSD call) |
 | `/tdd:discuss` | `/gsd:discuss-phase` |
 | `/tdd:plan` | `/gsd:plan-phase` |
 | `/tdd:build` | write tests + `/gsd:execute-phase` |

package/init.md

@@ -0,0 +1,147 @@
+# /tdd:init - Initialize TDD in Existing Project
+
+Add TDD workflow to an existing codebase.
+
+## When to Use
+
+- You have existing code without tests
+- You have existing code with some tests
+- You're joining a project mid-development
+- You want to adopt TDD on a "vibe coded" project
+
+For brand new projects with no code, use `/tdd:new-project` instead.
+
+## Process
+
+### 1. Scan for Existing Code
+
+Check for source files:
+- `src/`, `lib/`, `app/`, `pkg/`, or root-level code files
+- `package.json`, `pyproject.toml`, `go.mod`, `Gemfile`, `Cargo.toml`
+
+If no code found, suggest running `/tdd:new-project` instead.
+
+### 2. Detect Stack
+
+| Indicator | Stack |
+|-----------|-------|
+| `package.json` + React/Next deps | Next.js / React |
+| `package.json` (no framework) | Node.js |
+| `pyproject.toml` / `requirements.txt` | Python |
+| `go.mod` | Go |
+| `Gemfile` | Ruby |
+| `Cargo.toml` | Rust |
+
+### 3. Scan for Existing Tests
+
+Look for test indicators:
+
+**Directories:**
+- `tests/`, `test/`, `__tests__/`, `spec/`
+
+**Files:**
+- `*_test.py`, `test_*.py`
+- `*.test.ts`, `*.test.js`, `*.spec.ts`, `*.spec.js`
+- `*_test.go`
+- `*_spec.rb`
+
+**Config files:**
+- `vitest.config.*`, `jest.config.*`, `pytest.ini`, `pyproject.toml` [tool.pytest]
+- `.rspec`, `spec/spec_helper.rb`
+
+### 4. Set Up Test Framework (if missing)
+
+If no tests found, set up based on detected stack:
+
+| Stack | Framework | Setup |
+|-------|-----------|-------|
+| Next.js / React | Vitest | `npm install -D vitest @testing-library/react` |
+| Node.js | Vitest | `npm install -D vitest` |
+| Python | pytest | `pip install pytest` or add to pyproject.toml |
+| Go | go test | Built-in, no setup needed |
+| Ruby | RSpec | `gem install rspec && rspec --init` |
+| Rust | cargo test | Built-in, no setup needed |
+
+Create config file and test directory structure.
+
+Add test scripts to package.json / pyproject.toml / Makefile:
+```json
+"scripts": {
+  "test": "vitest run",
+  "test:watch": "vitest"
+}
+```
+
+### 5. If Tests Already Exist
+
+- Skip framework setup
+- Note existing test patterns for consistency
+- Report: "Found existing test framework: [vitest/jest/pytest/etc]"
+- Report: "Found X existing test files"
+
+### 6. Analyze Existing Code Structure
+
+Scan the codebase and generate summary:
+- Main directories and their purpose
+- Key modules/components identified
+- Entry points (main files, API routes, etc.)
+- Dependencies and their roles
+
+### 7. Create or Update PROJECT.md
+
+If PROJECT.md doesn't exist, create it with:
+
+```markdown
+# [Project Name]
+
+## Overview
+[Inferred from code structure and README if present]
+
+## Tech Stack
+- [Detected stack]
+- [Key dependencies]
+
+## Project Structure
+[Generated from scan]
+
+## Development Methodology: Test-Led Development
+
+This project uses TDD. All new implementation follows Red -> Green -> Refactor:
+
+1. **Red**: Write failing tests that define expected behavior
+2. **Green**: Write minimum code to make tests pass
+3. **Refactor**: Clean up while keeping tests green
+
+Tests are written BEFORE implementation, not after.
+
+## Test Framework
+- Framework: [detected or installed]
+- Run tests: `[test command]`
+- Test directory: `[path]`
+```
+
+If PROJECT.md exists, append the TDD section only.
+
+### 8. Report Summary
+
+```
+TDD initialized for [project name]
+
+Stack: [detected]
+Test framework: [framework] (existing/newly configured)
+Test directory: [path]
+Existing tests: [count] files
+
+Next steps:
+- Run /tdd:status to check current test coverage
+- Run /tdd:discuss to plan new features with TDD
+- Run /tdd:quick for ad-hoc tasks with tests
+```
+
+## Usage
+
+```
+/tdd:init
+```
+
+No arguments needed. Auto-detects everything.

package/package.json

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