From c679253c301e28eea4a3e856fc0b71ce4d373ef8 Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Thu, 20 Nov 2025 09:41:32 +0000
Subject: [PATCH] refactor: streamline lite-fix.md to match lite-plan's concise
 style (707 lines)

Reduced from 1700+ lines to 707 lines while preserving core functionality:

Preserved:
- Complete 6-phase execution flow
- Three severity modes (Regular/Critical/Hotfix)
- Data structure definitions
- Best practices and quality gates
- Related commands and comparisons

Removed/Condensed:
- Redundant examples (kept 3 essential ones)
- Verbose implementation details
- Duplicate explanations
- Extended discussion sections

Format matches lite-plan.md (667 lines) for consistency.
Detailed design rationale remains in LITE_FIX_DESIGN.md.
---
 .claude/commands/workflow/lite-fix.md | 940 +++++++-------------------
 1 file changed, 243 insertions(+), 697 deletions(-)

diff --git a/.claude/commands/workflow/lite-fix.md b/.claude/commands/workflow/lite-fix.md
index cfb40f52..ecbe035a 100644
--- a/.claude/commands/workflow/lite-fix.md
+++ b/.claude/commands/workflow/lite-fix.md
@@ -36,40 +36,23 @@ Fast-track bug fixing workflow optimized for quick diagnosis, targeted fixes, an
 
 ### Severity Modes
 
-**Regular Mode** (default):
-- Full diagnosis and exploration
-- Comprehensive test verification
-- Standard branch workflow
-- Time budget: 2-4 hours
+| Mode | Time Budget |适用场景 | 流程特点 |
+|------|-------------|---------|---------|
+| **Regular** (default) | 2-4 hours | 非阻塞bug，<20%用户影响 | 完整诊断 + 全量测试 |
+| **Critical** (`--critical`) | 30-60 min | 核心功能受损，20-50%用户影响 | 聚焦诊断 + 关键测试 |
+| **Hotfix** (`--hotfix`) | 15-30 min | 生产故障，100%用户影响 | 最小诊断 + Smoke测试 + 自动跟进 |
 
-**Critical Mode** (`--critical`):
-- Focused diagnosis (skip deep exploration)
-- Smoke test verification
-- Expedited review process
-- Time budget: 30-60 minutes
+### Examples
 
-**Hotfix Mode** (`--hotfix`):
-- Minimal diagnosis (known issue)
-- Production-grade smoke tests
-- Hotfix branch from production tag
-- Follow-up task auto-generated
-- Time budget: 15-30 minutes
-
-### Input Requirements
-
-**Bug Description Formats**:
 ```bash
-# Natural language
-/workflow:lite-fix "用户登录失败，提示token已过期"
+# Regular mode: 一般bug修复
+/workflow:lite-fix "用户头像上传失败，返回413错误"
 
-# Issue reference
-/workflow:lite-fix "Fix #1234: Payment processing timeout"
+# Critical mode: 紧急但非致命
+/workflow:lite-fix --critical "购物车结算时随机丢失商品"
 
-# Incident reference (critical)
-/workflow:lite-fix --critical --incident INC-2024-1015 "支付网关5xx错误"
-
-# Production hotfix
-/workflow:lite-fix --hotfix "修复内存泄漏导致服务崩溃"
+# Hotfix mode: 生产环境故障
+/workflow:lite-fix --hotfix --incident INC-2024-1015 "支付网关5xx错误"
 ```
 
 ## Execution Process
@@ -81,19 +64,19 @@ Bug Input → Diagnosis (Phase 1) → Impact Assessment (Phase 2)
         ↓
     Fix Planning (Phase 3) → Verification Strategy (Phase 4)
         ↓
-    User Confirmation → Execution (Phase 5) → Monitoring (Phase 6)
+    User Confirmation (Phase 5) → Execution (Phase 6)
 ```
 
 ### Phase Summary
 
-| Phase | Regular | Critical | Hotfix | Skippable |
-|-------|---------|----------|--------|-----------|
-| 1. Diagnosis & Root Cause | Full (30min) | Focused (10min) | Minimal (5min) | ❌ |
-| 2. Impact Assessment | Comprehensive | Targeted | Critical path | ❌ |
-| 3. Fix Planning | Multiple options | Single best | Surgical fix | ❌ |
-| 4. Verification Strategy | Full test suite | Key scenarios | Smoke tests | ❌ |
-| 5. User Confirmation | 4-dimension | 3-dimension | 2-dimension | ❌ |
-| 6. Execution & Monitoring | Standard | Expedited | Real-time | Via lite-execute |
+| Phase | Regular | Critical | Hotfix |
+|-------|---------|----------|--------|
+| 1. Diagnosis | Full (cli-explore-agent) | Focused (direct grep) | Minimal (known issue) |
+| 2. Impact | Comprehensive | Targeted | Critical path only |
+| 3. Planning | Multiple strategies | Single best | Surgical fix |
+| 4. Verification | Full test suite | Key scenarios | Smoke tests |
+| 5. Confirmation | 4 dimensions | 3 dimensions | 2 dimensions |
+| 6. Execution | Via lite-execute | Via lite-execute | Via lite-execute + monitoring |
 
 ---
 
@@ -103,97 +86,58 @@ Bug Input → Diagnosis (Phase 1) → Impact Assessment (Phase 2)
 
 **Goal**: Identify root cause and affected code paths
 
-**Step 1.1: Parse Bug Description**
-
-Extract structured information:
-```javascript
-{
-  symptom: "用户登录失败",
-  error_message: "token已过期",
-  affected_feature: "authentication",
-  keywords: ["login", "token", "expire", "authentication"]
-}
-```
-
-**Step 1.2: Code Search Strategy**
-
-Execution depends on severity mode:
+**Execution Strategy by Mode**:
 
 **Regular Mode** - Comprehensive search:
 ```javascript
 Task(
   subagent_type="cli-explore-agent",
-  description="Diagnose authentication token expiration",
   prompt=`
-  Bug Symptom: ${bug_description}
+  Bug: ${bug_description}
 
   Execute diagnostic search:
-  1. Search error message: Grep "${error_message}" --output_mode content
-  2. Find token validation logic: Glob "**/auth/**/*.{ts,js}"
-  3. Trace token expiration handling: Search "token" AND "expire"
-  4. Check recent changes: git log --since="1 week ago" --grep="auth|token"
-
-  Analyze and return:
-  - Root cause hypothesis (file:line)
-  - Affected code paths
-  - Recent changes correlation
-  - Edge cases and reproduction steps
+  1. Search error message: Grep "${error}" --output_mode content
+  2. Find related code: Glob "**/affected-module/**/*.{ts,js}"
+  3. Trace execution path
+  4. Check recent changes: git log --since="1 week ago"
 
+  Return: Root cause hypothesis, affected paths, reproduction steps
   Time limit: 20 minutes
   `
 )
 ```
 
-**Critical Mode** - Focused search:
-```javascript
-// Skip cli-explore-agent, use direct targeted searches
-Bash(commands=[
-  "grep -r '${error_message}' src/ --include='*.ts' -n | head -10",
-  "git log --oneline --since='1 week ago' --all -- '*auth*' | head -5",
-  "git blame ${suspected_file}"
-])
+**Critical Mode** - Direct targeted search:
+```bash
+grep -r '${error_message}' src/ --include='*.ts' -n | head -10
+git log --oneline --since='1 week ago' -- '*affected*' | head -5
+git blame ${suspected_file}
 ```
 
 **Hotfix Mode** - Minimal search (assume known issue):
-```javascript
-// User provides suspected file/function, skip exploration
-Read(suspected_file)
+```bash
+Read(suspected_file)  # User provides file path
 ```
 
-**Step 1.3: Root Cause Determination**
-
-Output structured diagnosis:
+**Output Structure**:
 ```javascript
 {
   root_cause: {
     file: "src/auth/tokenValidator.ts",
     line_range: "45-52",
-    issue: "Token expiration check uses wrong timestamp comparison",
-    introduced_by: "commit abc123 on 2024-10-15"
+    issue: "Token expiration check uses wrong comparison",
+    introduced_by: "commit abc123"
   },
-  reproduction_steps: [
-    "Login with valid credentials",
-    "Wait 15 minutes (half of token TTL)",
-    "Attempt protected route access",
-    "Observe premature expiration error"
-  ],
+  reproduction_steps: ["Login", "Wait 15min", "Access protected route"],
   affected_scope: {
     users: "All authenticated users",
-    features: ["login", "API access", "session management"],
+    features: ["login", "API access"],
     data_risk: "none"
   }
 }
 ```
 
-**Progress Tracking**:
-```json
-[
-  {"content": "Parse bug description and extract keywords", "status": "completed", "activeForm": "Parsing bug"},
-  {"content": "Execute code search for root cause", "status": "completed", "activeForm": "Searching code"},
-  {"content": "Determine root cause and affected scope", "status": "completed", "activeForm": "Analyzing root cause"},
-  {"content": "Phase 2: Impact assessment", "status": "in_progress", "activeForm": "Assessing impact"}
-]
-```
+**TodoWrite**: Mark Phase 1 completed, Phase 2 in_progress
 
 ---
 
@@ -201,87 +145,46 @@ Output structured diagnosis:
 
 **Goal**: Quantify blast radius and risk level
 
-**Step 2.1: User Impact Analysis**
-
-```javascript
-{
-  affected_users: {
-    count: "100% of active users (est. 5000)",
-    severity: "high",
-    workaround: "Re-login required (poor UX)"
-  },
-  affected_features: [
-    {
-      feature: "API authentication",
-      criticality: "critical",
-      degradation: "complete_failure"
-    },
-    {
-      feature: "Session management",
-      criticality: "high",
-      degradation: "partial_failure"
-    }
-  ]
-}
-```
-
-**Step 2.2: Data & System Risk**
-
-```javascript
-{
-  data_risk: {
-    corruption: "none",
-    loss: "none",
-    exposure: "none"
-  },
-  system_risk: {
-    availability: "degraded_30%",
-    cascading_failures: "possible_logout_storm",
-    rollback_complexity: "low"
-  },
-  business_impact: {
-    revenue: "medium",
-    reputation: "high",
-    sla_breach: "yes"
-  }
-}
-```
-
-**Step 2.3: Risk Score Calculation**
-
+**Risk Score Calculation**:
 ```javascript
 risk_score = (user_impact × 0.4) + (system_risk × 0.3) + (business_impact × 0.3)
 
-// Example:
-// user_impact=8, system_risk=6, business_impact=7
-// risk_score = 8×0.4 + 6×0.3 + 7×0.3 = 7.1 (HIGH)
-
+// Severity mapping
 if (risk_score >= 8.0) severity = "critical"
 else if (risk_score >= 5.0) severity = "high"
 else if (risk_score >= 3.0) severity = "medium"
 else severity = "low"
 ```
 
-**Output to User**:
-```markdown
-## Impact Assessment
-
-**Risk Level**: HIGH (7.1/10)
-
-**Affected Users**: ~5000 active users (100%)
-**Feature Impact**:
-  - 🔴 API authentication: Complete failure
-  - 🟡 Session management: Partial failure
-
-**Business Impact**:
-  - Revenue: Medium
-  - Reputation: High
-  - SLA: Breached
-
-**Recommended Severity**: --critical flag suggested
+**Assessment Output**:
+```javascript
+{
+  affected_users: {
+    count: "5000 active users (100%)",
+    severity: "high",
+    workaround: "Re-login required"
+  },
+  system_risk: {
+    availability: "degraded_30%",
+    cascading_failures: "possible_logout_storm"
+  },
+  business_impact: {
+    revenue: "medium",
+    reputation: "high",
+    sla_breach: "yes"
+  },
+  risk_score: 7.1,
+  severity: "high"
+}
 ```
 
-**Progress Tracking**: Mark Phase 2 completed, Phase 3 in_progress
+**Auto-Severity Suggestion**:
+If `risk_score >= 8.0` and user didn't provide `--critical`, suggest:
+```
+💡 Suggestion: Consider using --critical flag (risk score: 8.2/10)
+```
+
+**TodoWrite**: Mark Phase 2 completed, Phase 3 in_progress
 
 ---
 
@@ -289,203 +192,139 @@ else severity = "low"
 
 **Goal**: Generate fix options with trade-off analysis
 
-**Step 3.1: Generate Fix Strategies**
+**Strategy Generation by Mode**:
 
-Produce 1-3 fix strategies based on complexity:
-
-**Regular Bug** (1-3 strategies):
+**Regular Mode** - Multiple strategies (1-3 options):
 ```javascript
 [
   {
     strategy: "immediate_patch",
-    description: "Fix timestamp comparison logic",
-    files: ["src/auth/tokenValidator.ts:45-52"],
+    description: "Fix comparison operator",
+    files: ["src/auth/tokenValidator.ts:47"],
     estimated_time: "15 minutes",
     risk: "low",
-    pros: ["Quick fix", "Minimal code change"],
-    cons: ["Doesn't address underlying token refresh issue"]
+    pros: ["Quick fix", "Minimal change"],
+    cons: ["Doesn't address token refresh"]
   },
   {
     strategy: "comprehensive_refactor",
-    description: "Refactor token validation with proper refresh logic",
+    description: "Refactor token validation with proper refresh",
     files: ["src/auth/tokenValidator.ts", "src/auth/refreshToken.ts"],
     estimated_time: "2 hours",
     risk: "medium",
-    pros: ["Addresses root cause", "Improves token handling"],
-    cons: ["Longer implementation", "More testing needed"]
+    pros: ["Addresses root cause"],
+    cons: ["Longer implementation"]
   }
 ]
 ```
 
-**Critical/Hotfix** (1 strategy only):
+**Critical/Hotfix Mode** - Single best strategy:
 ```javascript
-[
-  {
-    strategy: "surgical_fix",
-    description: "Minimal change to fix timestamp comparison",
-    files: ["src/auth/tokenValidator.ts:47"],
-    change: "Replace currentTime > expiryTime with currentTime >= expiryTime",
-    estimated_time: "5 minutes",
-    risk: "minimal",
-    test_strategy: "smoke_test_login_flow"
-  }
-]
+{
+  strategy: "surgical_fix",
+  description: "Minimal change to fix comparison",
+  files: ["src/auth/tokenValidator.ts:47"],
+  change: "currentTime > expiryTime → currentTime >= expiryTime",
+  estimated_time: "5 minutes",
+  risk: "minimal"
+}
 ```
 
-**Step 3.2: Adaptive Planning**
-
-Determine planning strategy based on complexity:
-
+**Complexity Assessment & Planning**:
 ```javascript
 complexity = assessComplexity(fix_strategies)
 
 if (complexity === "low" || mode === "hotfix") {
-  // Direct planning by Claude
-  plan = generateSimplePlan(selected_strategy)
+  plan = generateSimplePlan(selected_strategy)  // Direct by Claude
 } else if (complexity === "medium") {
-  // Use cli-lite-planning-agent
   plan = Task(subagent_type="cli-lite-planning-agent", ...)
 } else {
-  // Suggest full workflow
   suggestCommand("/workflow:plan --mode bugfix")
 }
 ```
 
-**Step 3.3: Generate Fix Plan**
-
-Output structured plan:
+**Plan Output**:
 ```javascript
 {
   summary: "Fix timestamp comparison in token validation",
-  approach: "Update comparison operator to handle edge case",
-  tasks: [
-    {
-      title: "Fix token expiration comparison",
-      file: "src/auth/tokenValidator.ts",
-      action: "Update",
-      description: "Change line 47 comparison from > to >=",
-      implementation: [
-        "Locate validateToken function (line 45)",
-        "Update comparison: currentTime >= expiryTime",
-        "Add comment explaining edge case handling"
-      ],
-      verification: [
-        "Manual test: Login and wait at boundary timestamp",
-        "Run auth integration tests",
-        "Check no regression in token refresh flow"
-      ]
-    }
-  ],
+  approach: "Update comparison operator",
+  tasks: [{
+    title: "Fix token expiration comparison",
+    file: "src/auth/tokenValidator.ts",
+    action: "Update",
+    implementation: ["Locate validateToken", "Update line 47", "Add comment"],
+    verification: ["Manual test at boundary", "Run auth tests"]
+  }],
   estimated_time: "30 minutes",
   recommended_execution: "Agent"
 }
 ```
 
-**Progress Tracking**: Mark Phase 3 completed, Phase 4 in_progress
+**TodoWrite**: Mark Phase 3 completed, Phase 4 in_progress
 
 ---
 
 ### Phase 4: Verification Strategy
 
-**Goal**: Define appropriate testing approach based on severity
+**Goal**: Define testing approach based on severity
 
-**Verification Levels**:
+**Test Strategy Selection**:
 
-| Mode | Test Scope | Duration | Pass Criteria |
-|------|------------|----------|---------------|
-| **Regular** | Full test suite | 10-20 min | All tests pass |
-| **Critical** | Key scenarios | 5-10 min | Critical paths pass |
-| **Hotfix** | Smoke tests | 2-5 min | No regressions in core flow |
+| Mode | Test Scope | Duration | Automation |
+|------|------------|----------|------------|
+| **Regular** | Full test suite | 10-20 min | `npm test` |
+| **Critical** | Focused integration | 5-10 min | `npm test -- auth.test.ts` |
+| **Hotfix** | Smoke tests | 2-5 min | `npm test -- auth.smoke.test.ts` |
 
-**Step 4.1: Select Test Strategy**
+**Branch Strategy**:
 
+**Regular/Critical**:
 ```javascript
-if (mode === "hotfix") {
-  test_strategy = {
-    type: "smoke_tests",
-    tests: [
-      "Login with valid credentials",
-      "Access protected route",
-      "Token refresh at boundary",
-      "Logout successfully"
-    ],
-    automation: "npx jest auth.smoke.test.ts",
-    manual_verification: "Production-like staging test"
-  }
-} else if (mode === "critical") {
-  test_strategy = {
-    type: "focused_integration",
-    tests: [
-      "auth.integration.test.ts",
-      "session.test.ts"
-    ],
-    skip: ["e2e tests", "performance tests"]
-  }
-} else {
-  test_strategy = {
-    type: "comprehensive",
-    tests: "npm test",
-    coverage_threshold: "no_decrease"
-  }
+{
+  type: "feature_branch",
+  base: "main",
+  name: "fix/token-expiration-edge-case",
+  merge_target: "main"
 }
 ```
 
-**Step 4.2: Branching Strategy**
-
+**Hotfix**:
 ```javascript
-if (mode === "hotfix") {
-  branch_strategy = {
-    type: "hotfix_branch",
-    base: "production_tag_v2.3.1",
-    name: "hotfix/token-validation-fix",
-    merge_target: ["main", "production"],
-    tag_after_merge: "v2.3.2"
-  }
-} else {
-  branch_strategy = {
-    type: "feature_branch",
-    base: "main",
-    name: "fix/token-expiration-edge-case",
-    merge_target: "main"
-  }
+{
+  type: "hotfix_branch",
+  base: "production_tag_v2.3.1",  // ⚠️ From production tag
+  name: "hotfix/token-validation-fix",
+  merge_target: ["main", "production"]  // Dual merge
 }
 ```
 
-**Progress Tracking**: Mark Phase 4 completed, Phase 5 in_progress
+**TodoWrite**: Mark Phase 4 completed, Phase 5 in_progress
 
 ---
 
 ### Phase 5: User Confirmation & Execution Selection
 
-**Multi-Dimension Confirmation**
-
-Number of dimensions varies by severity:
+**Multi-Dimension Confirmation**:
 
 **Regular Mode** (4 dimensions):
 ```javascript
 AskUserQuestion({
   questions: [
     {
-      question: `**Fix Strategy**: ${plan.summary}
-
-**Estimated Time**: ${plan.estimated_time}
-**Risk**: ${plan.risk}
-
-Confirm fix approach?`,
+      question: "Confirm fix approach?",
       header: "Fix Confirmation",
-      multiSelect: false,
       options: [
         { label: "Proceed", description: "Execute as planned" },
-        { label: "Modify", description: "Adjust strategy first" },
-        { label: "Escalate", description: "Use full /workflow:plan" }
+        { label: "Modify", description: "Adjust strategy" },
+        { label: "Escalate", description: "Use /workflow:plan" }
       ]
     },
     {
-      question: "Select execution method:",
+      question: "Execution method:",
       header: "Execution",
       options: [
-        { label: "Agent", description: "@code-developer autonomous" },
-        { label: "CLI Tool", description: "Codex/Gemini execution" },
+        { label: "Agent", description: "@code-developer" },
+        { label: "CLI Tool", description: "Codex/Gemini" },
         { label: "Manual", description: "Provide plan only" }
       ]
     },
@@ -493,27 +332,24 @@ Confirm fix approach?`,
       question: "Verification level:",
       header: "Testing",
       options: [
-        { label: "Full Suite", description: "Run all tests (safer)" },
-        { label: "Focused", description: "Affected tests only (faster)" },
-        { label: "Smoke Only", description: "Critical path only (fastest)" }
+        { label: "Full Suite", description: "All tests" },
+        { label: "Focused", description: "Affected tests" },
+        { label: "Smoke Only", description: "Critical path" }
       ]
     },
     {
       question: "Post-fix review:",
       header: "Code Review",
       options: [
-        { label: "Gemini", description: "AI review for quality" },
-        { label: "Skip", description: "Trust automated tests" }
+        { label: "Gemini", description: "AI review" },
+        { label: "Skip", description: "Trust tests" }
       ]
     }
   ]
 })
 ```
 
-**Critical Mode** (3 dimensions - skip detailed review):
-```javascript
-// Skip dimension 4 (code review), auto-apply "Skip"
-```
+**Critical Mode** (3 dimensions - skip code review)
 
 **Hotfix Mode** (2 dimensions - minimal confirmation):
 ```javascript
@@ -522,15 +358,15 @@ AskUserQuestion({
     {
       question: "Confirm hotfix deployment:",
       options: [
-        { label: "Deploy", description: "Apply fix to production" },
+        { label: "Deploy", description: "Apply to production" },
         { label: "Stage First", description: "Test in staging" },
-        { label: "Abort", description: "Cancel hotfix" }
+        { label: "Abort", description: "Cancel" }
       ]
     },
     {
       question: "Post-deployment monitoring:",
       options: [
-        { label: "Real-time", description: "Monitor for 15 minutes" },
+        { label: "Real-time", description: "Monitor 15 minutes" },
         { label: "Passive", description: "Rely on alerts" }
       ]
     }
@@ -538,55 +374,7 @@ AskUserQuestion({
 })
 ```
 
-**Step 5.2: Export Enhanced Task JSON** (optional)
-
-If user confirms "Proceed":
-```javascript
-if (user_wants_json_export) {
-  timestamp = new Date().toISOString().replace(/[:.]/g, '-')
-  taskId = `BUGFIX-${timestamp}`
-  filename = `.workflow/lite-fixes/${taskId}.json`
-
-  Write(filename, {
-    id: taskId,
-    title: bug_description,
-    status: "pending",
-    meta: {
-      type: "bugfix",
-      severity: mode,
-      incident_id: incident_id || null,
-      created_at: timestamp
-    },
-    context: {
-      requirements: [plan.summary],
-      root_cause: diagnosis.root_cause,
-      affected_scope: impact_assessment,
-      focus_paths: plan.tasks.flatMap(t => t.file),
-      acceptance: plan.tasks.flatMap(t => t.verification)
-    },
-    flow_control: {
-      pre_analysis: [
-        {
-          step: "reproduce_bug",
-          action: "Verify bug reproduction",
-          commands: diagnosis.reproduction_steps.map(step => `# ${step}`)
-        }
-      ],
-      implementation_approach: plan.tasks.map((task, i) => ({
-        step: i + 1,
-        title: task.title,
-        description: task.description,
-        modification_points: task.implementation,
-        verification: task.verification,
-        depends_on: i === 0 ? [] : [i]
-      })),
-      target_files: plan.tasks.map(t => t.file)
-    }
-  })
-}
-```
-
-**Progress Tracking**: Mark Phase 5 completed, Phase 6 in_progress
+**TodoWrite**: Mark Phase 5 completed, Phase 6 in_progress
 
 ---
 
@@ -594,12 +382,10 @@ if (user_wants_json_export) {
 
 **Step 6.1: Dispatch to lite-execute**
 
-Store execution context and invoke lite-execute:
-
 ```javascript
 executionContext = {
   mode: "bugfix",
-  severity: mode, // "regular" | "critical" | "hotfix"
+  severity: mode,  // "regular" | "critical" | "hotfix"
   planObject: plan,
   diagnosisContext: diagnosis,
   impactContext: impact_assessment,
@@ -619,145 +405,92 @@ if (mode === "hotfix") {
   follow_up_tasks = [
     {
       id: `FOLLOWUP-${taskId}-comprehensive`,
-      title: "Comprehensive fix for token validation",
-      description: "Replace quick hotfix with proper solution",
+      title: "Replace hotfix with comprehensive fix",
       priority: "high",
-      due_date: "within_3_days",
-      tasks: [
-        "Refactor token validation logic",
-        "Add comprehensive test coverage",
-        "Update documentation"
-      ]
+      due_date: "within_3_days"
     },
     {
       id: `FOLLOWUP-${taskId}-postmortem`,
       title: "Incident postmortem",
-      description: "Root cause analysis and prevention",
       priority: "medium",
-      due_date: "within_1_week",
-      deliverables: [
-        "Timeline of events",
-        "Root cause analysis",
-        "Prevention measures"
-      ]
+      due_date: "within_1_week"
     }
   ]
 
   Write(`.workflow/lite-fixes/${taskId}-followup.json`, follow_up_tasks)
-
-  console.log(`
-  ⚠️ Hotfix applied. Follow-up tasks generated:
-  1. Comprehensive fix: ${follow_up_tasks[0].id}
-  2. Postmortem: ${follow_up_tasks[1].id}
-
-  Review tasks: cat .workflow/lite-fixes/${taskId}-followup.json
-  `)
 }
 ```
 
-**Step 6.3: Monitoring Setup** (if real-time selected)
+**Step 6.3: Real-time Monitoring** (if selected)
 
 ```javascript
 if (user_selection.monitoring === "real-time") {
   console.log(`
   📊 Real-time Monitoring Active (15 minutes)
 
-  Metrics to watch:
-  - Error rate: /metrics/errors?filter=auth
-  - Login success rate: /metrics/login_success
-  - Token validation latency: /metrics/auth_latency
+  Metrics:
+  - Error rate: <5%
+  - Login success: >95%
+  - Auth latency: <500ms
 
-  Auto-rollback triggers:
-  - Error rate > 5%
-  - Login success < 95%
-  - P95 latency > 500ms
-
-  Dashboard: https://monitoring.example.com/hotfix-${taskId}
-  `)
-
-  // Optional: Set up automated monitoring (if integrated)
-  Bash(`
-    ./scripts/monitor-deployment.sh \
-      --duration 15m \
-      --metrics error_rate,login_success,auth_latency \
-      --alert-threshold error_rate:5%,login_success:95% \
-      --rollback-on-threshold
+  Auto-rollback: Enabled
   `)
 }
 ```
 
-**Progress Tracking**: Mark Phase 6 completed, lite-execute continues
+**TodoWrite**: Mark Phase 6 completed
 
 ---
 
 ## Data Structures
 
 ### diagnosisContext
-
 ```javascript
 {
-  symptom: string,                      // Original bug description
-  error_message: string | null,         // Extracted error message
-  keywords: string[],                   // Search keywords
+  symptom: string,
+  error_message: string | null,
+  keywords: string[],
   root_cause: {
-    file: string,                       // File path
-    line_range: string,                 // e.g., "45-52"
-    issue: string,                      // Root cause description
-    introduced_by: string               // git blame info
+    file: string,
+    line_range: string,
+    issue: string,
+    introduced_by: string
   },
-  reproduction_steps: string[],         // How to reproduce
-  affected_scope: {
-    users: string,                      // Impact description
-    features: string[],                 // Affected features
-    data_risk: "none" | "low" | "medium" | "high"
-  }
+  reproduction_steps: string[],
+  affected_scope: {...}
 }
 ```
 
 ### impactContext
-
 ```javascript
 {
-  affected_users: {
-    count: string,
-    severity: "low" | "medium" | "high" | "critical",
-    workaround: string | null
-  },
-  affected_features: [{
-    feature: string,
-    criticality: "low" | "medium" | "high" | "critical",
-    degradation: "none" | "partial_failure" | "complete_failure"
-  }],
-  risk_score: number,                   // 0-10
+  affected_users: { count: string, severity: string },
+  system_risk: { availability: string, cascading_failures: string },
+  business_impact: { revenue: string, reputation: string, sla_breach: string },
+  risk_score: number,  // 0-10
   severity: "low" | "medium" | "high" | "critical"
 }
 ```
 
 ### fixPlan
-
 ```javascript
 {
-  strategy: "immediate_patch" | "comprehensive_refactor" | "surgical_fix",
-  summary: string,                      // 1-2 sentence overview
-  approach: string,                     // High-level strategy
+  strategy: string,
+  summary: string,
+  approach: string,
   tasks: [{
     title: string,
     file: string,
     action: "Update" | "Create" | "Delete",
-    description: string,
-    implementation: string[],            // Step-by-step
-    verification: string[]               // Test steps
+    implementation: string[],
+    verification: string[]
   }],
   estimated_time: string,
-  risk: "minimal" | "low" | "medium" | "high",
   recommended_execution: "Agent" | "CLI" | "Manual"
 }
 ```
 
-### executionContext
-
-Passed to lite-execute:
-
+### executionContext (passed to lite-execute)
 ```javascript
 {
   mode: "bugfix",
@@ -765,19 +498,10 @@ Passed to lite-execute:
   planObject: fixPlan,
   diagnosisContext: diagnosisContext,
   impactContext: impactContext,
-  verificationStrategy: {
-    type: "smoke_tests" | "focused_integration" | "comprehensive",
-    tests: string[] | string,
-    automation: string | null
-  },
-  branchStrategy: {
-    type: "hotfix_branch" | "feature_branch",
-    base: string,
-    name: string,
-    merge_target: string[]
-  },
-  executionMethod: "Agent" | "CLI" | "Manual",
-  monitoringLevel: "real-time" | "passive"
+  verificationStrategy: {...},
+  branchStrategy: {...},
+  executionMethod: string,
+  monitoringLevel: string
 }
 ```
 
@@ -785,13 +509,13 @@ Passed to lite-execute:
 
 ## Best Practices
 
-### 1. Severity Selection
+### Severity Selection Guide
 
 **Use Regular Mode when:**
 - Bug is not blocking critical functionality
-- Have time for comprehensive testing
+- Have time for comprehensive testing (2-4 hours)
 - Want to explore multiple fix strategies
-- Can afford 2-4 hour fix cycle
+- Can afford full test suite run
 
 **Use Critical Mode when:**
 - Bug affects significant user base (>20%)
@@ -804,228 +528,62 @@ Passed to lite-execute:
 - Revenue/reputation at immediate risk
 - SLA breach occurring
 - Need fix within 30 minutes
-- Issue is well-understood (skip exploration)
+- Issue is well-understood
 
-### 2. Branching Best Practices
+### Branching Best Practices
 
 **Hotfix Branching**:
 ```bash
-# Correct: Branch from production tag
+# ✅ Correct: Branch from production tag
 git checkout -b hotfix/fix-name v2.3.1
 
-# Wrong: Branch from main (may include unreleased code)
+# ❌ Wrong: Branch from main (unreleased code)
 git checkout -b hotfix/fix-name main
 ```
 
 **Merge Strategy**:
 ```bash
-# Hotfix merges to both main and production
+# Hotfix merges to both targets
 git checkout main && git merge hotfix/fix-name
 git checkout production && git merge hotfix/fix-name
 git tag v2.3.2
 ```
 
-### 3. Verification Strategies
+### Follow-up Task Management
 
-**Smoke Tests** (Hotfix):
-- Login flow
-- Critical user journey
-- Core API endpoints
-- Data integrity spot check
-
-**Focused Integration** (Critical):
-- All tests in affected module
-- Integration tests with dependencies
-- Regression tests for similar bugs
-
-**Comprehensive** (Regular):
-- Full test suite
-- Coverage delta check
-- Manual exploratory testing
-
-### 4. Follow-up Task Management
-
-**Always create follow-up tasks for hotfixes**:
+**Always create follow-up for hotfixes**:
 - ✅ Comprehensive fix (within 3 days)
 - ✅ Test coverage improvement
 - ✅ Monitoring/alerting enhancements
 - ✅ Documentation updates
 - ✅ Postmortem (if critical)
 
-**Track technical debt**:
-```javascript
-{
-  debt_type: "quick_hotfix",
-  paydown_by: "2024-10-30",
-  cost_of_delay: "Increased fragility in auth module"
-}
-```
-
 ---
 
 ## Error Handling
 
 | Error | Cause | Resolution |
 |-------|-------|------------|
-| Root cause not found | Insufficient search | Expand search scope or escalate to /workflow:plan |
-| Reproduction fails | Stale bug or environment issue | Verify environment, request updated reproduction steps |
-| Multiple potential causes | Complex interaction | Use /cli:discuss-plan for multi-model analysis |
-| Fix too complex for lite-fix | High-risk refactor needed | Suggest /workflow:plan --mode refactor |
-| Hotfix verification fails | Insufficient smoke tests | Add critical test case or downgrade to critical mode |
-| Branch conflict | Concurrent changes | Rebase or merge main, re-run diagnosis |
+| Root cause not found | Insufficient search | Expand search or escalate to /workflow:plan |
+| Reproduction fails | Stale bug or env issue | Verify environment, request updated steps |
+| Multiple causes | Complex interaction | Use /cli:discuss-plan for analysis |
+| Fix too complex | High-risk refactor | Suggest /workflow:plan --mode refactor |
+| Verification fails | Insufficient tests | Add test cases or adjust mode |
 
 ---
 
-## Examples
-
-### Example 1: Regular Bug Fix
-
-```bash
-/workflow:lite-fix "用户头像上传失败，返回413错误"
-```
-
-**Phase 1**: Diagnosis finds file size limit configuration issue
-**Phase 2**: Impact - affects 10% users, medium severity
-**Phase 3**: Two strategies - increase limit (quick) vs implement chunked upload (robust)
-**Phase 4**: User selects quick fix
-**Phase 5**: Confirmation - Agent execution, focused tests
-**Result**: Fix in 45 minutes, full test coverage
-
----
-
-### Example 2: Critical Production Bug
-
-```bash
-/workflow:lite-fix --critical "购物车结算时随机丢失商品"
-```
-
-**Phase 1**: Fast diagnosis - race condition in cart update
-**Phase 2**: Impact - 30% checkout failures, high revenue impact
-**Phase 3**: Single strategy - add pessimistic locking
-**Phase 4**: Smoke tests + manual verification
-**Phase 5**: User confirms, Codex execution
-**Result**: Fix in 30 minutes, deployed to staging first
-
----
-
-### Example 3: Production Hotfix
-
-```bash
-/workflow:lite-fix --hotfix --incident INC-2024-1015 "支付接口5xx错误，API密钥过期"
-```
-
-**Phase 1**: Minimal diagnosis (known issue - expired credentials)
-**Phase 2**: Impact - 100% payment failures, critical
-**Phase 3**: Single surgical fix - rotate API key
-**Phase 4**: Hotfix branch from v2.3.1 tag
-**Phase 5**: Deploy confirmation, real-time monitoring
-**Phase 6**: Follow-up tasks generated automatically
-**Result**: Fix in 15 minutes, monitoring for 15 minutes post-deploy
-
-**Follow-up Tasks**:
-```json
-[
-  {
-    "id": "FOLLOWUP-rotation-automation",
-    "title": "Automate API key rotation",
-    "due": "3 days"
-  },
-  {
-    "id": "FOLLOWUP-monitoring",
-    "title": "Add expiry monitoring alert",
-    "due": "1 week"
-  }
-]
-```
-
----
-
-### Example 4: Complex Bug Escalation
-
-```bash
-/workflow:lite-fix "性能下降，数据库查询超时"
-```
-
-**Phase 1**: Diagnosis reveals multiple N+1 queries and missing indexes
-**Phase 3**: Complexity assessment - too complex for lite-fix
-**Recommendation**:
-```
-⚠️ This bug requires comprehensive refactoring.
-
-Suggested workflow:
-1. Use /workflow:plan --performance-optimization "优化数据库查询性能"
-2. Or: Use /cli:discuss-plan --topic "Database performance issues"
-
-Lite-fix is designed for targeted fixes. This requires:
-- Multiple file changes
-- Schema migrations
-- Load testing verification
-
-Proceeding with lite-fix may result in incomplete fix.
-```
-
-**User Decision**: Escalate to /workflow:plan
-
----
-
-## Comparison with Other Commands
-
-| Command | Use Case | Time Budget | Test Coverage | Output |
-|---------|----------|-------------|---------------|--------|
-| `/workflow:lite-fix` | Bug fixes (regular to critical) | 15min - 4hrs | Smoke to full | In-memory + optional JSON |
-| `/workflow:lite-plan` | New features (simple to medium) | 1-6 hrs | Full suite | In-memory + optional JSON |
-| `/workflow:plan` | Complex features/refactors | 1-5 days | Comprehensive | Persistent session |
-| `/cli:mode:bug-diagnosis` | Analysis only (no fix) | 10-30 min | N/A | Diagnostic report |
-| `/cli:execute` | Direct implementation | Variable | Depends on prompt | Code changes |
-
----
-
-## Integration with Existing Workflows
-
-### Escalation Path
-
-```
-lite-fix → (too complex) → /workflow:plan --mode bugfix
-lite-fix → (needs discussion) → /cli:discuss-plan
-lite-fix → (needs perf analysis) → /workflow:plan --performance-optimization
-```
-
-### Complementary Commands
-
-**Before lite-fix**:
-```bash
-# Optional: Preliminary diagnosis
-/cli:mode:bug-diagnosis "describe issue"
-
-# Then proceed with fix
-/workflow:lite-fix "same issue description"
-```
-
-**After lite-fix**:
-```bash
-# Review fix quality
-/workflow:review --type security
-
-# Complete session (if session-based)
-/workflow:session:complete
-```
-
----
-
-## File Structure
-
-### Output Locations
+## Output Routing
 
 **Lite-fix directory**:
 ```
 .workflow/lite-fixes/
 ├── BUGFIX-2024-10-20T14-30-00.json          # Bug fix task JSON
-├── BUGFIX-2024-10-20T14-30-00-followup.json # Follow-up tasks (hotfix only)
-└── diagnosis-cache/                          # Cached diagnosis results
-    └── auth-token-expiration-hash.json
+├── BUGFIX-2024-10-20T14-30-00-followup.json # Follow-up tasks (hotfix)
+└── diagnosis-cache/                          # Cached diagnosis
+    └── auth-token-hash.json
 ```
 
-**Session-based** (if active session exists):
+**Session-based** (if active session):
 ```
 .workflow/active/WFS-feature/
 ├── .bugfixes/
@@ -1041,55 +599,38 @@ lite-fix → (needs perf analysis) → /workflow:plan --performance-optimization
 
 ### 1. Diagnosis Caching
 
-Speed up repeated diagnoses of similar issues:
-
+Speed up similar issues:
 ```javascript
-// Generate diagnosis cache key
 cache_key = hash(bug_keywords + recent_changes_hash)
 cache_path = `.workflow/lite-fixes/diagnosis-cache/${cache_key}.json`
 
-if (file_exists(cache_path) && cache_age < 1_week) {
-  diagnosis = Read(cache_path)
-  console.log("Using cached diagnosis (similar issue found)")
-} else {
-  diagnosis = performDiagnosis()
-  Write(cache_path, diagnosis)
+if (cache_exists && cache_age < 1_week) {
+  diagnosis = load_from_cache()
 }
 ```
 
-### 2. Automatic Severity Detection
-
-Auto-suggest severity flag based on keywords:
+### 2. Auto-Severity Detection
 
 ```javascript
 if (bug_description.includes("production|down|critical|outage")) {
   suggested_flag = "--critical"
-} else if (bug_description.includes("hotfix|urgent|5xx|incident")) {
+} else if (bug_description.includes("hotfix|urgent|incident")) {
   suggested_flag = "--hotfix"
 }
-
-if (suggested_flag && !user_provided_flag) {
-  console.log(`💡 Suggestion: Consider using ${suggested_flag} flag`)
-}
 ```
 
-### 3. Rollback Plan Generation
-
-Auto-generate rollback instructions for hotfixes:
+### 3. Rollback Plan (Hotfix)
 
 ```javascript
 rollback_plan = {
   method: "git_revert",
   commands: [
-    `git revert ${commit_sha}`,
-    `git push origin hotfix/${branch_name}`,
-    `# Re-deploy previous version v2.3.1`
+    "git revert ${commit_sha}",
+    "git push origin hotfix/${branch}",
+    "# Re-deploy v2.3.1"
   ],
-  estimated_time: "5 minutes",
-  risk: "low"
+  estimated_time: "5 minutes"
 }
-
-Write(`.workflow/lite-fixes/${taskId}-rollback.sh`, rollback_plan.commands.join('\n'))
 ```
 
 ---
@@ -1100,62 +641,67 @@ Write(`.workflow/lite-fixes/${taskId}-rollback.sh`, rollback_plan.commands.join(
 - `/cli:mode:bug-diagnosis` - Root cause analysis only
 - `/cli:mode:code-analysis` - Execution path tracing
 
-**Fix Execution Commands**:
+**Fix Execution**:
 - `/workflow:lite-execute --in-memory` - Execute fix plan (called by lite-fix)
-- `/cli:execute` - Direct fix implementation
-- `/cli:codex-execute` - Multi-stage fix with Codex
+- `/cli:execute` - Direct implementation
+- `/cli:codex-execute` - Multi-stage fix
 
 **Planning Commands**:
 - `/workflow:plan --mode bugfix` - Complex bug requiring comprehensive planning
-- `/workflow:plan --performance-optimization` - Performance-related bugs
-- `/cli:discuss-plan` - Multi-model collaborative analysis for unclear bugs
+- `/cli:discuss-plan` - Multi-model collaborative analysis
 
 **Review Commands**:
 - `/workflow:review --type quality` - Post-fix code review
-- `/workflow:review --type security` - Security validation after fix
-
-**Session Management**:
-- `/workflow:session:start` - Start tracked session for bug fixes
-- `/workflow:session:complete` - Complete bug fix session
+- `/workflow:review --type security` - Security validation
 
 ---
 
-## Governance & Best Practices
+## Comparison with Other Commands
 
-### When to Use lite-fix
+| Command | Use Case | Time | Output |
+|---------|----------|------|--------|
+| `/workflow:lite-fix` | Bug fixes (regular to critical) | 15min-4h | In-memory + JSON |
+| `/workflow:lite-plan` | New features | 1-6h | In-memory + JSON |
+| `/workflow:plan` | Complex features | 1-5 days | Persistent session |
+| `/cli:mode:bug-diagnosis` | Analysis only | 10-30min | Diagnostic report |
+
+---
+
+## Quality Gates
+
+**Before execution**:
+- [ ] Root cause identified (>80% confidence)
+- [ ] Impact scope clearly defined
+- [ ] Fix strategy reviewed and approved
+- [ ] Verification plan matches risk level
+- [ ] Branch strategy appropriate
+
+**Hotfix-specific**:
+- [ ] Incident ticket linked
+- [ ] Incident commander approval
+- [ ] Rollback plan documented
+- [ ] Follow-up tasks generated
+- [ ] Monitoring configured
+
+---
+
+## When to Use lite-fix
 
 ✅ **Good fit**:
-- Clear bug symptom with reproducible steps
+- Clear bug symptom with reproduction steps
 - Localized fix (1-3 files)
-- Established codebase with tests
 - Time-sensitive but not catastrophic
 - Known technology stack
 
 ❌ **Poor fit**:
-- Root cause unclear (use /cli:mode:bug-diagnosis first)
-- Requires architectural changes (use /workflow:plan)
-- No existing tests and complex legacy code (use /workflow:plan --legacy-refactor)
-- Performance investigation needed (use /workflow:plan --performance-optimization)
-- Data corruption/migration required (use /workflow:plan --data-migration)
-
-### Quality Gates
-
-**Before proceeding to execution**:
-- [ ] Root cause identified with >80% confidence
-- [ ] Impact scope clearly defined
-- [ ] Fix strategy reviewed and approved
-- [ ] Verification plan adequate for risk level
-- [ ] Branch strategy appropriate for severity
-
-**Hotfix-specific gates**:
-- [ ] Incident ticket created and linked
-- [ ] Incident commander approval obtained
-- [ ] Rollback plan documented
-- [ ] Follow-up tasks generated
-- [ ] Post-deployment monitoring configured
+- Root cause unclear → use `/cli:mode:bug-diagnosis` first
+- Requires architectural changes → use `/workflow:plan`
+- Complex legacy code → use `/workflow:plan --legacy-refactor`
+- Performance investigation → use `/workflow:plan --performance-optimization`
+- Data migration needed → use `/workflow:plan --data-migration`
 
 ---
 
 **Last Updated**: 2025-11-20
 **Version**: 1.0.0
-**Status**: Design Document (Implementation Pending)
+**Status**: Design Document