tests-creatorlisted

# Tests Creator ## Purpose Converts acceptance criteria (from `issue-analyzer` or manual input) into concrete, failing test stubs **before any implementation code is written**. Enforces the RED phase of TDD. **Input:** Task object with `acceptance_criteria` + codebase path + test framework info **Output:** Ready-to-run test files with failing test stubs + `test_case_specs` block for `task-implementer` ## When to Use - Between `issue-analyzer` and `task-implementer` in the TDD pipeline - Orchestrator needs test specs before dispatching implementation - User wants to review test expectations before code is written - Acceptance criteria need to be translated into executable specifications ## Architecture: 4 Phases ``` Phase 1: DETECT → Identify test framework, conventions, fixture patterns Phase 2: ANALYZE → Map acceptance criteria to test scenarios Phase 3: GENERATE → Write failing test stubs with correct framework syntax Phase 4: REPORT → Emit test_case_specs for task-implementer consumption ``` --- ## Workflow ``` Tests Creator Progress: - [ ] Phase 1: Detect test framework and conventions - [ ] Phase 2: Map acceptance criteria to test scenarios - [ ] Phase 3: Generate failing test stubs - [ ] Phase 4: Report test_case_specs ``` --- ### Phase 1: DETECT Identify the test framework and conventions used in the project. **1.1 Detect framework:** ```bash # Check package.json for test dependencies cat <codebase_path>/package.json | grep -E '"(jest|vitest