claude-code-workflow 7.2.10 → 7.2.11

package/.claude/skills/team-brainstorm/role-specs/ideator.md

@@ -1,71 +0,0 @@
----
-prefix: IDEA
-inner_loop: false
-delegates_to: []
-message_types:
-  success: ideas_ready
-  error: error
----
-
-# Ideator
-
-Multi-angle idea generator. Divergent thinking, concept exploration, and idea revision as the Generator in the Generator-Critic loop.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session folder | Task description (Session: line) | Yes |
-| Topic | <session>/.msg/meta.json | Yes |
-| Angles | <session>/.msg/meta.json | Yes |
-| GC Round | <session>/.msg/meta.json | Yes |
-| Previous critique | <session>/critiques/*.md | For revision tasks only |
-| Previous ideas | <session>/.msg/meta.json generated_ideas | No |
-
-1. Extract session path from task description (match "Session: <path>")
-2. Read .msg/meta.json for topic, angles, gc_round
-3. Detect task mode:
-
-| Condition | Mode |
-|-----------|------|
-| Task subject contains "revision" or "fix" | GC Revision |
-| Otherwise | Initial Generation |
-
-4. If GC Revision mode:
-   - Glob critique files from <session>/critiques/
-   - Read latest critique for revision context
-5. Read previous ideas from .msg/meta.json generated_ideas state
-
-## Phase 3: Idea Generation
-
-### Mode Router
-
-| Mode | Focus |
-|------|-------|
-| Initial Generation | Multi-angle divergent thinking, no prior critique |
-| GC Revision | Address HIGH/CRITICAL challenges from critique |
-
-**Initial Generation**:
-- For each angle, generate 3+ ideas
-- Each idea: title, description (2-3 sentences), key assumption, potential impact, implementation hint
-
-**GC Revision**:
-- Focus on HIGH/CRITICAL severity challenges from critique
-- Retain unchallenged ideas intact
-- Revise ideas with revision rationale
-- Replace unsalvageable ideas with new alternatives
-
-**Output**: Write to `<session>/ideas/idea-<num>.md`
-- Sections: Topic, Angles, Mode, [Revision Context if applicable], Ideas list, Summary
-
-## Phase 4: Self-Review
-
-| Check | Pass Criteria | Action on Failure |
-|-------|---------------|-------------------|
-| Minimum count | >= 6 (initial) or >= 3 (revision) | Generate additional ideas |
-| No duplicates | All titles unique | Replace duplicates |
-| Angle coverage | At least 1 idea per angle | Generate missing angle ideas |
-
-After passing checks, update shared state:
-- Append new ideas to .msg/meta.json generated_ideas
-- Each entry: id, title, round, revised flag

package/.claude/skills/team-brainstorm/role-specs/synthesizer.md

@@ -1,59 +0,0 @@
----
-prefix: SYNTH
-inner_loop: false
-delegates_to: []
-message_types:
-  success: synthesis_ready
-  error: error
----
-
-# Synthesizer
-
-Cross-idea integrator. Extracts themes from multiple ideas and challenge feedback, resolves conflicts, generates consolidated proposals.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Session folder | Task description (Session: line) | Yes |
-| All ideas | <session>/ideas/*.md files | Yes |
-| All critiques | <session>/critiques/*.md files | Yes |
-| GC rounds completed | <session>/.msg/meta.json gc_round | Yes |
-
-1. Extract session path from task description (match "Session: <path>")
-2. Glob all idea files from <session>/ideas/
-3. Glob all critique files from <session>/critiques/
-4. Read all idea and critique files for synthesis
-5. Read .msg/meta.json for context (topic, gc_round, generated_ideas, critique_insights)
-
-## Phase 3: Synthesis Execution
-
-| Step | Action |
-|------|--------|
-| 1. Theme Extraction | Identify common themes across ideas, rate strength (1-10), list supporting ideas |
-| 2. Conflict Resolution | Identify contradictory ideas, determine resolution approach, document rationale |
-| 3. Complementary Grouping | Group complementary ideas together |
-| 4. Gap Identification | Discover uncovered perspectives |
-| 5. Integrated Proposal | Generate 1-3 consolidated proposals |
-
-**Integrated Proposal Structure**:
-- Core concept description
-- Source ideas combined
-- Addressed challenges from critiques
-- Feasibility score (1-10), Innovation score (1-10)
-- Key benefits list, Remaining risks list
-
-**Output**: Write to `<session>/synthesis/synthesis-<num>.md`
-- Sections: Input summary, Extracted Themes, Conflict Resolution, Integrated Proposals, Coverage Analysis
-
-## Phase 4: Quality Check
-
-| Check | Pass Criteria | Action on Failure |
-|-------|---------------|-------------------|
-| Proposal count | >= 1 proposal | Generate at least one proposal |
-| Theme count | >= 2 themes | Look for more patterns |
-| Conflict resolution | All conflicts documented | Address unresolved conflicts |
-
-After passing checks, update shared state:
-- Set .msg/meta.json synthesis_themes
-- Each entry: name, strength, supporting_ideas

package/.claude/skills/team-frontend/role-specs/analyst.md

@@ -1,91 +0,0 @@
----
-prefix: ANALYZE
-inner_loop: false
-message_types:
-  success: analyze_ready
-  error: error
----
-
-# Requirements Analyst
-
-Analyze frontend requirements and retrieve industry design intelligence via ui-ux-pro-max skill. Produce design-intelligence.json and requirements.md for downstream consumption by architect and developer roles.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Industry context | Extracted from task description | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | No |
-
-1. Extract session path, industry type, and tech stack from task description
-2. Detect existing design system:
-
-| Signal | Detection Method |
-|--------|-----------------|
-| Token files | Glob `**/*token*.*` |
-| CSS files | Glob `**/*.css` |
-| Package.json | Read for framework dependencies |
-
-3. Detect tech stack from package.json:
-
-| Dependency | Stack |
-|------------|-------|
-| `next` | nextjs |
-| `react` | react |
-| `vue` | vue |
-| `svelte` | svelte |
-| `@shadcn/ui` | shadcn |
-| (none) | html-tailwind |
-
-4. Load .msg/meta.json for shared state
-
-## Phase 3: Design Intelligence Retrieval
-
-Retrieve design intelligence via ui-ux-pro-max skill integration.
-
-**Step 1: Invoke ui-ux-pro-max** (primary path):
-
-| Action | Invocation |
-|--------|------------|
-| Full design system | `Skill(skill="ui-ux-pro-max", args="<industry> <keywords> --design-system")` |
-| UX guidelines | `Skill(skill="ui-ux-pro-max", args="accessibility animation responsive --domain ux")` |
-| Tech stack guide | `Skill(skill="ui-ux-pro-max", args="<keywords> --stack <detected-stack>")` |
-
-**Step 2: Fallback** (if skill unavailable):
-- Generate design recommendations from LLM general knowledge
-- Log warning: `ui-ux-pro-max not installed. Install via: /plugin install ui-ux-pro-max@ui-ux-pro-max-skill`
-
-**Step 3: Analyze existing codebase** (if token/CSS files found):
-- Explore existing design patterns (color palette, typography scale, spacing, component patterns)
-
-**Step 4: Competitive reference** (optional, if industry is not "Other"):
-- `WebSearch({ query: "<industry> web design trends best practices" })`
-
-**Step 5: Compile design-intelligence.json**:
-
-| Field | Source |
-|-------|--------|
-| `_source` | "ui-ux-pro-max-skill" or "llm-general-knowledge" |
-| `industry` | Task description |
-| `detected_stack` | Phase 2 detection |
-| `design_system` | Skill output (colors, typography, effects) |
-| `ux_guidelines` | Skill UX domain output |
-| `stack_guidelines` | Skill stack output |
-| `recommendations` | Synthesized: style, anti-patterns, must-have |
-
-**Output files**:
-- `<session>/analysis/design-intelligence.json`
-- `<session>/analysis/requirements.md`
-
-## Phase 4: Self-Review
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| JSON validity | Parse design-intelligence.json | No parse errors |
-| Required fields | Check _source, industry, design_system | All present |
-| Anti-patterns populated | Check recommendations.anti_patterns | Non-empty array |
-| Requirements doc exists | File check | requirements.md written |
-
-Update .msg/meta.json: merge `design_intelligence` and `industry_context` keys.

package/.claude/skills/team-frontend/role-specs/architect.md

@@ -1,85 +0,0 @@
----
-prefix: ARCH
-inner_loop: false
-message_types:
-  success: arch_ready
-  error: error
----
-
-# Frontend Architect
-
-Consume design-intelligence.json to define design token system, component architecture, and project structure. Token values prioritize ui-ux-pro-max recommendations. Produce architecture artifacts for developer consumption.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Scope | Extracted from task description (tokens/components/full) | No (default: full) |
-| Design intelligence | <session>/analysis/design-intelligence.json | Yes |
-| .msg/meta.json | <session>/.msg/meta.json | No |
-
-1. Extract session path and scope from task description
-2. Load design intelligence from analyst output
-3. Load .msg/meta.json for shared state (industry_context, design_intelligence)
-4. Detect existing project structure via Glob `src/**/*`
-
-**Fail-safe**: If design-intelligence.json not found, use default token values and log warning.
-
-## Phase 3: Architecture Design
-
-**Scope selection**:
-
-| Scope | Output |
-|-------|--------|
-| `tokens` | Design token system only |
-| `components` | Component specs only |
-| `full` | Both tokens and components + project structure |
-
-**Step 1: Design Token System** (scope: tokens or full):
-
-Generate `<session>/architecture/design-tokens.json` with categories:
-
-| Category | Content | Source |
-|----------|---------|--------|
-| `color` | Primary, secondary, background, surface, text, CTA | ui-ux-pro-max |
-| `typography` | Font families, font sizes (scale) | ui-ux-pro-max |
-| `spacing` | xs through 2xl | Standard scale |
-| `border-radius` | sm, md, lg, full | Standard scale |
-| `shadow` | sm, md, lg | Standard elevation |
-| `transition` | fast, normal, slow | Standard durations |
-
-Use `$type` + `$value` format (Design Tokens Community Group). Support light/dark mode via nested values.
-
-**Step 2: Component Architecture** (scope: components or full):
-
-Generate component specs in `<session>/architecture/component-specs/`:
-- Design reference (style, stack)
-- Props table (name, type, default, description)
-- Variants table
-- Accessibility requirements (role, keyboard, ARIA, contrast)
-- Anti-patterns to avoid (from design intelligence)
-
-**Step 3: Project Structure** (scope: full):
-
-Generate `<session>/architecture/project-structure.md` with stack-specific layout:
-
-| Stack | Key Directories |
-|-------|----------------|
-| react | src/components/, src/pages/, src/hooks/, src/styles/ |
-| nextjs | app/(routes)/, app/components/, app/lib/, app/styles/ |
-| vue | src/components/, src/views/, src/composables/, src/styles/ |
-| html-tailwind | src/components/, src/pages/, src/styles/ |
-
-## Phase 4: Self-Review
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| JSON validity | Parse design-tokens.json | No errors |
-| Required categories | Check color, typography, spacing | All present |
-| Anti-pattern compliance | Token values vs anti-patterns | No violations |
-| Component specs complete | Each has props + accessibility | All complete |
-| File existence | Verify all planned files | All present |
-
-Update .msg/meta.json: merge `design_token_registry` and `component_inventory` keys.

package/.claude/skills/team-frontend/role-specs/developer.md

@@ -1,92 +0,0 @@
----
-prefix: DEV
-inner_loop: true
-message_types:
-  success: dev_complete
-  error: error
----
-
-# Frontend Developer
-
-Consume architecture artifacts (design tokens, component specs, project structure) to implement frontend code. Reference design-intelligence.json for implementation checklist, tech stack guidelines, and anti-pattern constraints.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Scope | Extracted from task description (tokens/components/full) | No (default: full) |
-| Design intelligence | <session>/analysis/design-intelligence.json | No |
-| Design tokens | <session>/architecture/design-tokens.json | Yes |
-| Component specs | <session>/architecture/component-specs/*.md | No |
-| Project structure | <session>/architecture/project-structure.md | No |
-| .msg/meta.json | <session>/.msg/meta.json | No |
-
-1. Extract session path and scope from task description
-2. Load design tokens (required -- if missing, report to coordinator)
-3. Load design intelligence for anti-patterns and guidelines
-4. Load component specs and project structure
-5. Detect tech stack from design intelligence `detected_stack`
-6. Load .msg/meta.json for shared state
-
-## Phase 3: Code Implementation
-
-**Scope selection**:
-
-| Scope | Output |
-|-------|--------|
-| `tokens` | CSS custom properties from design tokens |
-| `components` | Component code from specs |
-| `full` | Both token CSS and components |
-
-**Step 1: Generate Design Token CSS** (scope: tokens or full):
-
-Convert design-tokens.json to `src/styles/tokens.css`:
-
-| JSON Category | CSS Variable Prefix |
-|---------------|---------------------|
-| color | `--color-` |
-| typography.font-family | `--font-` |
-| typography.font-size | `--text-` |
-| spacing | `--space-` |
-| border-radius | `--radius-` |
-| shadow | `--shadow-` |
-| transition | `--duration-` |
-
-Add `@media (prefers-color-scheme: dark)` override for color tokens.
-
-**Step 2: Implement Components** (scope: components or full):
-
-Implementation strategy by complexity:
-
-| Condition | Strategy |
-|-----------|----------|
-| <= 2 components | Direct inline Edit/Write |
-| 3-5 components | Single batch implementation |
-| > 5 components | Group by module, implement per batch |
-
-**Coding standards** (mandatory):
-- Use design token CSS variables -- never hardcode colors/spacing
-- All interactive elements: `cursor: pointer`
-- Transitions: 150-300ms via `var(--duration-normal)`
-- Text contrast: minimum 4.5:1 ratio
-- Include `focus-visible` styles for keyboard navigation
-- Support `prefers-reduced-motion`
-- Responsive: mobile-first with md/lg breakpoints
-- No emoji as functional icons
-
-## Phase 4: Self-Review
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Hardcoded colors | Scan for hex codes outside tokens.css | None found |
-| cursor-pointer | Check buttons/links | All have cursor-pointer |
-| Focus styles | Check interactive elements | All have focus styles |
-| Responsive | Check for breakpoints | Breakpoints present |
-| File existence | Verify all planned files | All present |
-| Import resolution | Check no broken imports | All imports resolve |
-
-Auto-fix where possible: add missing cursor-pointer, basic focus styles.
-
-Update .msg/meta.json: merge `component_inventory` key with implemented file list.

package/.claude/skills/team-frontend/role-specs/qa.md

@@ -1,78 +0,0 @@
----
-prefix: QA
-inner_loop: false
-message_types:
-  success: qa_passed
-  error: error
----
-
-# QA Engineer
-
-Execute 5-dimension quality audit integrating ux-guidelines Do/Don't rules, pre-delivery checklist, and industry anti-pattern library. Perform CSS-level precise review on architecture artifacts and implementation code.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Review type | Extracted from task description | No (default: code-review) |
-| Design intelligence | <session>/analysis/design-intelligence.json | No |
-| Design tokens | <session>/architecture/design-tokens.json | No |
-| .msg/meta.json | <session>/.msg/meta.json | No |
-
-1. Extract session path and review type from task description
-2. Load design intelligence (for anti-patterns, must-have rules)
-3. Load design tokens (for compliance checks)
-4. Load .msg/meta.json (for industry context, strictness level)
-5. Collect files to review based on review type:
-
-| Type | Files to Review |
-|------|-----------------|
-| architecture-review | `<session>/architecture/**/*` |
-| token-review | `<session>/architecture/**/*` |
-| code-review | `src/**/*.{tsx,jsx,vue,svelte,html,css}` |
-| final | `src/**/*.{tsx,jsx,vue,svelte,html,css}` |
-
-## Phase 3: 5-Dimension Audit
-
-| Dimension | Weight | Focus |
-|-----------|--------|-------|
-| Code Quality | 0.20 | Structure, naming, maintainability |
-| Accessibility | 0.25 | WCAG compliance, keyboard nav, screen reader |
-| Design Compliance | 0.20 | Anti-pattern check, design token usage |
-| UX Best Practices | 0.20 | Interaction patterns, responsive, animations |
-| Pre-Delivery | 0.15 | Final checklist (code-review/final types only) |
-
-**Dimension 1 -- Code Quality**: File length (>300 LOC), console.log, empty catch, unused imports.
-
-**Dimension 2 -- Accessibility**: Image alt text, input labels, button text, heading hierarchy, focus styles, ARIA roles. Strict mode (medical/financial): prefers-reduced-motion required.
-
-**Dimension 3 -- Design Compliance**: Hardcoded colors (must use `var(--color-*)`), hardcoded spacing, industry anti-patterns from design intelligence.
-
-**Dimension 4 -- UX Best Practices**: cursor-pointer on clickable, transition 150-300ms, responsive design, loading states, error states.
-
-**Dimension 5 -- Pre-Delivery** (final/code-review only): No emoji icons, cursor-pointer, transitions, focus states, reduced-motion, responsive, no hardcoded colors, dark mode support.
-
-**Score calculation**: `score = sum(dimension_score * weight)`
-
-**Verdict**:
-
-| Condition | Verdict | Message Type |
-|-----------|---------|-------------|
-| score >= 8 AND critical == 0 | PASSED | `qa_passed` |
-| score >= 6 AND critical == 0 | PASSED_WITH_WARNINGS | `qa_result` |
-| score < 6 OR critical > 0 | FIX_REQUIRED | `fix_required` |
-
-## Phase 4: Self-Review
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| All dimensions scored | Check 5 dimension scores | All present |
-| Audit report written | File check | audit-NNN.md exists |
-| Verdict determined | Score calculated | Verdict assigned |
-| Issues categorized | Severity labels | All issues have severity |
-
-Write audit report to `<session>/qa/audit-<NNN>.md` with: summary, dimension scores, issues by severity, passed dimensions.
-
-Update .msg/meta.json: append to `qa_history` array.

package/.claude/skills/team-issue/role-specs/explorer.md

@@ -1,95 +0,0 @@
----
-prefix: EXPLORE
-inner_loop: false
-message_types:
-  success: context_ready
-  error: error
----
-
-# Issue Explorer
-
-Analyze issue context, explore codebase for relevant files, map dependencies and impact scope. Produce a shared context report for planner, reviewer, and implementer.
-
-## Phase 2: Issue Loading & Context Setup
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Issue ID | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
-| Issue details | `ccw issue status <id> --json` | Yes |
-| Session path | Extracted from task description | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract issue ID from task description via regex: `(?:GH-\d+|ISS-\d{8}-\d{6})`
-2. If no issue ID found -> report error, STOP
-3. Load issue details:
-
-```
-Bash("ccw issue status <issueId> --json")
-```
-
-4. Parse JSON response for issue metadata (title, context, priority, labels, feedback)
-5. Load wisdom files from `<session>/wisdom/` if available
-
-## Phase 3: Codebase Exploration & Impact Analysis
-
-**Complexity assessment determines exploration depth**:
-
-| Signal | Weight | Keywords |
-|--------|--------|----------|
-| Structural change | +2 | refactor, architect, restructure, module, system |
-| Cross-cutting | +2 | multiple, across, cross |
-| Integration | +1 | integrate, api, database |
-| High priority | +1 | priority >= 4 |
-
-| Score | Complexity | Strategy |
-|-------|------------|----------|
-| >= 4 | High | Deep exploration via CLI tool |
-| 2-3 | Medium | Hybrid: ACE search + selective CLI |
-| 0-1 | Low | Direct ACE search only |
-
-**Exploration execution**:
-
-| Complexity | Execution |
-|------------|-----------|
-| Low | Direct ACE search: `mcp__ace-tool__search_context(project_root_path, query)` |
-| Medium/High | CLI exploration: `Bash("ccw cli -p \"<exploration_prompt>\" --tool gemini --mode analysis", { run_in_background: false })` |
-
-**CLI exploration prompt template**:
-
-```
-PURPOSE: Explore codebase for issue <issueId> to identify relevant files, dependencies, and impact scope; success = comprehensive context report written to <session>/explorations/context-<issueId>.json
-
-TASK: • Run ccw tool exec get_modules_by_depth '{}' • Execute ACE searches for issue keywords • Map file dependencies and integration points • Assess impact scope • Find existing patterns • Check git log for related changes
-
-MODE: analysis
-
-CONTEXT: @**/* | Memory: Issue <issueId> - <issue.title> (Priority: <issue.priority>)
-
-EXPECTED: JSON report with: relevant_files (path + relevance), dependencies, impact_scope (low/medium/high), existing_patterns, related_changes, key_findings, complexity_assessment
-
-CONSTRAINTS: Focus on issue context | Write output to <session>/explorations/context-<issueId>.json
-```
-
-**Report schema**:
-
-```json
-{
-  "issue_id": "string",
-  "issue": { "id": "", "title": "", "priority": 0, "status": "", "labels": [], "feedback": "" },
-  "relevant_files": [{ "path": "", "relevance": "" }],
-  "dependencies": [],
-  "impact_scope": "low | medium | high",
-  "existing_patterns": [],
-  "related_changes": [],
-  "key_findings": [],
-  "complexity_assessment": "Low | Medium | High"
-}
-```
-
-## Phase 4: Context Report & Wisdom Contribution
-
-1. Write context report to `<session>/explorations/context-<issueId>.json`
-2. If file not found from agent, build minimal report from ACE results
-3. Update `<session>/wisdom/.msg/meta.json` under `explorer` namespace:
-   - Read existing -> merge `{ "explorer": { issue_id, complexity, impact_scope, file_count } }` -> write back
-4. Contribute discoveries to `<session>/wisdom/learnings.md` if new patterns found

package/.claude/skills/team-issue/role-specs/implementer.md

@@ -1,89 +0,0 @@
----
-prefix: BUILD
-inner_loop: false
-message_types:
-  success: impl_complete
-  failed: impl_failed
-  error: error
----
-
-# Issue Implementer
-
-Load solution plan, route to execution backend (Agent/Codex/Gemini), run tests, and commit. Execution method determined by coordinator during task creation. Supports parallel instances for batch mode.
-
-## Modes
-
-| Backend | Condition | Method |
-|---------|-----------|--------|
-| codex | task_count > 3 or explicit | `ccw cli --tool codex --mode write --id issue-<issueId>` |
-| gemini | task_count <= 3 or explicit | `ccw cli --tool gemini --mode write --id issue-<issueId>` |
-| qwen | explicit | `ccw cli --tool qwen --mode write --id issue-<issueId>` |
-
-## Phase 2: Load Solution & Resolve Executor
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Issue ID | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
-| Bound solution | `ccw issue solutions <id> --json` | Yes |
-| Explorer context | `<session>/explorations/context-<issueId>.json` | No |
-| Execution method | Task description (`execution_method: Codex|Gemini|Qwen|Auto`) | Yes |
-| Code review | Task description (`code_review: Skip|Gemini Review|Codex Review`) | No |
-
-1. Extract issue ID from task description
-2. If no issue ID -> report error, STOP
-3. Load bound solution: `Bash("ccw issue solutions <issueId> --json")`
-4. If no bound solution -> report error, STOP
-5. Load explorer context (if available)
-6. Resolve execution method (Auto: task_count <= 3 -> gemini, else codex)
-7. Update issue status: `Bash("ccw issue update <issueId> --status in-progress")`
-
-## Phase 3: Implementation (Multi-Backend Routing)
-
-**Execution prompt template** (all backends):
-
-```
-## Issue
-ID: <issueId>
-Title: <solution.bound.title>
-
-## Solution Plan
-<solution.bound JSON>
-
-## Codebase Context (from explorer)
-Relevant files: <explorerContext.relevant_files>
-Existing patterns: <explorerContext.existing_patterns>
-Dependencies: <explorerContext.dependencies>
-
-## Implementation Requirements
-1. Follow the solution plan tasks in order
-2. Write clean, minimal code following existing patterns
-3. Run tests after each significant change
-4. Ensure all existing tests still pass
-5. Do NOT over-engineer
-
-## Quality Checklist
-- All solution tasks implemented
-- No TypeScript/linting errors
-- Existing tests pass
-- New tests added where appropriate
-```
-
-Route by executor:
-- **codex**: `Bash("ccw cli -p \"<prompt>\" --tool codex --mode write --id issue-<issueId>", { run_in_background: false })`
-- **gemini**: `Bash("ccw cli -p \"<prompt>\" --tool gemini --mode write --id issue-<issueId>", { run_in_background: false })`
-- **qwen**: `Bash("ccw cli -p \"<prompt>\" --tool qwen --mode write --id issue-<issueId>", { run_in_background: false })`
-
-On CLI failure, resume: `ccw cli -p "Continue" --resume issue-<issueId> --tool <tool> --mode write`
-
-## Phase 4: Verify & Commit
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Tests pass | Detect and run test command | No new failures |
-| Code review | Optional, per task config | Review output logged |
-
-- Tests pass -> optional code review -> `ccw issue update <issueId> --status resolved` -> report `impl_complete`
-- Tests fail -> report `impl_failed` with truncated test output
-
-Update `<session>/wisdom/.msg/meta.json` under `implementer` namespace:
-- Read existing -> merge `{ "implementer": { issue_id, executor, test_status, review_status } }` -> write back