diff --git a/GETTING_STARTED.md b/GETTING_STARTED.md
index 3f1a7d85..4ce2e774 100644
--- a/GETTING_STARTED.md
+++ b/GETTING_STARTED.md
@@ -138,7 +138,69 @@ For complex features requiring thorough analysis, use the complete workflow: **b
 - Architectural decisions with significant impact
 - When you need thorough requirements before implementation
 
-### Scenario 4: Bug Fixing
+### Scenario 4: Quality Assurance - Concept Clarification
+
+Before generating tasks, ensure your requirements are clear and unambiguous:
+
+```bash
+# After brainstorming synthesis or planning analysis, verify conceptual clarity
+/workflow:concept-clarify
+
+# The command will:
+# 1. Analyze artifacts for ambiguities and missing details
+# 2. Ask up to 5 targeted questions to resolve critical gaps
+# 3. Update synthesis-specification.md or ANALYSIS_RESULTS.md with clarifications
+# 4. Recommend whether to proceed or address outstanding issues
+```
+
+**When to Use**:
+- After `/workflow:brainstorm:synthesis` (before `/workflow:plan`)
+- After Phase 3 of `/workflow:plan` (before task generation)
+- When you want to reduce planning errors and rework
+
+**Benefits**:
+- Detects underspecified requirements early
+- Prevents downstream implementation errors
+- Ensures team alignment on critical decisions
+- Reduces costly rework during execution
+
+### Scenario 5: Quality Assurance - Action Plan Verification
+
+After planning, validate your implementation plan for consistency and completeness:
+
+```bash
+# After /workflow:plan completes, verify task quality
+/workflow:action-plan-verify
+
+# The command will:
+# 1. Check requirements coverage (all requirements have tasks)
+# 2. Validate task dependencies (no circular or broken dependencies)
+# 3. Ensure synthesis alignment (tasks match architectural decisions)
+# 4. Assess task specification quality
+# 5. Generate detailed verification report with remediation todos
+```
+
+**The verification report includes**:
+- Requirements coverage analysis
+- Dependency graph validation
+- Synthesis alignment checks
+- Task specification quality assessment
+- Prioritized remediation recommendations
+
+**When to Use**:
+- After `/workflow:plan` generates IMPL_PLAN.md and task files
+- Before starting `/workflow:execute`
+- When working on complex projects with many dependencies
+- When you want to ensure high-quality task specifications
+
+**Benefits**:
+- Catches planning errors before execution
+- Ensures complete requirements coverage
+- Validates architectural consistency
+- Identifies resource conflicts and skill gaps
+- Provides actionable remediation plan with TodoWrite integration
+
+### Scenario 6: Bug Fixing
 
 Quick bug analysis and fix workflow:
 
diff --git a/GETTING_STARTED_CN.md b/GETTING_STARTED_CN.md
index 9c7d5b06..63166d8e 100644
--- a/GETTING_STARTED_CN.md
+++ b/GETTING_STARTED_CN.md
@@ -138,7 +138,69 @@
 - 具有重大影响的架构决策
 - 实现前需要详尽需求分析
 
-### 场景 4：Bug 修复
+### 场景 4：质量保证 - 概念澄清
+
+在生成任务之前，确保您的需求清晰且无歧义：
+
+```bash
+# 在头脑风暴综合或规划分析后，验证概念清晰度
+/workflow:concept-clarify
+
+# 该命令将：
+# 1. 分析工件中的歧义和缺失细节
+# 2. 提出最多 5 个针对性问题以解决关键差距
+# 3. 使用澄清更新 synthesis-specification.md 或 ANALYSIS_RESULTS.md
+# 4. 建议是继续进行还是解决未完成的问题
+```
+
+**使用时机**：
+- 在 `/workflow:brainstorm:synthesis` 之后（在 `/workflow:plan` 之前）
+- 在 `/workflow:plan` 的第 3 阶段之后（在任务生成之前）
+- 当您想减少规划错误和返工时
+
+**优势**：
+- 及早检测未明确的需求
+- 防止下游实现错误
+- 确保团队在关键决策上保持一致
+- 减少执行期间的昂贵返工
+
+### 场景 5：质量保证 - 行动计划验证
+
+规划后，验证您的实现计划的一致性和完整性：
+
+```bash
+# /workflow:plan 完成后，验证任务质量
+/workflow:action-plan-verify
+
+# 该命令将：
+# 1. 检查需求覆盖率（所有需求都有任务）
+# 2. 验证任务依赖关系（无循环或损坏的依赖）
+# 3. 确保综合对齐（任务符合架构决策）
+# 4. 评估任务规范质量
+# 5. 生成详细的验证报告和修复待办事项
+```
+
+**验证报告包括**：
+- 需求覆盖率分析
+- 依赖关系图验证
+- 综合对齐检查
+- 任务规范质量评估
+- 优先级修复建议
+
+**使用时机**：
+- 在 `/workflow:plan` 生成 IMPL_PLAN.md 和任务文件后
+- 在开始 `/workflow:execute` 之前
+- 处理具有许多依赖关系的复杂项目时
+- 当您想确保高质量的任务规范时
+
+**优势**：
+- 在执行前捕获规划错误
+- 确保完整的需求覆盖
+- 验证架构一致性
+- 识别资源冲突和技能差距
+- 提供可执行的修复计划，集成 TodoWrite
+
+### 场景 6：Bug 修复
 
 快速 Bug 分析和修复工作流：