catlog22/Claude-Code-Workflow
1
0
Fork 0
mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-11 02:33:51 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat: Redesign test-gen workflow with independent session and cross-session context

Browse Source 
Major redesign of test-gen workflow based on simplified architecture:

Core Changes:
- Creates independent test session (WFS-test-[source]) instead of modifying existing session
- Implements 4-phase execution with concept-enhanced analysis integration
- Reuses IMPL-*.json format with meta.type="test-fix" (no new task type)
- Auto-detects cross-session context via workflow-session.json metadata

4-Phase Workflow:
1. Phase 1: Create test session with workflow_type and source_session_id metadata
2. Phase 2: Auto-detect and gather cross-session context (summaries, git changes, tests)
3. Phase 3: Analyze implementation with concept-enhanced (parallel Gemini + Codex)
4. Phase 4: Generate IMPL-001.json task with test strategy from ANALYSIS_RESULTS.md

Key Features:
- Session isolation: Test session separate from implementation session
- Parameter simplification: context-gather auto-detects via metadata (no --source-session param)
- Format reuse: IMPL-*.json with meta.type field (zero changes to execute/status tools)
- Analysis integration: concept-enhanced provides comprehensive test strategy and code targets
- Automatic cross-session: Collects source session artifacts automatically

Tool Modifications Required:
- session-start: Support test session metadata (workflow_type, source_session_id)
- context-gather: Auto-detect test session and gather from source session
- task-generate: Extract test strategy from ANALYSIS_RESULTS.md
- concept-enhanced: No changes (already supports analysis)
- execute: No changes (already dispatches by meta.agent)

Data Flow:
User → session-start (creates test session) → context-gather (auto cross-session)
→ concept-enhanced (analyzes + generates strategy) → task-generate (creates task)
→ Returns summary → User triggers /workflow:execute separately

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-10-03 12:04:00 +08:00
parent ae77e698db
commit 2efd45b0ed
1 changed files with 280 additions and 158 deletions
Download Patch File Download Diff File Expand all files Collapse all files

438
.claude/commands/workflow/test-gen.md
View File

@@ -1,11 +1,11 @@
--- ---
name: test-gen name: test-gen
description: Orchestrate test-fix workflow by analyzing implementation and generating TEST-FIX tasks description: Create independent test-fix workflow session by analyzing completed implementation
usage: /workflow:test-gen [session-id] usage: /workflow:test-gen <source-session-id>
argument-hint: "[session-id]" argument-hint: "<source-session-id>"
examples: examples:
- /workflow:test-gen
- /workflow:test-gen WFS-user-auth - /workflow:test-gen WFS-user-auth
- /workflow:test-gen WFS-api-refactor
allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*) allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
--- ---
@@ -13,134 +13,177 @@ allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
## Coordinator Role ## Coordinator Role
**This command is a pure orchestrator**: Analyze completed implementation session, generate test-fix workflow through standardized tool commands, and trigger automated test validation. **This command is a pure orchestrator**: Creates an independent test-fix workflow session for validating a completed implementation. It reuses the standard planning toolchain with automatic cross-session context gathering.
**Core Principles**:
- **Session Isolation**: Creates new `WFS-test-[source]` session to keep verification separate from implementation
- **Context-First**: Prioritizes gathering code changes and summaries from source session
- **Format Reuse**: Creates standard `IMPL-*.json` task, using `meta.type: "test-fix"` for agent assignment
- **Parameter Simplification**: Tools auto-detect test session type via metadata, no manual cross-session parameters needed
**Execution Flow**: **Execution Flow**:
1. Initialize TodoWrite → Execute Phase 1 → Parse output → Update TodoWrite 1. Initialize TodoWrite → Create test session → Parse session ID
2. Execute Phase 2 with Phase 1 data → Parse output → Update TodoWrite 2. Gather cross-session context (automatic) → Parse context path
3. Execute Phase 3 with Phase 2 data → Parse output → Update TodoWrite 3. Analyze implementation with concept-enhanced → Parse ANALYSIS_RESULTS.md
4. Execute Phase 4 with Phase 3 validation → Update TodoWrite → Return summary 4. Generate test task from analysis → Return summary
## Core Rules ## Core Rules
1. **Start Immediately**: First action is TodoWrite initialization, second action is Phase 1 session discovery 1. **Start Immediately**: First action is TodoWrite initialization, second action is Phase 1 test session creation
2. **No Preliminary Analysis**: Do not read files or analyze before Phase 1 2. **No Preliminary Analysis**: Do not read files or analyze before Phase 1
3. **Parse Every Output**: Extract required data from each phase for next phase 3. **Parse Every Output**: Extract required data from each phase for next phase
4. **Sequential Execution**: Each phase depends on previous phase's output 4. **Sequential Execution**: Each phase depends on previous phase's output
5. **Complete All Phases**: Do not return to user until Phase 4 completes 5. **Complete All Phases**: Do not return to user until Phase 4 completes (execution triggered separately)
6. **Track Progress**: Update TodoWrite after every phase completion 6. **Track Progress**: Update TodoWrite after every phase completion
7. **Use Standard Tools**: Follow plan.md pattern using context-gather, concept-enhanced, task-generate 7. **Automatic Detection**: context-gather auto-detects test session and gathers source session context
## 4-Phase Execution ## 4-Phase Execution
### Phase 1: Session Discovery & Context Gathering ### Phase 1: Create Test Session
**Command**: `SlashCommand(command="/workflow:tools:context-gather --session [sessionId] \"TEST-FIX: Validate implementation for [sessionId]\"")` **Command**: `SlashCommand(command="/workflow:session:start --new \"Test validation for [sourceSessionId]\"")`
**Session ID Resolution**: **Input**: `sourceSessionId` from user argument (e.g., `WFS-user-auth`)
- If argument provided → Use directly as `sessionId`
- If no argument → Auto-detect from `.workflow/.active-*` marker
- Format: `WFS-[session-name]`
**Task Description Structure**: **Expected Behavior**:
``` - Creates new session with pattern `WFS-test-[source-slug]` (e.g., `WFS-test-user-auth`)
GOAL: Execute and validate all tests for completed implementation - Writes metadata to `workflow-session.json`:
SCOPE: Test execution, failure diagnosis, code fixing - `workflow_type: "test_session"`
CONTEXT: Implementation session [sessionId] with completed IMPL tasks - `source_session_id: "[sourceSessionId]"`
``` - Returns new session ID for subsequent phases
**Parse Output**: **Parse Output**:
- Extract: context package path (store as `contextPath`) - Extract: new test session ID (store as `testSessionId`)
- Typical pattern: `.workflow/[sessionId]/.process/context-package-test.json` - Pattern: `WFS-test-[slug]`
**Validation**: **Validation**:
- Session directory `.workflow/[sessionId]/` exists - Source session `.workflow/[sourceSessionId]/` exists
- Session has completed IMPL tasks (check .summaries/IMPL-*-summary.md) - Source session has completed IMPL tasks (`.summaries/IMPL-*-summary.md`)
- Context package created successfully - New test session directory created
- Metadata includes `workflow_type` and `source_session_id`
**TodoWrite**: Mark phase 1 completed, phase 2 in_progress **TodoWrite**: Mark phase 1 completed, phase 2 in_progress
--- ---
### Phase 2: Implementation Analysis ### Phase 2: Gather Cross-Session Context
**Command**: `SlashCommand(command="/workflow:tools:concept-enhanced --session [sessionId] --context [contextPath]")` **Command**: `SlashCommand(command="/workflow:tools:context-gather --session [testSessionId]")`
**Input**: `sessionId` from Phase 1, `contextPath` from Phase 1 **Input**: `testSessionId` from Phase 1 (e.g., `WFS-test-user-auth`)
**Expected Analysis**: **Automatic Detection**:
- Review completed implementation summaries - context-gather reads `.workflow/[testSessionId]/workflow-session.json`
- Identify test files and coverage gaps - Detects `workflow_type: "test_session"`
- Assess test execution strategy - Automatically uses `source_session_id` to gather source session context
- Determine failure diagnosis approach - No need for manual `--source-session` parameter
**Cross-Session Context Collection** (Automatic):
- Implementation summaries: `.workflow/[sourceSessionId]/.summaries/IMPL-*-summary.md`
- Code changes: `git log --since=[source_session_created_at]` for changed files
- Original plan: `.workflow/[sourceSessionId]/IMPL_PLAN.md`
- Test files: Discovered via MCP code-index tools
**Parse Output**: **Parse Output**:
- Verify `.workflow/[sessionId]/.process/ANALYSIS_RESULTS.md` created - Extract: context package path (store as `contextPath`)
- Extract test execution recommendations - Pattern: `.workflow/[testSessionId]/.process/context-package.json`
- Identify critical test areas
**Validation**: **Validation**:
- File `.workflow/[sessionId]/.process/ANALYSIS_RESULTS.md` exists - Context package created in test session directory
- Contains test strategy and execution plan - Contains source session artifacts (summaries, changed files)
- Lists focus test paths and acceptance criteria - Includes test file inventory
**TodoWrite**: Mark phase 2 completed, phase 3 in_progress **TodoWrite**: Mark phase 2 completed, phase 3 in_progress
--- ---
### Phase 3: TEST-FIX Task Generation ### Phase 3: Implementation Analysis
**Command**: `SlashCommand(command="/workflow:tools:task-generate --session [sessionId]")` **Command**: `SlashCommand(command="/workflow:tools:concept-enhanced --session [testSessionId] --context [contextPath]")`
**Input**: `sessionId` from Phase 1 **Input**:
- `testSessionId` from Phase 1 (e.g., `WFS-test-user-auth`)
- `contextPath` from Phase 2 (e.g., `.workflow/WFS-test-user-auth/.process/context-package.json`)
**Analysis Focus**:
- Review implementation summaries from source session
- Identify test files and coverage gaps
- Assess test execution strategy (unit, integration, e2e)
- Determine failure diagnosis approach
- Recommend code quality improvements
**Expected Behavior**: **Expected Behavior**:
- Parse ANALYSIS_RESULTS.md for test requirements - Reads context-package.json with cross-session artifacts
- Generate TEST-FIX-001.json with: - Executes parallel analysis (Gemini for test strategy, optional Codex for validation)
- `meta.type: "test-fix"` - Generates comprehensive test execution strategy
- `meta.agent: "@test-fix-agent"` - Identifies code modification targets for test fixes
- `context.requirements`: Test execution requirements - Provides feasibility assessment for test validation
- `context.focus_paths`: Test files and source files
- `context.acceptance`: All tests pass criteria
- `flow_control.pre_analysis`: Load implementation summaries
- `flow_control.implementation_approach`: Test execution strategy
**Parse Output**: **Parse Output**:
- Verify `.workflow/[sessionId]/.task/TEST-FIX-001.json` exists - Verify `.workflow/[testSessionId]/.process/ANALYSIS_RESULTS.md` created
- Verify `.workflow/[sessionId]/IMPL_PLAN.md` updated - Contains test strategy and execution plan
- Verify `.workflow/[sessionId]/TODO_LIST.md` updated - Lists code modification targets (format: `file:function:lines` or `file`)
- Includes risk assessment and optimization recommendations
**Validation**: **Validation**:
- Task JSON has correct structure (id, meta.type="test-fix", meta.agent="@test-fix-agent") - File `.workflow/[testSessionId]/.process/ANALYSIS_RESULTS.md` exists
- IMPL_PLAN.md contains test-fix strategy - Contains complete analysis sections:
- TODO_LIST.md shows TEST-FIX-001 task - Current State Analysis (test coverage, existing tests)
- Proposed Solution Design (test execution strategy)
- Implementation Strategy (code targets, feasibility)
- Solution Optimization (performance, quality)
- Critical Success Factors (acceptance criteria)
**TodoWrite**: Mark phase 3 completed, phase 4 in_progress **TodoWrite**: Mark phase 3 completed, phase 4 in_progress
--- ---
### Phase 4: Execute Test-Fix Workflow ### Phase 4: Generate Test Task
**Command**: `SlashCommand(command="/workflow:execute --session [sessionId]")` **Command**: `SlashCommand(command="/workflow:tools:task-generate --session [testSessionId]")`
**Input**: `sessionId` from Phase 1 **Input**: `testSessionId` from Phase 1
**Expected Behavior**: **Expected Behavior**:
- Workflow executor detects TEST-FIX-001 task - Reads ANALYSIS_RESULTS.md from Phase 3
- Assigns to @test-fix-agent - Extracts test strategy and code modification targets
- Agent executes tests using flow_control.pre_analysis - Generates `IMPL-001.json` (reusing standard format) with:
- If failures: diagnoses and fixes code - `meta.type: "test-fix"` (enables @test-fix-agent assignment)
- Re-runs tests until all pass - `meta.agent: "@test-fix-agent"`
- Generates completion summary - `context.requirements`: Test execution requirements from analysis
- `context.focus_paths`: Test files and source files from analysis
- `context.acceptance`: All tests pass criteria
- `flow_control.pre_analysis`: Load source session summaries
- `flow_control.implementation_approach`: Test execution strategy from ANALYSIS_RESULTS.md
- `flow_control.target_files`: Code modification targets from analysis
**Parse Output**:
- Verify `.workflow/[testSessionId]/.task/IMPL-001.json` exists
- Verify `.workflow/[testSessionId]/IMPL_PLAN.md` created
- Verify `.workflow/[testSessionId]/TODO_LIST.md` created
**Validation**: **Validation**:
- Workflow execution started successfully - Task JSON has `id: "IMPL-001"` and `meta.type: "test-fix"`
- TEST-FIX-001 task status updated to "active" or "completed" - IMPL_PLAN.md contains test validation strategy from ANALYSIS_RESULTS.md
- TODO_LIST.md shows IMPL-001 task
- flow_control includes code targets and test strategy
- Task is ready for /workflow:execute
**TodoWrite**: Mark phase 4 completed **TodoWrite**: Mark phase 4 completed
**Return to User**: **Return to User**:
``` ```
Test-fix workflow initiated for session: [sessionId] Independent test-fix workflow created successfully!
- TEST-FIX-001 created and executing
- @test-fix-agent validating implementation Source Session: [sourceSessionId]
- Progress: /workflow:status [sessionId] Test Session: [testSessionId]
Task Created: IMPL-001 (test-fix)
Next Steps:
1. Review test plan: .workflow/[testSessionId]/IMPL_PLAN.md
2. Execute validation: /workflow:execute
3. Monitor progress: /workflow:status
The @test-fix-agent will:
- Execute all tests
- Diagnose any failures
- Fix code until tests pass
``` ```
--- ---
@@ -150,72 +193,112 @@ Test-fix workflow initiated for session: [sessionId]
```javascript ```javascript
// Initialize (before Phase 1) // Initialize (before Phase 1)
TodoWrite({todos: [ TodoWrite({todos: [
{"content": "Execute context gathering for test-fix", "status": "in_progress", "activeForm": "Executing context gathering for test-fix"}, {"content": "Create independent test session", "status": "in_progress", "activeForm": "Creating test session"},
{"content": "Execute implementation analysis", "status": "pending", "activeForm": "Executing implementation analysis"}, {"content": "Gather cross-session context", "status": "pending", "activeForm": "Gathering cross-session context"},
{"content": "Execute TEST-FIX task generation", "status": "pending", "activeForm": "Executing TEST-FIX task generation"}, {"content": "Analyze implementation for test strategy", "status": "pending", "activeForm": "Analyzing implementation"},
{"content": "Execute test-fix workflow", "status": "pending", "activeForm": "Executing test-fix workflow"} {"content": "Generate test validation task", "status": "pending", "activeForm": "Generating test validation task"}
]}) ]})
// After Phase 1 // After Phase 1
TodoWrite({todos: [ TodoWrite({todos: [
{"content": "Execute context gathering for test-fix", "status": "completed", "activeForm": "Executing context gathering for test-fix"}, {"content": "Create independent test session", "status": "completed", "activeForm": "Creating test session"},
{"content": "Execute implementation analysis", "status": "in_progress", "activeForm": "Executing implementation analysis"}, {"content": "Gather cross-session context", "status": "in_progress", "activeForm": "Gathering cross-session context"},
{"content": "Execute TEST-FIX task generation", "status": "pending", "activeForm": "Executing TEST-FIX task generation"}, {"content": "Analyze implementation for test strategy", "status": "pending", "activeForm": "Analyzing implementation"},
{"content": "Execute test-fix workflow", "status": "pending", "activeForm": "Executing test-fix workflow"} {"content": "Generate test validation task", "status": "pending", "activeForm": "Generating test validation task"}
]}) ]})
// Continue pattern for Phase 2, 3, 4... // After Phase 2
TodoWrite({todos: [
{"content": "Create independent test session", "status": "completed", "activeForm": "Creating test session"},
{"content": "Gather cross-session context", "status": "completed", "activeForm": "Gathering cross-session context"},
{"content": "Analyze implementation for test strategy", "status": "in_progress", "activeForm": "Analyzing implementation"},
{"content": "Generate test validation task", "status": "pending", "activeForm": "Generating test validation task"}
]})
// After Phase 3
TodoWrite({todos: [
{"content": "Create independent test session", "status": "completed", "activeForm": "Creating test session"},
{"content": "Gather cross-session context", "status": "completed", "activeForm": "Gathering cross-session context"},
{"content": "Analyze implementation for test strategy", "status": "completed", "activeForm": "Analyzing implementation"},
{"content": "Generate test validation task", "status": "in_progress", "activeForm": "Generating test validation task"}
]})
// After Phase 4
TodoWrite({todos: [
{"content": "Create independent test session", "status": "completed", "activeForm": "Creating test session"},
{"content": "Gather cross-session context", "status": "completed", "activeForm": "Gathering cross-session context"},
{"content": "Analyze implementation for test strategy", "status": "completed", "activeForm": "Analyzing implementation"},
{"content": "Generate test validation task", "status": "completed", "activeForm": "Generating test validation task"}
]})
``` ```
## Data Flow ## Data Flow
``` ```
Session ID (from argument or auto-detect) User: /workflow:test-gen WFS-user-auth
↓ ↓
Phase 1: context-gather --session sessionId "test-fix description" Phase 1: session-start --new "Test validation for WFS-user-auth"
↓ Output: contextPath (context-package-test.json) ↓ Creates: WFS-test-user-auth session
↓ Writes: workflow-session.json with workflow_type="test_session", source_session_id="WFS-user-auth"
↓ Output: testSessionId = "WFS-test-user-auth"
↓ ↓
Phase 2: concept-enhanced --session sessionId --context contextPath Phase 2: context-gather --session WFS-test-user-auth
↓ Input: sessionId + contextPath ↓ Auto-detects: test session type from workflow-session.json
↓ Output: ANALYSIS_RESULTS.md (test execution strategy) ↓ Auto-reads: source_session_id = "WFS-user-auth"
↓ Gathers: Cross-session context (summaries, code changes, tests)
↓ Output: .workflow/WFS-test-user-auth/.process/context-package.json
↓ ↓
Phase 3: task-generate --session sessionId Phase 3: concept-enhanced --session WFS-test-user-auth --context context-package.json
↓ Input: sessionId + ANALYSIS_RESULTS.md ↓ Reads: context-package.json with cross-session artifacts
↓ Output: TEST-FIX-001.json, IMPL_PLAN.md, TODO_LIST.md ↓ Executes: Parallel analysis (Gemini test strategy + optional Codex validation)
↓ Analyzes: Test coverage, execution strategy, code targets
↓ Output: .workflow/WFS-test-user-auth/.process/ANALYSIS_RESULTS.md
↓ ↓
Phase 4: execute --session sessionId Phase 4: task-generate --session WFS-test-user-auth
↓ Input: sessionId + TEST-FIX-001.json ↓ Reads: ANALYSIS_RESULTS.md with test strategy and code targets
↓ Output: Test execution and fixing ↓ Generates: IMPL-001.json with meta.type="test-fix"
↓ Output: Task, plan, and todo files in test session
↓ ↓
Return summary to user Return: Summary with next steps (user triggers /workflow:execute separately)
``` ```
## Context Gathering Customization ## Session Metadata Design
context-gather will analyze: **Test Session (`WFS-test-user-auth/workflow-session.json`)**:
- Completed IMPL task summaries ```json
- Git changes since session start {
- Test files in focus_paths "session_id": "WFS-test-user-auth",
- Implementation files to be tested "project": "Test validation for user authentication implementation",
- Test framework configuration "status": "planning",
"created_at": "2025-10-03T12:00:00Z",
"workflow_type": "test_session",
"source_session_id": "WFS-user-auth"
}
```
## Analysis Focus ## Automatic Cross-Session Context Collection
concept-enhanced will analyze: When `context-gather` detects `workflow_type: "test_session"`:
- Test coverage gaps
- Test execution strategy (unit, integration, e2e) **Collected from Source Session** (`.workflow/WFS-user-auth/`):
- Failure diagnosis approaches - Implementation summaries: `.summaries/IMPL-*-summary.md`
- Code fixing patterns - Code changes: `git log --since=[source_created_at] --name-only`
- Test framework best practices - Original plan: `IMPL_PLAN.md`
- Task definitions: `.task/IMPL-*.json`
**Collected from Current Project**:
- Test files: `mcp__code-index__find_files(pattern="*.test.*")`
- Test configuration: `package.json`, `jest.config.js`, etc.
- Source files: Based on changed files from git log
## Task Generation Output ## Task Generation Output
task-generate creates TEST-FIX-001.json with: task-generate creates `IMPL-001.json` (reusing standard format) with:
```json ```json
{ {
"id": "TEST-FIX-001", "id": "IMPL-001",
"title": "Execute and validate tests for [sessionId]", "title": "Execute and validate tests for [sourceSessionId]",
"status": "pending", "status": "pending",
"meta": { "meta": {
"type": "test-fix", "type": "test-fix",
@@ -239,11 +322,11 @@ task-generate creates TEST-FIX-001.json with:
"flow_control": { "flow_control": {
"pre_analysis": [ "pre_analysis": [
{ {
"step": "load_implementation_summaries", "step": "load_source_session_summaries",
"action": "Load completed IMPL task summaries", "action": "Load implementation summaries from source session",
"commands": [ "commands": [
"bash(find .workflow/[sessionId]/.summaries/ -name 'IMPL-*-summary.md' 2>/dev/null)", "bash(find .workflow/[sourceSessionId]/.summaries/ -name 'IMPL-*-summary.md' 2>/dev/null)",
"Read(.workflow/[sessionId]/.summaries/IMPL-001-summary.md)" "Read(.workflow/[sourceSessionId]/.summaries/IMPL-001-summary.md)"
], ],
"output_to": "implementation_context", "output_to": "implementation_context",
"on_error": "skip_optional" "on_error": "skip_optional"
@@ -286,20 +369,22 @@ task-generate creates TEST-FIX-001.json with:
## Error Handling ## Error Handling
### Phase 1 Failures ### Phase 1 Failures
- **No session found**: Return error "No active session detected. Provide session-id or run /workflow:plan first" - **Source session not found**: Return error "Source session [sourceSessionId] not found in .workflow/"
- **Invalid session**: Return error "Session [sessionId] not found or incomplete" - **Invalid source session**: Return error "Source session [sourceSessionId] has no completed IMPL tasks"
- **No implementation**: Return error "No completed IMPL tasks found. Complete implementation first" - **Session creation failed**: Return error "Could not create test session. Check /workflow:session:start"
### Phase 2 Failures ### Phase 2 Failures
- **Analysis failed**: Return error "Implementation analysis failed. Check context package" - **Context gathering failed**: Return error "Could not gather cross-session context. Check source session artifacts"
- **No test strategy**: Return error "Could not determine test execution strategy" - **No source artifacts**: Return error "Source session has no implementation summaries or git history"
### Phase 3 Failures ### Phase 3 Failures
- **Task generation failed**: Retry once, then return error with details - **Analysis failed**: Return error "Implementation analysis failed. Check context package and ANALYSIS_RESULTS.md"
- **Invalid task structure**: Return error with JSON validation details - **No test strategy**: Return error "Could not determine test execution strategy from analysis"
- **Missing code targets**: Warning only, proceed with general test task
### Phase 4 Failures ### Phase 4 Failures
- **Execution failed**: Return error "Could not start test-fix workflow. Check session state" - **Task generation failed**: Retry once, then return error with details
- **Invalid task structure**: Return error with JSON validation details
## Workflow Integration ## Workflow Integration
@@ -307,18 +392,22 @@ task-generate creates TEST-FIX-001.json with:
``` ```
1. Implementation Phase (prior to test-gen) 1. Implementation Phase (prior to test-gen)
/workflow:plan "Build auth system" /workflow:plan "Build auth system"
→ Creates WFS-auth session
→ @code-developer implements + writes tests → @code-developer implements + writes tests
→ Creates IMPL-001-summary.md → Creates IMPL-001-summary.md in WFS-auth
2. Test Generation Phase (test-gen) 2. Test Generation Phase (test-gen)
/workflow:test-gen WFS-auth /workflow:test-gen WFS-auth
Phase 1: context-gather → Creates context-package-test.json Phase 1: session-start → Creates WFS-test-auth session
Phase 2: concept-enhanced → Creates ANALYSIS_RESULTS.md Phase 2: context-gather → Gathers from WFS-auth, creates context-package.json
Phase 3: task-generate → Creates TEST-FIX-001.json Phase 3: concept-enhanced → Analyzes implementation, creates ANALYSIS_RESULTS.md
Phase 4: execute → Triggers @test-fix-agent Phase 4: task-generate → Creates IMPL-001.json with meta.type="test-fix"
Returns: Summary with next steps
3. Test-Fix Phase (automated) 3. Test Execution Phase (user-triggered)
@test-fix-agent picks up TEST-FIX-001 /workflow:execute
→ Detects active session: WFS-test-auth
→ @test-fix-agent picks up IMPL-001 (test-fix type)
→ Runs test suite → Runs test suite
→ Diagnoses failures (if any) → Diagnoses failures (if any)
→ Fixes source code → Fixes source code
@@ -327,39 +416,72 @@ task-generate creates TEST-FIX-001.json with:
``` ```
### Output Files Created ### Output Files Created
- `.workflow/[sessionId]/.process/context-package-test.json` - Test context package
- `.workflow/[sessionId]/.process/ANALYSIS_RESULTS.md` - Test execution strategy **In Test Session** (`.workflow/WFS-test-auth/`):
- `.workflow/[sessionId]/.task/TEST-FIX-001.json` - Task definition - `workflow-session.json` - Contains workflow_type and source_session_id
- `.workflow/[sessionId]/IMPL_PLAN.md` - Updated with test-fix plan - `.process/context-package.json` - Cross-session context from WFS-auth
- `.workflow/[sessionId]/TODO_LIST.md` - Updated with TEST-FIX task - `.process/ANALYSIS_RESULTS.md` - Test strategy and code targets from concept-enhanced
- `.workflow/[sessionId]/.summaries/TEST-FIX-001-summary.md` - Created by test-fix-agent after completion - `.task/IMPL-001.json` - Test-fix task definition
- `IMPL_PLAN.md` - Test validation plan (from ANALYSIS_RESULTS.md)
- `TODO_LIST.md` - Task checklist
- `.summaries/IMPL-001-summary.md` - Created by @test-fix-agent after completion
## Best Practices ## Best Practices
1. **Run after implementation complete**: Ensure all IMPL tasks are done before test-gen 1. **Run after implementation complete**: Ensure source session has completed IMPL tasks and summaries
2. **Check git commits**: Make sure implementation changes are committed 2. **Check git commits**: Implementation changes should be committed for accurate git log analysis
3. **Verify test files exist**: Code-developer should have created tests 3. **Verify test files exist**: Source implementation should include test files
4. **Monitor execution**: Use `/workflow:status` to track test-fix progress 4. **Independent sessions**: Test session is separate from implementation session for clean separation
5. **Review failures**: If tests fail repeatedly, check test-fix-agent summary for details 5. **Monitor execution**: Use `/workflow:status` to track test-fix progress after /workflow:execute
## Coordinator Checklist ## Coordinator Checklist
✅ Initialize TodoWrite before any command ✅ Initialize TodoWrite before any command (4 phases)
✅ Execute Phase 1 immediately with session ID ✅ Phase 1: Create test session with source session ID
✅ Parse context package path from Phase 1 output ✅ Parse new test session ID from Phase 1 output
✅ Pass session ID and context path to Phase 2 command ✅ Phase 2: Run context-gather (auto-detects test session, no extra params)
✅ Verify ANALYSIS_RESULTS.md after Phase 2 ✅ Verify context-package.json contains cross-session artifacts
✅ Pass session ID to Phase 3 command ✅ Phase 3: Run concept-enhanced with session and context path
✅ Verify all Phase 3 outputs (task JSON, IMPL_PLAN, TODO_LIST) ✅ Verify ANALYSIS_RESULTS.md contains test strategy and code targets
✅ Pass session ID to Phase 4 command ✅ Phase 4: Run task-generate to create IMPL-001.json
✅ Verify task has meta.type="test-fix" and meta.agent="@test-fix-agent"
✅ Verify flow_control includes analysis insights and code targets
✅ Update TodoWrite after each phase ✅ Update TodoWrite after each phase
✅ Return summary only after Phase 4 completes ✅ Return summary after Phase 4 (execution is separate user action)
## Required Tool Modifications
### `/workflow:session:start`
- Support `--new` flag for test session creation
- Auto-detect test session pattern from task description
- Write `workflow_type: "test_session"` and `source_session_id` to metadata
### `/workflow:tools:context-gather`
- Read session metadata to detect `workflow_type: "test_session"`
- Auto-extract `source_session_id` from metadata
- Gather cross-session context from source session artifacts
- Include git log analysis from source session creation time
### `/workflow:tools:concept-enhanced`
- No changes required (already supports cross-session context analysis)
- Will automatically analyze test strategy based on context-package.json
- Generates ANALYSIS_RESULTS.md with code targets and test execution plan
### `/workflow:tools:task-generate`
- Recognize test session context and generate appropriate task
- Create `IMPL-001.json` with `meta.type: "test-fix"`
- Extract test strategy from ANALYSIS_RESULTS.md
- Include code targets and cross-session references in flow_control
### `/workflow:execute`
- No changes required (already dispatches by meta.agent)
## Related Commands ## Related Commands
- `/workflow:plan` - Create implementation workflow (run before test-gen) - `/workflow:plan` - Create implementation workflow (run before test-gen)
- `/workflow:tools:context-gather` - Phase 1 tool for context collection - `/workflow:session:start` - Phase 1 tool for test session creation
- `/workflow:tools:concept-enhanced` - Phase 2 tool for analysis - `/workflow:tools:context-gather` - Phase 2 tool for cross-session context collection
- `/workflow:tools:task-generate` - Phase 3 tool for task creation - `/workflow:tools:concept-enhanced` - Phase 3 tool for implementation analysis and test strategy
- `/workflow:execute` - Phase 4 workflow execution - `/workflow:tools:task-generate` - Phase 4 tool for test task creation
- `/workflow:execute` - Execute test-fix workflow (user-triggered after test-gen)
- `/workflow:status` - Check workflow progress - `/workflow:status` - Check workflow progress
- `@test-fix-agent` - Agent that executes and fixes tests - `@test-fix-agent` - Agent that executes and fixes tests