Add TDD Structure Validation and Verification Phases with Comprehensive Reporting

- Introduced Phase 6: TDD Structure Validation to ensure compliance with TDD workflow standards, including task structure validation, dependency checks, and user configuration verification.
- Implemented Phase 7: TDD Verification for full compliance checks, including task chain structure validation, coverage analysis, and TDD cycle verification.
- Generated detailed TDD compliance reports with quality gate recommendations based on objective criteria.
- Added documentation for new commands and workflows in the Claude Commands index.
This commit is contained in:
catlog22
2026-02-28 20:41:06 +08:00
parent 4a89f626fc
commit 65763c76e9
92 changed files with 643 additions and 525 deletions

View File

@@ -29,9 +29,9 @@ Commands are organized into the following categories:
High-level orchestrators for complex, multi-phase development processes.
### **/workflow:plan**
### **/workflow-plan**
- **Syntax**: `/workflow:plan [--agent] [--cli-execute] "text description"|file.md`
- **Syntax**: `/workflow-plan [--agent] [--cli-execute] "text description"|file.md`
- **Parameters**:
- `--agent` (Optional, Flag): Use the `task-generate-agent` for autonomous task generation.
- `--cli-execute` (Optional, Flag): Generate tasks with commands ready for CLI execution (e.g., using Codex).
@@ -39,15 +39,15 @@ High-level orchestrators for complex, multi-phase development processes.
- **Responsibilities**: Orchestrates a 5-phase planning workflow that includes session start, context gathering, intelligent analysis, concept clarification (quality gate), and task generation.
- **Agent Calls**: Delegates analysis to `@cli-execution-agent` and task generation to `@action-planning-agent`.
- **Skill Invocation**: Does not directly invoke a skill, but the underlying agents may.
- **Integration**: This is a primary entry point for starting a development workflow. It is followed by `/workflow:execute`.
- **Integration**: This is a primary entry point for starting a development workflow. It is followed by `/workflow-execute`.
- **Example**:
```bash
/workflow:plan "Create a simple Express API that returns Hello World"
/workflow-plan "Create a simple Express API that returns Hello World"
```
### **/workflow:lite-plan** ⚡ NEW
### **/workflow-lite-plan** ⚡ NEW
- **Syntax**: `/workflow:lite-plan [--tool claude|gemini|qwen|codex] [-e|--explore] "task description"|file.md`
- **Syntax**: `/workflow-lite-plan [--tool claude|gemini|qwen|codex] [-e|--explore] "task description"|file.md`
- **Parameters**:
- `--tool` (Optional, String): Preset CLI tool for execution (claude|gemini|qwen|codex). If not provided, user selects during confirmation.
- `-e, --explore` (Optional, Flag): Force code exploration phase (overrides auto-detection logic).
@@ -70,31 +70,31 @@ High-level orchestrators for complex, multi-phase development processes.
- `@cli-planning-agent` (conditional, Phase 3 for Medium/High complexity)
- `@code-developer` (conditional, Phase 5 if Agent execution selected)
- **Skill Invocation**: None directly, but agents may invoke skills.
- **Integration**: Standalone workflow for quick tasks. Alternative to `/workflow:plan` + `/workflow:execute` pattern.
- **Integration**: Standalone workflow for quick tasks. Alternative to `/workflow-plan` + `/workflow-execute` pattern.
- **Example**:
```bash
# Basic usage with auto-detection
/workflow:lite-plan "Add JWT authentication to user login"
/workflow-lite-plan "Add JWT authentication to user login"
# Force code exploration
/workflow:lite-plan -e "Refactor logging module for better performance"
/workflow-lite-plan -e "Refactor logging module for better performance"
# Basic usage
/workflow:lite-plan "Add unit tests for auth service"
/workflow-lite-plan "Add unit tests for auth service"
```
### **/workflow:execute**
### **/workflow-execute**
- **Syntax**: `/workflow:execute [--resume-session="session-id"]`
- **Syntax**: `/workflow-execute [--resume-session="session-id"]`
- **Parameters**:
- `--resume-session` (Optional, String): The ID of a paused session to resume.
- **Responsibilities**: Discovers and executes all pending tasks in the active (or specified) workflow session. It handles dependency resolution and orchestrates agents to perform the work.
- **Agent Calls**: Dynamically calls the agent specified in each task's `meta.agent` field (e.g., `@code-developer`, `@test-fix-agent`).
- **Integration**: The primary command for implementing a plan generated by `/workflow:plan`.
- **Integration**: The primary command for implementing a plan generated by `/workflow-plan`.
- **Example**:
```bash
# Execute tasks in the currently active session
/workflow:execute
/workflow-execute
```
### **/workflow:resume**
@@ -102,8 +102,8 @@ High-level orchestrators for complex, multi-phase development processes.
- **Syntax**: `/workflow:resume "session-id"`
- **Parameters**:
- `session-id` (Required, String): The ID of the workflow session to resume.
- **Responsibilities**: A two-phase orchestrator that first analyzes the status of a paused session and then resumes it by calling `/workflow:execute --resume-session`.
- **Agent Calls**: None directly. It orchestrates `/workflow:status` and `/workflow:execute`.
- **Responsibilities**: A two-phase orchestrator that first analyzes the status of a paused session and then resumes it by calling `/workflow-execute --resume-session`.
- **Agent Calls**: None directly. It orchestrates `/workflow:status` and `/workflow-execute`.
- **Integration**: Used to continue a previously paused or interrupted workflow.
- **Example**:
```bash
@@ -118,7 +118,7 @@ High-level orchestrators for complex, multi-phase development processes.
- `session-id` (Optional, String): The session to review. Defaults to the active session.
- **Responsibilities**: Performs a specialized, post-implementation review. This is optional, as the default quality gate is passing tests.
- **Agent Calls**: Uses `gemini` or `qwen-wrapper` for analysis based on the review type.
- **Integration**: Used after `/workflow:execute` to perform audits before deployment.
- **Integration**: Used after `/workflow-execute` to perform audits before deployment.
- **Example**:
```bash
/workflow:review --type=security
@@ -202,7 +202,7 @@ CLI tool configuration commands.
/cli:cli-init
```
> **Note**: For analysis, planning, and bug fixing, use workflow commands (`/workflow:lite-plan`, `/workflow:lite-fix`) or semantic invocation through natural language. Claude will automatically use appropriate CLI tools (Gemini/Qwen/Codex) with templates as needed.
> **Note**: For analysis, planning, and bug fixing, use workflow commands (`/workflow-lite-plan`, `/workflow:lite-fix`) or semantic invocation through natural language. Claude will automatically use appropriate CLI tools (Gemini/Qwen/Codex) with templates as needed.
---
@@ -402,22 +402,22 @@ Specialized workflow for UI/UX design, from style extraction to prototype genera
Workflows for Test-Driven Development (TDD) and post-implementation test generation.
### **/workflow:tdd-plan**
- **Syntax**: `/workflow:tdd-plan [--agent] "feature description"|file.md`
### **/workflow-tdd-plan**
- **Syntax**: `/workflow-tdd-plan [--agent] "feature description"|file.md`
- **Responsibilities**: Orchestrates a 7-phase TDD planning workflow, creating tasks with Red-Green-Refactor cycles.
- **Agent Calls**: Orchestrates sub-commands which may call agents.
- **Example**:
```bash
/workflow:tdd-plan "Implement a secure login endpoint"
/workflow-tdd-plan "Implement a secure login endpoint"
```
### **/workflow:tdd-verify**
- **Syntax**: `/workflow:tdd-verify [session-id]`
### **/workflow-tdd-verify**
- **Syntax**: `/workflow-tdd-verify [session-id]`
- **Responsibilities**: Verifies TDD workflow compliance by analyzing task chains, test coverage, and cycle execution.
- **Agent Calls**: None directly, orchestrates `gemini`.
- **Example**:
```bash
/workflow:tdd-verify WFS-login-tdd
/workflow-tdd-verify WFS-login-tdd
```
### **/workflow:test-gen**
@@ -429,21 +429,21 @@ Workflows for Test-Driven Development (TDD) and post-implementation test generat
/workflow:test-gen WFS-user-auth-v2
```
### **/workflow:test-fix-gen**
- **Syntax**: `/workflow:test-fix-gen [--use-codex] [--cli-execute] (<source-session-id> | "description" | /path/to/file.md)`
### **/workflow-test-fix**
- **Syntax**: `/workflow-test-fix [--use-codex] [--cli-execute] (<source-session-id> | "description" | /path/to/file.md)`
- **Responsibilities**: Creates an independent test-fix workflow from either a completed session or a feature description.
- **Agent Calls**: Orchestrates sub-commands that call `@code-developer` and `@test-fix-agent`.
- **Example**:
```bash
/workflow:test-fix-gen "Test the user authentication API endpoints"
/workflow-test-fix "Test the user authentication API endpoints"
```
### **/workflow:test-cycle-execute**
- **Syntax**: `/workflow:test-cycle-execute [--resume-session="session-id"] [--max-iterations=N]`
- **Responsibilities**: Executes a test-fix workflow by delegating to `/workflow:execute`. Generates test tasks dynamically and creates intermediate fix tasks based on test results.
- **Agent Calls**: Delegates to `/workflow:execute` which invokes `@test-fix-agent` for task execution.
- **Note**: This command generates tasks; actual execution is performed by `/workflow:execute`.
### **/workflow-test-fix**
- **Syntax**: `/workflow-test-fix [--resume-session="session-id"] [--max-iterations=N]`
- **Responsibilities**: Executes a test-fix workflow by delegating to `/workflow-execute`. Generates test tasks dynamically and creates intermediate fix tasks based on test results.
- **Agent Calls**: Delegates to `/workflow-execute` which invokes `@test-fix-agent` for task execution.
- **Note**: This command generates tasks; actual execution is performed by `/workflow-execute`.
- **Example**:
```bash
/workflow:test-cycle-execute --resume-session="WFS-test-user-auth"
/workflow-test-fix --resume-session="WFS-test-user-auth"
```