- Refactor test-task-generate.md to use action-planning-agent
- Add two-phase execution flow (Discovery → Agent Execution)
- Integrate Memory-First principle and MCP tool enhancements
- Support both agent-mode (default) and cli-execute-mode
- Add test-specific context package with TEST_ANALYSIS_RESULTS.md
- Align with task-generate-agent.md architecture
- Remove 556 lines of redundant old content (Phase 1-4 old structure)
- Update test-gen.md and test-fix-gen.md to reflect agent-driven changes
Changes include:
- Core Philosophy with agent-driven principles
- Agent Context Package structure for test sessions
- Discovery Actions for test context loading
- Agent Invocation with test-specific requirements
- Test Task Structure Reference
- Updated Integration & Usage sections
- Enhanced Related Commands documentation
Now test task generation uses autonomous agent planning with MCP enhancements for better test coverage analysis and generation.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Reorganize documentation with improved structure and clarity:
- Add comprehensive dual-mode support (session vs prompt mode)
- Enhance usage examples with clear mode comparison
- Detail task specifications for IMPL-001 and IMPL-002
- Improve phase execution flow descriptions
- Add complete artifacts and output structure
- Expand best practices and related commands sections
The restructured documentation maintains backward compatibility while
making dual-mode functionality more discoverable and easier to use.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Enable test generation for existing codebases without requiring prior
workflow session. Supports both session-based (WFS-xxx) and prompt-based
(text description or file path) inputs with automatic mode detection.
Key improvements:
- Prompt mode: Generate tests from feature description or requirements file
- Backward compatible: Existing session-based usage unchanged
- Flexible input: Accepts session ID, text description, or file path
- Use case: Testing existing APIs without workflow history
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Renamed /workflow:test-execute to /workflow:test-cycle-execute to better
communicate the iterative cycle nature of the command (test → diagnose → fix → retest).
Changes:
- Renamed test-execute.md to test-cycle-execute.md
- Updated command metadata and document title
- Updated 9 internal references within the command file
- Updated reference in test-fix-gen.md related commands section
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Renamed test-gen to test-fix-gen and created new test-execute command for
dynamic iterative test-fix cycles. Improved task generation flexibility and
clarified data flow between planning and execution phases.
Key changes:
- Rename test-gen.md → test-fix-gen.md to reflect task generation purpose
- Add test-execute.md for dynamic test-fix workflow execution with CLI analysis
- Enhance test-fix-gen.md:
* Emphasize code-developer's understanding and analysis responsibilities
* Support flexible task count (minimum 2, expandable based on complexity)
* Add examples for multi-module test generation scenarios
- Clarify test-execute.md data flow:
* failure_context contains raw test output and error messages
* fix_strategy generated by CLI tool (Gemini/Qwen) analysis
* IMPL-001 (test generation) executes first, then IMPL-002 (test-fix cycle)
This improves workflow clarity and enables adaptive test-fix strategies for
complex projects requiring multiple test generation tasks.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
