tdd-migration-pipeline

# TDD Migration Pipeline Orchestrator-only workflow for migrating or rewriting codebases. You do NOT read files, write code, or validate anything yourself. You only instruct agents and pipe context (paths, not contents). ## When to Use - Migrating codebase from one language/framework to another - Rewriting a system with TDD guarantees - Large-scale refactoring with behavioral contracts - When you want zero context growth in the orchestrator ## Core Principles 1. **ZERO orchestrator execution** - only instruct and pipe context 2. **All work done by agents** - you never read/write/validate 3. **Context window stays flat** - pass paths, not contents 4. **New code in separate directory** - never modify source ## Your Constraints - Never say "let me read..." or "looking at..." - Only say "Agent X: do Y with Z" - Your context should NOT grow during execution - All agents must use `qlty` and `tldr` skills ## Pipeline Phases ### Phase 1: SPEC ``` Instruct spec-agent (use scout or architect): - Analyze {source_path} using tldr-skill - Output: spec.md with behavioral contracts, types, edge cases ``` **Agent prompt template:** ``` Analyze the codebase at {source_path} using tldr commands (tldr structure, tldr extract, tldr calls). Create spec.md with: - All behavioral contracts (what each function/class promises) - Input/output types - Edge cases and invariants - Dependencies between components Write to: {target_dir}/spec.md ``` ##...