claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-frontend-debug/schemas/tasks-schema.md

@@ -1,198 +0,0 @@
-# Team Frontend Debug -- CSV Schema
-
-## Master CSV: tasks.csv
-
-### Column Definitions
-
-#### Input Columns (Set by Decomposer)
-
-| Column | Type | Required | Description | Example |
-|--------|------|----------|-------------|---------|
-| `id` | string | Yes | Unique task identifier (PREFIX-NNN) | `"TEST-001"` |
-| `title` | string | Yes | Short task title | `"Feature testing"` |
-| `description` | string | Yes | Detailed task description (self-contained) with PURPOSE/TASK/CONTEXT/EXPECTED/CONSTRAINTS | `"PURPOSE: Test all features from list..."` |
-| `role` | enum | Yes | Worker role: `tester`, `reproducer`, `analyzer`, `fixer`, `verifier` | `"tester"` |
-| `pipeline_mode` | enum | Yes | Pipeline mode: `test-pipeline` or `debug-pipeline` | `"test-pipeline"` |
-| `base_url` | string | No | Target URL for browser-based tasks | `"http://localhost:3000"` |
-| `evidence_dimensions` | string | No | Semicolon-separated evidence types to collect | `"screenshot;console;network"` |
-| `deps` | string | No | Semicolon-separated dependency task IDs | `"TEST-001"` |
-| `context_from` | string | No | Semicolon-separated task IDs for context | `"TEST-001"` |
-| `exec_mode` | enum | Yes | Execution mechanism: `csv-wave` or `interactive` | `"csv-wave"` |
-
-#### Computed Columns (Set by Wave Engine)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `wave` | integer | Wave number (1-based, from topological sort) | `2` |
-| `prev_context` | string | Aggregated findings from context_from tasks (per-wave CSV only) | `"[TEST-001] Found 3 issues: 2 high, 1 medium..."` |
-
-#### Output Columns (Set by Agent)
-
-| Column | Type | Description | Example |
-|--------|------|-------------|---------|
-| `status` | enum | `pending` -> `completed` / `failed` / `skipped` | `"completed"` |
-| `findings` | string | Key discoveries (max 500 chars) | `"Tested 5 features: 3 pass, 2 fail. BUG-001: TypeError on login. BUG-002: API 500 on save."` |
-| `artifacts_produced` | string | Semicolon-separated paths of produced artifacts | `"artifacts/TEST-001-report.md;artifacts/TEST-001-issues.json"` |
-| `issues_count` | string | Number of issues found (tester/analyzer only, empty for others) | `"2"` |
-| `verdict` | string | Verification verdict: `pass`, `pass_with_warnings`, `fail` (verifier only) | `"pass"` |
-| `error` | string | Error message if failed | `""` |
-
----
-
-### exec_mode Values
-
-| Value | Mechanism | Description |
-|-------|-----------|-------------|
-| `csv-wave` | `spawn_agents_on_csv` | One-shot batch execution within wave |
-| `interactive` | `spawn_agent`/`wait`/`send_input`/`close_agent` | Multi-round individual execution |
-
-Interactive tasks appear in master CSV for dependency tracking but are NOT included in wave-{N}.csv files.
-
----
-
-### Role Prefixes
-
-| Role | Prefix | Pipeline | Inner Loop |
-|------|--------|----------|------------|
-| tester | TEST | test-pipeline | Yes (iterates over features) |
-| reproducer | REPRODUCE | debug-pipeline | No |
-| analyzer | ANALYZE | both | No |
-| fixer | FIX | both | Yes (may need multiple fix passes) |
-| verifier | VERIFY | both | No |
-
----
-
-### Example Data (Test Pipeline)
-
-```csv
-id,title,description,role,pipeline_mode,base_url,evidence_dimensions,deps,context_from,exec_mode,wave,status,findings,artifacts_produced,issues_count,verdict,error
-"TEST-001","Feature testing","PURPOSE: Test all features from feature list and discover issues | Success: All features tested with pass/fail results\nTASK:\n- Parse feature list\n- Navigate to each feature URL using Chrome DevTools\n- Execute test scenarios (click, fill, hover)\n- Capture evidence: screenshots, console logs, network requests\n- Classify results: pass/fail/warning\nCONTEXT:\n- Session: .workflow/.csv-wave/tfd-login-test-20260308\n- Base URL: http://localhost:3000\n- Features: Login, Dashboard, Profile\nEXPECTED: artifacts/TEST-001-report.md + artifacts/TEST-001-issues.json\nCONSTRAINTS: Chrome DevTools MCP only | No code modifications","tester","test-pipeline","http://localhost:3000","screenshot;console;network","","","csv-wave","1","pending","","","","",""
-"ANALYZE-001","Root cause analysis","PURPOSE: Analyze discovered issues to identify root causes | Success: RCA for each high/medium issue\nTASK:\n- Load test report and issues list\n- Analyze console errors, network failures, DOM anomalies\n- Map to source code locations\nCONTEXT:\n- Session: .workflow/.csv-wave/tfd-login-test-20260308\n- Upstream: artifacts/TEST-001-issues.json\nEXPECTED: artifacts/ANALYZE-001-rca.md","analyzer","test-pipeline","","console;network","TEST-001","TEST-001","csv-wave","2","pending","","","","",""
-"FIX-001","Fix all issues","PURPOSE: Fix identified issues | Success: All high/medium issues resolved\nTASK:\n- Load RCA report\n- Locate and fix each root cause\n- Run syntax/type checks\nCONTEXT:\n- Session: .workflow/.csv-wave/tfd-login-test-20260308\n- Upstream: artifacts/ANALYZE-001-rca.md\nEXPECTED: Modified source files + artifacts/FIX-001-changes.md","fixer","test-pipeline","","","ANALYZE-001","ANALYZE-001","csv-wave","3","pending","","","","",""
-"VERIFY-001","Verify fixes","PURPOSE: Re-test failed scenarios to verify fixes | Success: Previously failed scenarios now pass\nTASK:\n- Re-execute failed test scenarios\n- Capture evidence and compare\n- Report pass/fail per scenario\nCONTEXT:\n- Session: .workflow/.csv-wave/tfd-login-test-20260308\n- Original: artifacts/TEST-001-report.md\n- Fix: artifacts/FIX-001-changes.md\nEXPECTED: artifacts/VERIFY-001-report.md","verifier","test-pipeline","http://localhost:3000","screenshot;console;network","FIX-001","FIX-001;TEST-001","csv-wave","4","pending","","","","",""
-```
-
-### Example Data (Debug Pipeline)
-
-```csv
-id,title,description,role,pipeline_mode,base_url,evidence_dimensions,deps,context_from,exec_mode,wave,status,findings,artifacts_produced,issues_count,verdict,error
-"REPRODUCE-001","Bug reproduction","PURPOSE: Reproduce bug and collect evidence | Success: Bug reproduced with artifacts\nTASK:\n- Navigate to target URL\n- Execute reproduction steps\n- Capture screenshots, snapshots, console logs, network\nCONTEXT:\n- Session: .workflow/.csv-wave/tfd-save-crash-20260308\n- Bug URL: http://localhost:3000/settings\n- Steps: 1. Click save 2. Observe white screen\nEXPECTED: evidence/ directory with all captures","reproducer","debug-pipeline","http://localhost:3000/settings","screenshot;console;network;snapshot","","","csv-wave","1","pending","","","","",""
-"ANALYZE-001","Root cause analysis","PURPOSE: Analyze evidence to find root cause | Success: RCA with file:line location\nTASK:\n- Load evidence from reproducer\n- Analyze console errors and stack traces\n- Map to source code\nCONTEXT:\n- Session: .workflow/.csv-wave/tfd-save-crash-20260308\n- Upstream: evidence/\nEXPECTED: artifacts/ANALYZE-001-rca.md","analyzer","debug-pipeline","","","REPRODUCE-001","REPRODUCE-001","csv-wave","2","pending","","","","",""
-"FIX-001","Code fix","PURPOSE: Fix the identified bug | Success: Root cause resolved\nTASK:\n- Load RCA report\n- Implement fix\n- Validate syntax\nCONTEXT:\n- Session: .workflow/.csv-wave/tfd-save-crash-20260308\n- Upstream: artifacts/ANALYZE-001-rca.md\nEXPECTED: Modified files + artifacts/FIX-001-changes.md","fixer","debug-pipeline","","","ANALYZE-001","ANALYZE-001","csv-wave","3","pending","","","","",""
-"VERIFY-001","Fix verification","PURPOSE: Verify bug is fixed | Success: Original bug no longer reproduces\nTASK:\n- Same reproduction steps as REPRODUCE-001\n- Capture evidence and compare\n- Confirm resolution\nCONTEXT:\n- Session: .workflow/.csv-wave/tfd-save-crash-20260308\n- Original: evidence/\n- Fix: artifacts/FIX-001-changes.md\nEXPECTED: artifacts/VERIFY-001-report.md","verifier","debug-pipeline","http://localhost:3000/settings","screenshot;console;network;snapshot","FIX-001","FIX-001;REPRODUCE-001","csv-wave","4","pending","","","","",""
-```
-
----
-
-### Column Lifecycle
-
-```
-Decomposer (Phase 1)     Wave Engine (Phase 2)    Agent (Execution)
----------------------    --------------------     -----------------
-id          ---------->  id          ---------->  id
-title       ---------->  title       ---------->  (reads)
-description ---------->  description ---------->  (reads)
-role        ---------->  role        ---------->  (reads)
-pipeline_mode --------->  pipeline_mode --------->  (reads)
-base_url    ---------->  base_url    ---------->  (reads)
-evidence_dimensions --->  evidence_dimensions --->  (reads)
-deps        ---------->  deps        ---------->  (reads)
-context_from---------->  context_from---------->  (reads)
-exec_mode   ---------->  exec_mode   ---------->  (reads)
-                         wave         ---------->  (reads)
-                         prev_context ---------->  (reads)
-                                                   status
-                                                   findings
-                                                   artifacts_produced
-                                                   issues_count
-                                                   verdict
-                                                   error
-```
-
----
-
-## Output Schema (JSON)
-
-Agent output via `report_agent_job_result` (csv-wave tasks):
-
-Tester output:
-```json
-{
-  "id": "TEST-001",
-  "status": "completed",
-  "findings": "Tested 5 features: 3 pass, 2 fail. BUG-001: TypeError on login submit. BUG-002: API 500 on profile save.",
-  "artifacts_produced": "artifacts/TEST-001-report.md;artifacts/TEST-001-issues.json",
-  "issues_count": "2",
-  "verdict": "",
-  "error": ""
-}
-```
-
-Verifier output:
-```json
-{
-  "id": "VERIFY-001",
-  "status": "completed",
-  "findings": "Original bug resolved. Login error no longer appears. No new console errors. No new network failures.",
-  "artifacts_produced": "artifacts/VERIFY-001-report.md",
-  "issues_count": "",
-  "verdict": "pass",
-  "error": ""
-}
-```
-
-Interactive tasks output via structured text or JSON written to `interactive/{id}-result.json`.
-
----
-
-## Discovery Types
-
-| Type | Dedup Key | Data Schema | Description |
-|------|-----------|-------------|-------------|
-| `feature_tested` | `data.feature` | `{feature, name, result, issues}` | Feature test result |
-| `bug_reproduced` | `data.url` | `{url, steps, console_errors, network_failures}` | Bug reproduction result |
-| `evidence_collected` | `data.dimension+data.file` | `{dimension, file, description}` | Evidence artifact saved |
-| `root_cause_found` | `data.file+data.line` | `{category, file, line, confidence}` | Root cause identified |
-| `file_modified` | `data.file` | `{file, change, lines_added}` | Code fix applied |
-| `verification_result` | `data.verdict` | `{verdict, original_error_resolved, new_errors}` | Fix verification |
-| `issue_found` | `data.file+data.line` | `{file, line, severity, description}` | Issue discovered |
-
-### Discovery NDJSON Format
-
-```jsonl
-{"ts":"2026-03-08T10:00:00Z","worker":"TEST-001","type":"feature_tested","data":{"feature":"F-001","name":"Login","result":"fail","issues":1}}
-{"ts":"2026-03-08T10:05:00Z","worker":"REPRODUCE-001","type":"bug_reproduced","data":{"url":"/settings","steps":3,"console_errors":2,"network_failures":0}}
-{"ts":"2026-03-08T10:10:00Z","worker":"ANALYZE-001","type":"root_cause_found","data":{"category":"TypeError","file":"src/components/Settings.tsx","line":142,"confidence":"high"}}
-{"ts":"2026-03-08T10:15:00Z","worker":"FIX-001","type":"file_modified","data":{"file":"src/components/Settings.tsx","change":"Added null check for user object","lines_added":3}}
-```
-
-> Both csv-wave and interactive agents read/write the same discoveries.ndjson file.
-
----
-
-## Cross-Mechanism Context Flow
-
-| Source | Target | Mechanism |
-|--------|--------|-----------|
-| CSV task findings | Interactive task | Injected via spawn message or send_input |
-| Interactive task result | CSV task prev_context | Read from interactive/{id}-result.json |
-| Any agent discovery | Any agent | Shared via discoveries.ndjson |
-
----
-
-## Validation Rules
-
-| Rule | Check | Error |
-|------|-------|-------|
-| Unique IDs | No duplicate `id` values | "Duplicate task ID: {id}" |
-| Valid deps | All dep IDs exist in tasks | "Unknown dependency: {dep_id}" |
-| No self-deps | Task cannot depend on itself | "Self-dependency: {id}" |
-| No circular deps | Topological sort completes | "Circular dependency detected involving: {ids}" |
-| context_from valid | All context IDs exist and in earlier waves | "Invalid context_from: {id}" |
-| exec_mode valid | Value is `csv-wave` or `interactive` | "Invalid exec_mode: {value}" |
-| Description non-empty | Every task has description | "Empty description for task: {id}" |
-| Status enum | status in {pending, completed, failed, skipped} | "Invalid status: {status}" |
-| Role valid | role in {tester, reproducer, analyzer, fixer, verifier} | "Invalid role: {role}" |
-| Pipeline mode valid | pipeline_mode in {test-pipeline, debug-pipeline} | "Invalid pipeline_mode: {mode}" |
-| Verdict valid | verdict in {pass, pass_with_warnings, fail, ""} | "Invalid verdict: {verdict}" |
-| Base URL for browser tasks | tester/reproducer/verifier have non-empty base_url | "Missing base_url for browser task: {id}" |

package/.codex/skills/team-issue/agents/reviewer.md

@@ -1,204 +0,0 @@
-# Reviewer Agent
-
-Technical review agent for issue solutions. Performs multi-dimensional review with scored verdict. Used as interactive agent within the team-issue pipeline when review gates are required (full/batch modes).
-
-## Identity
-
-- **Type**: `interactive`
-- **Responsibility**: Multi-dimensional solution review with verdict routing
-
-## Boundaries
-
-### MUST
-
-- Load role definition via MANDATORY FIRST STEPS pattern
-- Read all solution artifacts and explorer context before reviewing
-- Score across three weighted dimensions: Technical Feasibility (40%), Risk (30%), Completeness (30%)
-- Produce structured output with per-issue and overall verdicts
-- Include file:line references in findings
-- Write audit report to session audits folder
-
-### MUST NOT
-
-- Skip the MANDATORY FIRST STEPS role loading
-- Modify solution artifacts or code
-- Produce unstructured output
-- Review without reading explorer context (when available)
-- Skip any scoring dimension
-
----
-
-## Toolbox
-
-### Available Tools
-
-| Tool | Type | Purpose |
-|------|------|---------|
-| `Read` | file | Load solution artifacts and context files |
-| `Bash` | shell | Run `ccw issue solutions <id> --json` to load bound solutions |
-| `Grep` | search | Search codebase for pattern conformance checks |
-| `Glob` | search | Find relevant files for coverage validation |
-| `Write` | file | Write audit report |
-
----
-
-## Execution
-
-### Phase 1: Context Loading
-
-**Objective**: Load all inputs needed for review.
-
-**Input**:
-
-| Source | Required | Description |
-|--------|----------|-------------|
-| Solution artifacts | Yes | `<session>/solutions/solution-<issueId>.json` |
-| Explorer context | No | `<session>/explorations/context-<issueId>.json` |
-| Bound solutions | Yes | `ccw issue solutions <issueId> --json` |
-| Discoveries | No | `<session>/discoveries.ndjson` |
-| Wisdom files | No | `<session>/wisdom/` |
-
-**Steps**:
-
-1. Read session folder path from spawn message
-2. Extract issue IDs from spawn message
-3. Load explorer context reports for each issue
-4. Load bound solutions for each issue via CLI
-5. Load discoveries for cross-reference
-
----
-
-### Phase 2: Multi-Dimensional Review
-
-**Objective**: Score each solution across three weighted dimensions.
-
-**Technical Feasibility (40%)**:
-
-| Criterion | Check | Score Impact |
-|-----------|-------|-------------|
-| File Coverage | Solution covers all affected files from explorer context | High |
-| Dependency Awareness | Considers dependency cascade effects | Medium |
-| API Compatibility | Maintains backward compatibility | High |
-| Pattern Conformance | Follows existing code patterns | Medium |
-
-**Risk Assessment (30%)**:
-
-| Criterion | Check | Score Impact |
-|-----------|-------|-------------|
-| Scope Creep | Solution stays within issue boundary (task_count <= 10) | High |
-| Breaking Changes | No destructive modifications | High |
-| Side Effects | No unforeseen side effects | Medium |
-| Rollback Path | Can rollback if issues occur | Low |
-
-**Completeness (30%)**:
-
-| Criterion | Check | Score Impact |
-|-----------|-------|-------------|
-| All Tasks Defined | Task decomposition is complete (count > 0) | High |
-| Test Coverage | Includes test plan | Medium |
-| Edge Cases | Considers boundary conditions | Low |
-
-**Score Calculation**:
-
-```
-total_score = round(
-  technical_feasibility.score * 0.4 +
-  risk_assessment.score * 0.3 +
-  completeness.score * 0.3
-)
-```
-
-**Verdict Rules**:
-
-| Score | Verdict | Description |
-|-------|---------|-------------|
-| >= 80 | approved | Solution is ready for implementation |
-| 60-79 | concerns | Minor issues noted, proceed with warnings |
-| < 60 | rejected | Solution needs revision before proceeding |
-
----
-
-### Phase 3: Compile Audit Report
-
-**Objective**: Write structured audit report.
-
-**Steps**:
-
-1. Compute per-issue scores and verdicts
-2. Compute overall verdict (any rejected -> overall rejected)
-3. Write audit report to `<session>/audits/audit-report.json`:
-
-```json
-{
-  "session_id": "<session-id>",
-  "review_timestamp": "<ISO8601>",
-  "issues_reviewed": [
-    {
-      "issue_id": "<issueId>",
-      "solution_id": "<solutionId>",
-      "total_score": 85,
-      "verdict": "approved",
-      "technical_feasibility": {
-        "score": 90,
-        "findings": ["Good file coverage", "API compatible"]
-      },
-      "risk_assessment": {
-        "score": 80,
-        "findings": ["No breaking changes", "Rollback via git revert"]
-      },
-      "completeness": {
-        "score": 82,
-        "findings": ["5 tasks defined", "Test plan included"]
-      }
-    }
-  ],
-  "overall_verdict": "approved",
-  "overall_score": 85,
-  "review_count": 1,
-  "rejection_reasons": [],
-  "actionable_feedback": []
-}
-```
-
-4. For rejected solutions: include specific rejection reasons and actionable feedback for SOLVE-fix task
-
----
-
-## Structured Output Template
-
-```
-## Summary
-- Review of <N> solutions: <verdict>
-
-## Findings
-- Finding 1: specific description with file:line reference
-- Finding 2: specific description with file:line reference
-
-## Per-Issue Verdicts
-- <issueId>: <score>/100 (<verdict>)
-  - Technical: <score>/100
-  - Risk: <score>/100
-  - Completeness: <score>/100
-
-## Overall Verdict
-<approved|concerns|rejected> (score: <N>/100)
-
-## Rejection Feedback (if rejected)
-1. Specific concern with remediation suggestion
-2. Specific concern with remediation suggestion
-
-## Open Questions
-1. Question needing clarification (if any)
-```
-
----
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Solution file not found | Report in Open Questions, score as 0 for completeness |
-| Explorer context missing | Proceed with reduced confidence, note in findings |
-| Bound solution not found via CLI | Attempt file-based fallback, report if still missing |
-| Processing failure | Output partial results with clear status indicator |
-| Timeout approaching | Output current findings with "PARTIAL" status |

package/.codex/skills/team-issue/instructions/agent-instruction.md

@@ -1,198 +0,0 @@
-# Agent Instruction -- Team Issue Resolution
-
-CSV agent instruction template for `spawn_agents_on_csv`. Each agent receives this template with its row's column values substituted via `{column_name}` placeholders.
-
----
-
-## TASK ASSIGNMENT
-
-### MANDATORY FIRST STEPS
-1. Read shared discoveries: `.workflow/.csv-wave/{session_id}/discoveries.ndjson` (if exists, skip if not)
-2. Read project context: `.workflow/project-tech.json` (if exists)
-3. Read wisdom files: `.workflow/.csv-wave/{session_id}/wisdom/` (conventions, learnings)
-
----
-
-## Your Task
-
-**Task ID**: {id}
-**Title**: {title}
-**Description**: {description}
-**Role**: {role}
-**Issue IDs**: {issue_ids}
-**Execution Method**: {execution_method}
-
-### Previous Tasks' Findings (Context)
-{prev_context}
-
----
-
-## Execution Protocol
-
-### Role Router
-
-Determine your execution steps based on `{role}`:
-
-| Role | Execution Steps |
-|------|----------------|
-| explorer | Step A: Codebase Exploration |
-| planner | Step B: Solution Design |
-| integrator | Step C: Queue Formation |
-| implementer | Step D: Implementation |
-
----
-
-### Step A: Codebase Exploration (explorer role)
-
-1. Extract issue ID from `{issue_ids}` (pattern: `GH-\d+` or `ISS-\d{8}-\d{6}`)
-2. Load issue details: `Bash("ccw issue status <issueId> --json")`
-3. Assess complexity from issue keywords:
-
-| Signal | Weight |
-|--------|--------|
-| Structural change (refactor, architect) | +2 |
-| Cross-cutting (multiple, across) | +2 |
-| Integration (api, database) | +1 |
-| High priority (>= 4) | +1 |
-
-4. Explore codebase:
-   - Use `mcp__ace-tool__search_context` for semantic search based on issue keywords
-   - Read relevant files to understand context
-   - Map dependencies and integration points
-   - Check git log for related changes
-
-5. Write context report:
-   ```bash
-   # Write to session explorations folder
-   Write("<session>/explorations/context-<issueId>.json", JSON.stringify({
-     issue_id: "<issueId>",
-     issue: { id, title, priority, status, labels, feedback },
-     relevant_files: [{ path, relevance }],
-     dependencies: [],
-     impact_scope: "low|medium|high",
-     existing_patterns: [],
-     related_changes: [],
-     key_findings: [],
-     complexity_assessment: "Low|Medium|High"
-   }))
-   ```
-
-6. Share discoveries to board
-
----
-
-### Step B: Solution Design (planner role)
-
-1. Extract issue ID from `{issue_ids}`
-2. Load explorer context (if available): Read upstream artifact from prev_context
-3. Check if this is a revision task (SOLVE-fix-*): If yes, read audit report for rejection feedback
-4. Generate solution via CLI:
-   ```bash
-   ccw cli -p "PURPOSE: Design solution for issue <issueId> and decompose into implementation tasks; success = solution with task breakdown
-   TASK: * Load issue details * Analyze explorer context * Design solution approach * Break into tasks * Generate solution JSON
-   MODE: analysis
-   CONTEXT: @**/* | Memory: Issue <issueId>, Explorer findings from prev_context
-   EXPECTED: Solution JSON with: issue_id, solution_id, approach, tasks[], estimated_files, dependencies
-   CONSTRAINTS: Follow existing patterns | Minimal changes
-   " --tool gemini --mode analysis --rule planning-breakdown-task-steps
-   ```
-5. Write solution artifact:
-   ```bash
-   Write("<session>/solutions/solution-<issueId>.json", solutionJson)
-   ```
-6. Bind solution to issue: `Bash("ccw issue bind <issueId> <solutionId>")`
-
----
-
-### Step C: Queue Formation (integrator role)
-
-1. Extract issue IDs from `{issue_ids}`
-2. Verify all issues have bound solutions: `Bash("ccw issue solutions <issueId> --json")`
-3. Analyze file conflicts between solutions
-4. Build dependency graph for execution ordering
-5. Determine parallel execution groups
-6. Write execution queue:
-   ```bash
-   Write("<session>/queue/execution-queue.json", JSON.stringify({
-     queue: [{ issue_id, solution_id, order, depends_on: [], estimated_files: [] }],
-     conflicts: [{ issues: [], files: [], resolution: "" }],
-     parallel_groups: [{ group: 0, issues: [] }]
-   }))
-   ```
-
----
-
-### Step D: Implementation (implementer role)
-
-1. Extract issue ID from `{issue_ids}`
-2. Load bound solution: `Bash("ccw issue solutions <issueId> --json")`
-3. Load explorer context (from prev_context or file)
-4. Determine execution backend from `{execution_method}`:
-
-| Method | CLI Command |
-|--------|-------------|
-| codex | `ccw cli --tool codex --mode write --id issue-<issueId>` |
-| gemini | `ccw cli --tool gemini --mode write --id issue-<issueId>` |
-| qwen | `ccw cli --tool qwen --mode write --id issue-<issueId>` |
-
-5. Execute implementation:
-   ```bash
-   ccw cli -p "PURPOSE: Implement solution for issue <issueId>; success = all tasks completed, tests pass
-   TASK: <solution.tasks as bullet points>
-   MODE: write
-   CONTEXT: @**/* | Memory: Solution plan, explorer context
-   EXPECTED: Working implementation with code changes, test updates
-   CONSTRAINTS: Follow existing patterns | Maintain backward compatibility
-   " --tool <execution_method> --mode write --rule development-implement-feature
-   ```
-
-6. Verify: Run tests, check for errors
-7. Update issue status: `Bash("ccw issue update <issueId> --status resolved")`
-
----
-
-## Share Discoveries (ALL ROLES)
-
-After completing your work, append findings to the shared discovery board:
-
-```bash
-echo '{"ts":"<ISO8601>","worker":"{id}","type":"<type>","data":{...}}' >> <session>/discoveries.ndjson
-```
-
-**Discovery Types to Share**:
-
-| Type | Data Schema | When to Use |
-|------|-------------|-------------|
-| `file_found` | `{path, relevance, purpose}` | Explorer: relevant file discovered |
-| `pattern_found` | `{pattern, location, description}` | Explorer: code pattern identified |
-| `dependency_found` | `{from, to, type}` | Explorer: module dependency found |
-| `solution_approach` | `{issue_id, approach, estimated_files}` | Planner: solution strategy |
-| `conflict_found` | `{issues, files, resolution}` | Integrator: file conflict |
-| `impl_result` | `{issue_id, files_changed, tests_pass}` | Implementer: build outcome |
-
----
-
-## Output (report_agent_job_result)
-
-Return JSON:
-```json
-{
-  "id": "{id}",
-  "status": "completed | failed",
-  "findings": "Key discoveries and implementation notes (max 500 chars)",
-  "artifact_path": "relative path to main artifact file (e.g., explorations/context-ISS-xxx.json)",
-  "error": ""
-}
-```
-
----
-
-## Quality Checklist
-
-Before reporting complete:
-- [ ] Mandatory first steps completed (discoveries, project context, wisdom)
-- [ ] Role-specific execution steps followed
-- [ ] At least 1 discovery shared to board
-- [ ] Artifact file written to session folder
-- [ ] Findings include file:line references where applicable
-- [ ] prev_context findings were incorporated