fix(dev-workflow): refactor backend selection to multiSelect mode

根据 PR review 反馈进行修复：

核心改动：
- Step 0: backend 选择改为 multiSelect 多选模式
- 三个独立选项：codex、claude、gemini（每个带详细说明）
- 简化任务分类：使用 type 字段（default|ui|quick-fix）替代复杂的 complexity 评级
- Backend 路由逻辑清晰：default→codex, ui→gemini, quick-fix→claude
- 用户限制优先：仅选 codex 时强制所有任务使用 codex

改进点：
- 移除 PR#61 的 complexity/simple/medium/complex 字段
- 移除 rationale 字段，简化为单一 type 维度
- 修正 UI 判定逻辑，改为每任务属性
- Fallback 策略：codex → claude → gemini（优先级清晰）
- 错误处理：type 缺失默认为 default

文件修改：
- dev-workflow/commands/dev.md: 添加 Step 0，更新路由逻辑
- dev-workflow/agents/dev-plan-generator.md: 简化任务分类
- dev-workflow/README.md: 更新文档和示例

Generated with SWE-Agent.ai

Co-Authored-By: SWE-Agent.ai <noreply@swe-agent.ai>

dev-workflow/README.md

@@ -9,44 +9,56 @@ A freshly designed lightweight development workflow with no legacy baggage, focu
 ```
 /dev trigger
   ↓
+AskUserQuestion (backend selection)
+  ↓
 AskUserQuestion (requirements clarification)
   ↓
-codeagent analysis (plan mode + UI auto-detection)
+codeagent analysis (plan mode + task typing + UI auto-detection)
   ↓
 dev-plan-generator (create dev doc)
   ↓
-codeagent concurrent development (intelligent backend selection)
+codeagent concurrent development (2–5 tasks, backend routing)
   ↓
 codeagent testing & verification (≥90% coverage)
   ↓
 Done (generate summary)
 ```
 
-## The 6 Steps
+## Step 0 + The 6 Steps
+
+### 0. Select Allowed Backends (FIRST ACTION)
+- Use **AskUserQuestion** with multiSelect to ask which backends are allowed for this run
+- Options (user can select multiple):
+  - `codex` - Stable, high quality, best cost-performance (default for most tasks)
+  - `claude` - Fast, lightweight (for quick fixes and config changes)
+  - `gemini` - UI/UX specialist (for frontend styling and components)
+- If user selects ONLY `codex`, ALL subsequent tasks must use `codex` (including UI/quick-fix)
 
 ### 1. Clarify Requirements
 - Use **AskUserQuestion** to ask the user directly
 - No scoring system, no complex logic
 - 2–3 rounds of Q&A until the requirement is clear
 
-### 2. codeagent Analysis & UI Detection
+### 2. codeagent Analysis + Task Typing + UI Detection
 - Call codeagent to analyze the request in plan mode style
-- Extract: core functions, technical points, task list with complexity ratings
+- Extract: core functions, technical points, task list (2–5 items)
+- For each task, assign exactly one type: `default` / `ui` / `quick-fix`
 - UI auto-detection: needs UI work when task involves style assets (.css, .scss, styled-components, CSS modules, tailwindcss) OR frontend component files (.tsx, .jsx, .vue); output yes/no plus evidence
 
 ### 3. Generate Dev Doc
 - Call the **dev-plan-generator** agent
 - Produce a single `dev-plan.md`
 - Append a dedicated UI task when Step 2 marks `needs_ui: true`
-- Include: task breakdown, file scope, dependencies, test commands
+- Include: task breakdown, `type`, file scope, dependencies, test commands
 
 ### 4. Concurrent Development
 - Work from the task list in dev-plan.md
-- Use codeagent per task with intelligent backend selection:
-  - Simple/Medium tasks → `--backend claude` (fast, cost-effective)
-  - Complex tasks → `--backend codex` (deep reasoning)
-  - UI tasks → `--backend gemini` (enforced)
-- Backend selected automatically based on task complexity rating
+- Route backend per task type (with user constraints + fallback):
+  - `default` → `codex`
+  - `ui` → `gemini` (enforced when allowed)
+  - `quick-fix` → `claude`
+  - Missing `type` → treat as `default`
+  - If the preferred backend is not allowed, fallback to an allowed backend by priority: `codex` → `claude` → `gemini`
 - Independent tasks → run in parallel
 - Conflicting tasks → run serially
 
@@ -67,7 +79,7 @@ Done (generate summary)
 /dev "Implement user login with email + password"
 ```
 
-**No options**, fixed workflow, works out of the box.
+No CLI flags required; workflow starts with an interactive backend selection.
 
 ## Output Structure
 
@@ -82,17 +94,14 @@ Only one file—minimal and clear.
 
 ### Tools
 - **AskUserQuestion**: interactive requirement clarification
-- **codeagent skill**: analysis, development, testing; supports `--backend` for claude/codex/gemini
-- **dev-plan-generator agent**: generate dev doc with complexity ratings (subagent via Task tool, saves context)
+- **codeagent skill**: analysis, development, testing; supports `--backend` for `codex` / `claude` / `gemini`
+- **dev-plan-generator agent**: generate dev doc (subagent via Task tool, saves context)
 
-## Intelligent Backend Selection
-- **Complexity-based routing**: Tasks are rated as simple/medium/complex based on functional requirements (NOT code volume)
-  - Simple: Follows existing patterns, deterministic logic → claude
-  - Medium: Requires design decisions, multiple scenarios → claude
-  - Complex: Architecture design, algorithms, deep domain knowledge → codex
-  - UI: Style/component work → gemini (enforced)
-- **Flow impact**: Step 2 analyzes complexity; Step 3 includes complexity ratings in dev-plan.md; Step 4 auto-selects backend
-- **Implementation**: Orchestrator reads complexity field and invokes codeagent skill with appropriate backend parameter
+## Backend Selection & Routing
+- **Step 0**: user selects allowed backends; if `仅 codex`, all tasks use codex
+- **UI detection standard**: style files (.css, .scss, styled-components, CSS modules, tailwindcss) OR frontend component code (.tsx, .jsx, .vue) trigger `needs_ui: true`
+- **Task type field**: each task in `dev-plan.md` must have `type: default|ui|quick-fix`
+- **Routing**: `default`→codex, `ui`→gemini, `quick-fix`→claude; if disallowed, fallback to an allowed backend by priority: codex→claude→gemini
 
 ## Key Features
 
@@ -122,6 +131,10 @@ Only one file—minimal and clear.
 # Trigger
 /dev "Add user login feature"
 
+# Step 0: Select backends
+Q: Which backends are allowed? (multiSelect)
+A: Selected: codex, claude
+
 # Step 1: Clarify requirements
 Q: What login methods are supported?
 A: Email + password
@@ -131,18 +144,18 @@ A: Yes, use JWT token
 # Step 2: codeagent analysis
 Output:
 - Core: email/password login + JWT auth
-- Task 1: Backend API (complexity: medium)
-- Task 2: Password hashing (complexity: simple)
-- Task 3: Frontend form (complexity: simple)
+- Task 1: Backend API (type=default)
+- Task 2: Password hashing (type=default)
+- Task 3: Frontend form (type=ui)
 UI detection: needs_ui = true (tailwindcss classes in frontend form)
 
 # Step 3: Generate doc
-dev-plan.md generated with complexity ratings ✓
+dev-plan.md generated with typed tasks ✓
 
-# Step 4-5: Concurrent development (intelligent backend selection)
-[task-1] Backend API (claude, medium) → tests → 92% ✓
-[task-2] Password hashing (claude, simple) → tests → 95% ✓
-[task-3] Frontend form (gemini, UI) → tests → 91% ✓
+# Step 4-5: Concurrent development (routing + fallback)
+[task-1] Backend API (codex) → tests → 92% ✓
+[task-2] Password hashing (codex) → tests → 95% ✓
+[task-3] Frontend form (fallback to codex; gemini not allowed) → tests → 91% ✓
 ```
 
 ## Directory Structure