refactor: Add tree-style execution flow diagrams to all workflow commands

Added tree-style execution process diagrams using ASCII art (├─, └─, │) to 34 workflow command files across three directories for improved readability and execution flow clarity.

## Changes by Directory

### workflow/ root (17 files)
- lite-plan.md, lite-execute.md, lite-fix.md
- plan.md, execute.md, replan.md
- status.md, review.md, review-fix.md
- review-session-cycle.md, review-module-cycle.md
- session commands (start, complete, resume, list)
- tdd-plan.md, tdd-verify.md, test-cycle-execute.md, test-gen.md, test-fix-gen.md

### workflow/ui-design/ (10 files)
- layout-extract.md, animation-extract.md, style-extract.md
- generate.md, import-from-code.md, codify-style.md
- imitate-auto.md, explore-auto.md
- reference-page-generator.md, design-sync.md

### workflow/tools/ (8 files)
- conflict-resolution.md, task-generate-agent.md, context-gather.md
- tdd-coverage-analysis.md, task-generate-tdd.md
- test-task-generate.md, test-concept-enhanced.md, test-context-gather.md

## Diagram Features
- Input parsing with flag enumeration
- Decision branching with conditional paths
- Phase/step hierarchy with clear nesting
- Mode detection and validation flows

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

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-11-27 16:13:30 +08:00
parent 964bbbf5bc
commit 2a11d5f190
27 changed files with 940 additions and 79 deletions

View File

@@ -52,14 +52,42 @@ Fast-track bug fixing workflow optimized for quick diagnosis, targeted fixes, an
## Execution Process
### Workflow Overview
```
Bug Input → Diagnosis (Phase 1) → Impact Assessment (Phase 2)
Severity Auto-Detection → Fix Planning (Phase 3)
Verification Strategy (Phase 4) → User Confirmation (Phase 5) → Execution (Phase 6)
Input Parsing:
└─ Parse flags: --hotfix → hotfixMode = true | false
Phase 1: Diagnosis & Root Cause Analysis
└─ Decision (confidence-based):
├─ High confidence (specific error) → Direct grep search (5min)
├─ Medium confidence → cli-explore-agent focused search (10-15min)
└─ Low confidence (vague) → cli-explore-agent broad search (20min)
└─ Hotfix mode: Minimal search (Read suspected file + git blame)
Phase 2: Impact Assessment & Severity Auto-Detection
└─ Calculate risk_score → Auto-determine severity
├─ ≥8.0 → critical
├─ ≥5.0 → high
├─ ≥3.0 → medium
└─ <3.0 → low
└─ Hotfix mode: Skip, assume critical
Phase 3: Fix Planning & Strategy Selection
└─ Decision (by risk score):
├─ risk_score ≥5.0 or hotfix → Single best strategy (fastest)
└─ risk_score <5.0 → Multiple strategy options for user selection
Phase 4: Verification Strategy
└─ Select test scope by risk score
└─ Define branch strategy (feature vs hotfix)
Phase 5: User Confirmation
└─ Default mode: 3 dimensions (approach, execution, verification)
└─ Hotfix mode: 2 dimensions (deploy confirmation, monitoring)
Phase 6: Execution Dispatch
├─ Export Enhanced Task JSON
├─ Dispatch to lite-execute --in-memory
└─ Hotfix mode: Generate follow-up tasks
```
### Phase Summary
@@ -77,6 +105,14 @@ Bug Input → Diagnosis (Phase 1) → Impact Assessment (Phase 2)
## Detailed Phase Execution
### Input Parsing
**Parse --hotfix flag**:
```javascript
const hotfixMode = $ARGUMENTS.includes('--hotfix') || $ARGUMENTS.includes('-h')
const bugDescription = $ARGUMENTS.replace(/--hotfix|-h/g, '').trim()
```
### Phase 1: Diagnosis & Root Cause Analysis
**Goal**: Identify root cause and affected code paths
@@ -480,7 +516,6 @@ if (mode === "hotfix") {
- Location: ${sessionFolder}/followup.json
`)
}
}
```
**TodoWrite**: Mark Phase 6 completed