feat: add spec-setup command for project initialization and interactive configuration

- Introduced a new command `spec-setup` to initialize project-level state.
- Generates `.workflow/project-tech.json` and `.ccw/specs/*.md` files.
- Implements a multi-round interactive questionnaire for configuring project guidelines.
- Supports flags for regeneration, skipping specs, and resetting existing content.
- Integrates analysis via `cli-explore-agent` for comprehensive project understanding.
- Provides detailed execution process and error handling for various scenarios.

Author: catlog22

.claude/commands/ccw-coordinator.md

@@ -923,8 +923,9 @@ Task: <description>
 **Cycle Workflows**: workflow:integration-test-cycle, workflow:refactor-cycle
 **Execution**: workflow:unified-execute-with-file
 **Design**: workflow:ui-design:*
-**Session Management**: workflow:session:start, workflow:session:resume, workflow:session:complete, workflow:session:solidify, workflow:session:list, workflow:session:sync
-**Utility**: workflow:clean, workflow:init, workflow:init-guidelines, workflow:status
+**Session Management**: workflow:session:start, workflow:session:resume, workflow:session:complete, workflow:session:list, workflow:session:sync
+**Utility**: workflow:clean, workflow:spec:setup, workflow:status
+**Spec Management**: workflow:spec:setup, workflow:spec:add
 **Issue Workflow**: issue:discover, issue:discover-by-prompt, issue:plan, issue:queue, issue:execute, issue:convert-to-plan, issue:from-brainstorm, issue:new
 
 ### Testing Commands Distinction

.claude/commands/ccw.md

@@ -760,8 +760,8 @@ todos = [
 |---------|---------|
 | `workflow:unified-execute-with-file` | Universal execution engine - consumes plan output from collaborative-plan, roadmap, brainstorm |
 | `workflow:clean` | Intelligent code cleanup - mainline detection, stale artifact removal |
-| `workflow:init` | Initialize `.workflow/project-tech.json` with project analysis |
-| `workflow:init-guidelines` | Interactive wizard to fill `specs/*.md` |
+| `workflow:spec:setup` | Initialize `.workflow/project-tech.json` with project analysis and specs scaffold |
+| `workflow:spec:add` | Interactive wizard to add individual specs with scope selection |
 | `workflow:status` | Generate on-demand views for project overview and workflow tasks |
 
 ---
@@ -817,7 +817,7 @@ todos = [
 # Utility commands (invoked directly, not auto-routed)
 # /workflow:unified-execute-with-file          # 通用执行引擎（消费 plan 输出）
 # /workflow:clean                              # 智能代码清理
-# /workflow:init                               # 初始化项目状态
-# /workflow:init-guidelines                    # 交互式填充项目规范
+# /workflow:spec:setup                         # 初始化项目状态
+# /workflow:spec:add                           # 交互式填充项目规范
 # /workflow:status                             # 项目概览和工作流状态
 ```

.claude/commands/flow-create.md

@@ -93,7 +93,7 @@ async function selectCommandCategory() {
         { label: "Brainstorm", description: "brainstorm-with-file, brainstorm (unified skill)" },
         { label: "Analysis", description: "analyze-with-file" },
         { label: "Issue", description: "discover, plan, queue, execute, from-brainstorm, convert-to-plan" },
-        { label: "Utility", description: "clean, init, replan, status" }
+        { label: "Utility", description: "clean, spec:setup, spec:add, replan, status" }
       ],
       multiSelect: false
     }]
@@ -153,7 +153,7 @@ async function selectCommand(category) {
     ],
     'Utility': [
       { label: "/workflow:clean", description: "Intelligent code cleanup" },
-      { label: "/workflow:init", description: "Initialize project-level state" },
+      { label: "/workflow:spec:setup", description: "Initialize project-level state" },
       { label: "/workflow:replan", description: "Interactive workflow replanning" },
       { label: "/workflow:status", description: "Generate workflow status views" }
     ]

.claude/commands/workflow/analyze-with-file.md

@@ -65,6 +65,14 @@ When `--yes` or `-y`: Auto-confirm exploration decisions, use recommended analys
 
 ## Implementation
 
+### AskUserQuestion Constraints
+
+All `AskUserQuestion` calls MUST comply:
+- **questions**: 1-4 questions per call
+- **options**: 2-4 per question (system auto-adds "Other" for free-text input)
+- **header**: max 12 characters
+- **label**: 1-5 words per option
+
 ### Session Initialization
 
 1. Extract topic/question from `$ARGUMENTS`
@@ -79,10 +87,10 @@ When `--yes` or `-y`: Auto-confirm exploration decisions, use recommended analys
 ### Phase 1: Topic Understanding
 
 1. **Parse Topic & Identify Dimensions** — Match keywords against Analysis Dimensions table
-2. **Initial Scoping** (if new session + not auto mode):
-   - **Focus**: Multi-select from Dimension-Direction Mapping directions
-   - **Perspectives**: Multi-select up to 4 (see Analysis Perspectives), default: single comprehensive
-   - **Depth**: Quick Overview (10-15min) / Standard (30-60min) / Deep Dive (1-2hr)
+2. **Initial Scoping** (if new session + not auto mode) — use **single AskUserQuestion call with up to 3 questions**:
+   - Q1 **Focus** (multiSelect: true, header: "分析方向"): Top 3-4 directions from Dimension-Direction Mapping (options max 4)
+   - Q2 **Perspectives** (multiSelect: true, header: "分析视角"): Up to 4 from Analysis Perspectives table (options max 4), default: single comprehensive
+   - Q3 **Depth** (multiSelect: false, header: "分析深度"): Quick Overview / Standard / Deep Dive (3 options)
 3. **Initialize discussion.md** — Structure includes:
    - **Dynamic TOC** (top of file, updated after each round/phase): `## Table of Contents` with links to major sections
    - **Current Understanding** (replaceable block, overwritten each round — NOT appended): `## Current Understanding` initialized as "To be populated after exploration"
@@ -223,31 +231,26 @@ CONSTRAINTS: Focus on ${dimensions.join(', ')}
 
 2. **Present Findings** from explorations.json
 
-3. **Gather Feedback** (AskUserQuestion, single-select):
-   - **同意，继续深入**: Direction correct, deepen
-   - **同意，并建议下一步**: Agree with direction, but user has specific next step in mind
-   - **需要调整方向**: Different focus
+3. **Gather Feedback** (AskUserQuestion, single-select, header: "分析反馈"):
+   - **继续深入**: Direction correct — deepen automatically or user specifies direction (combines agree+deepen and agree+suggest)
+   - **调整方向**: Different focus or specific questions to address
+   - **补充信息**: User has additional context, constraints, or corrections to provide
    - **分析完成**: Sufficient → exit to Phase 4
-   - **有具体问题**: Specific questions
 
 4. **Process Response** (always record user choice + impact to discussion.md):
 
-   **Agree, Deepen** → Dynamically generate deepen directions from current analysis context:
-   - Extract 2-3 context-driven options from: unresolved questions in explorations.json, low-confidence findings, unexplored dimensions, user-highlighted areas
-   - Generate 1-2 heuristic options that break current frame: e.g., "compare with best practices in [related domain]", "analyze under extreme load scenarios", "review from security audit perspective", "explore simpler architectural alternatives"
-   - Each option specifies: label, description, tool (cli-explore-agent for code-level / Gemini CLI for pattern-level), scope
-   - AskUserQuestion with generated options (single-select)
-   - Execute selected direction via corresponding tool
-   - Merge new code_anchors/call_chains into existing results
-   - Record confirmed assumptions + deepen angle
-
-   **Agree, Suggest Next Step** → AskUserQuestion (free text: "请描述您希望下一步深入的方向") → Execute user's specific direction via cli-explore-agent or CLI → Record user-driven exploration rationale
+   **继续深入** → Sub-question to choose direction (AskUserQuestion, single-select, header: "深入方向"):
+   - Dynamically generate **max 3** context-driven options from: unresolved questions, low-confidence findings, unexplored dimensions, user-highlighted areas
+   - Add **1** heuristic option that breaks current frame (e.g., "compare with best practices", "review from security perspective", "explore simpler alternatives")
+   - Total: **max 4 options**. Each specifies: label, description, tool (cli-explore-agent for code-level / Gemini CLI for pattern-level), scope
+   - **"Other" is auto-provided** by AskUserQuestion — covers user-specified custom direction (no need for separate "suggest next step" option)
+   - Execute selected direction → merge new code_anchors/call_chains → record confirmed assumptions + deepen angle
 
-   **Adjust Direction** → AskUserQuestion for new focus → new CLI exploration → Record Decision (old vs new direction, reason, impact)
+   **调整方向** → AskUserQuestion (header: "新方向", user selects or provides custom via "Other") → new CLI exploration → Record Decision (old vs new direction, reason, impact)
 
-   **Specific Questions** → Capture, answer via CLI/analysis, document Q&A → Record gaps revealed + new understanding
+   **补充信息** → Capture user input, integrate into context, answer questions via CLI/analysis if needed → Record corrections/additions + updated understanding
 
-   **Complete** → Exit loop → Record why concluding
+   **分析完成** → Exit loop → Record why concluding
 
 5. **Update discussion.md**:
    - **Append** Round N: user input, direction adjustment, Q&A, corrections, new insights
@@ -319,11 +322,11 @@ CONSTRAINTS: Focus on ${dimensions.join(', ')}
    ```
    For each recommendation (ordered by priority high→medium→low):
      1. Present: action, rationale, priority, steps[] (numbered sub-steps)
-     2. AskUserQuestion (single-select, header: "Rec #N"):
-        - **确认**: Accept as-is → review_status = "accepted"
-        - **修改**: User adjusts scope/steps → record modification → review_status = "modified"
-        - **删除**: Not needed → record reason → review_status = "rejected"
-        - **跳过逐条审议**: Accept all remaining as-is → break loop
+     2. AskUserQuestion (single-select, header: "建议#N"):
+        - **确认** (label: "确认", desc: "Accept as-is") → review_status = "accepted"
+        - **修改** (label: "修改", desc: "Adjust scope/steps") → record modification → review_status = "modified"
+        - **删除** (label: "删除", desc: "Not needed") → record reason → review_status = "rejected"
+        - **跳过审议** (label: "跳过审议", desc: "Accept all remaining") → break loop
      3. Record review decision to discussion.md Decision Log
      4. Update conclusions.json recommendation.review_status
    ```

.claude/commands/workflow/collaborative-plan-with-file.md

@@ -587,7 +587,11 @@ Schema (tasks): ~/.ccw/workflows/cli-templates/schemas/task-schema.json
    - Execution command
    - Conflict status
 
-6. **Update Todo**
+6. **Sync Session State**
+   - Execute: `/workflow:session:sync -y "Plan complete: ${subDomains.length} domains, ${allTasks.length} tasks"`
+   - Updates specs/*.md with planning insights and project-tech.json with planning session entry
+
+7. **Update Todo**
    - Set Phase 4 status to `completed`
 
 **plan.md Structure**: