feat: Add roles for issue resolution pipeline including planner, reviewer, integrator, and implementer

- Implemented `planner` role for solution design and task decomposition using issue-plan-agent.
- Introduced `reviewer` role for solution review, technical feasibility validation, and risk assessment.
- Created `integrator` role for queue formation and conflict detection using issue-queue-agent.
- Added `implementer` role for code implementation and test verification via code-developer.
- Defined message types and role boundaries for each role to ensure clear responsibilities.
- Established a team configuration file to manage roles, pipelines, and collaboration patterns for the issue processing pipeline.

.claude/skills/workflow-lite-plan/SKILL.md

@@ -21,7 +21,7 @@ Unified lightweight planning and execution skill. Routes to lite-plan (planning
      ┌───────────┐           ┌───────────┐
      │ lite-plan │           │lite-execute│
      │ Phase 1   │           │ Phase 2    │
-     │ Plan+Exec │──handoff─→│ Standalone │
+     │ Plan+Exec │─direct──→│ Standalone │
      └───────────┘           └───────────┘
 ```
 
@@ -44,9 +44,65 @@ function detectMode() {
 | `workflow:lite-plan` | plan | [phases/01-lite-plan.md](phases/01-lite-plan.md) | Full planning pipeline (explore → plan → confirm → execute) |
 | `workflow:lite-execute` | execute | [phases/02-lite-execute.md](phases/02-lite-execute.md) | Standalone execution (in-memory / prompt / file) |
 
+## Interactive Preference Collection
+
+Before dispatching, collect workflow preferences via AskUserQuestion:
+
+```javascript
+if (mode === 'plan') {
+  const prefResponse = AskUserQuestion({
+    questions: [
+      {
+        question: "是否跳过所有确认步骤（自动模式）？",
+        header: "Auto Mode",
+        multiSelect: false,
+        options: [
+          { label: "Interactive (Recommended)", description: "交互模式，包含确认步骤" },
+          { label: "Auto", description: "跳过所有确认，自动执行" }
+        ]
+      },
+      {
+        question: "是否强制执行代码探索阶段？",
+        header: "Exploration",
+        multiSelect: false,
+        options: [
+          { label: "Auto-detect (Recommended)", description: "智能判断是否需要探索" },
+          { label: "Force explore", description: "强制执行代码探索" }
+        ]
+      }
+    ]
+  })
+  workflowPreferences = {
+    autoYes: prefResponse.autoMode === 'Auto',
+    forceExplore: prefResponse.exploration === 'Force explore'
+  }
+} else {
+  // Execute mode (standalone, not in-memory)
+  const prefResponse = AskUserQuestion({
+    questions: [
+      {
+        question: "是否跳过所有确认步骤（自动模式）？",
+        header: "Auto Mode",
+        multiSelect: false,
+        options: [
+          { label: "Interactive (Recommended)", description: "交互模式，包含确认步骤" },
+          { label: "Auto", description: "跳过所有确认，自动执行" }
+        ]
+      }
+    ]
+  })
+  workflowPreferences = {
+    autoYes: prefResponse.autoMode === 'Auto',
+    forceExplore: false
+  }
+}
+```
+
+**workflowPreferences** is passed to phase execution as context variable, referenced as `workflowPreferences.autoYes` and `workflowPreferences.forceExplore` within phases.
+
 ## Prompt Enhancement
 
-Before dispatching to the target phase, enhance context:
+After collecting preferences, enhance context and dispatch:
 
 ```javascript
 // Step 1: Check for project context files
@@ -61,7 +117,7 @@ if (hasProjectGuidelines) {
   console.log('Project guidelines available: .workflow/project-guidelines.json')
 }
 
-// Step 3: Dispatch to phase
+// Step 3: Dispatch to phase (workflowPreferences available as context)
 if (mode === 'plan') {
   // Read phases/01-lite-plan.md and execute
 } else {
@@ -71,20 +127,20 @@ if (mode === 'plan') {
 
 ## Execution Flow
 
-### Plan Mode (workflow:lite-plan)
+### Plan Mode
 
 ```
-1. Parse flags (-y/--yes, -e/--explore) and task description
+1. Collect preferences via AskUserQuestion (autoYes, forceExplore)
 2. Enhance prompt with project context availability
 3. Read phases/01-lite-plan.md
 4. Execute lite-plan pipeline (Phase 1-5 within the phase doc)
-5. lite-plan Phase 5 internally calls workflow:lite-execute via Skill handoff
+5. lite-plan Phase 5 directly reads and executes Phase 2 (lite-execute) with executionContext
 ```
 
-### Execute Mode (workflow:lite-execute)
+### Execute Mode
 
 ```
-1. Parse flags (--in-memory, -y/--yes) and input
+1. Collect preferences via AskUserQuestion (autoYes)
 2. Enhance prompt with project context availability
 3. Read phases/02-lite-execute.md
 4. Execute lite-execute pipeline (input detection → execution → review)
@@ -92,17 +148,10 @@ if (mode === 'plan') {
 
 ## Usage
 
-```bash
-# Plan mode
-/workflow:lite-plan "实现JWT认证"                    # Interactive
-/workflow:lite-plan --yes "实现JWT认证"              # Auto mode
-/workflow:lite-plan -y -e "优化数据库查询性能"       # Auto + force exploration
+Plan mode and execute mode are triggered by skill name routing (see Mode Detection). Workflow preferences (auto mode, force explore) are collected interactively via AskUserQuestion before dispatching to phases.
 
-# Execute mode (standalone)
-/workflow:lite-execute "Add unit tests for auth"     # Prompt description
-/workflow:lite-execute plan.json                     # File input
-/workflow:lite-execute --in-memory                   # Called by lite-plan internally
-```
+**Plan mode**: Task description provided as arguments → interactive preference collection → planning pipeline
+**Execute mode**: Task description, file path, or in-memory context → interactive preference collection → execution pipeline
 
 ## Phase Reference Documents