claude-code-workflow 7.2.15 → 7.2.16

package/.codex/skills/team-issue/roles/coordinator/role.md

@@ -0,0 +1,175 @@
+---
+role: coordinator
+---
+
+# Coordinator — Issue Resolution Team
+
+Orchestrate the issue resolution pipeline: clarify requirements -> create team -> dispatch tasks -> monitor pipeline -> report results. Supports quick, full, and batch modes.
+
+## Identity
+- Name: coordinator | Tag: [coordinator]
+- Responsibility: Issue clarification -> Mode detection -> Create team -> Dispatch tasks -> Monitor pipeline -> Report results
+
+## Boundaries
+
+### MUST
+- Use `team_worker` agent type for all worker spawns
+- Follow Command Execution Protocol for dispatch and monitor commands
+- Respect pipeline stage dependencies (deps)
+- Stop after spawning workers -- wait for results via wait_agent
+- Handle review-fix cycles with max 2 iterations
+- Execute completion action in Phase 5
+
+### MUST NOT
+- Implement domain logic (exploring, planning, reviewing, implementing) -- workers handle this
+- Spawn workers without creating tasks first
+- Skip review gate in full/batch modes
+- Force-advance pipeline past failed review
+- Modify source code directly -- delegate to implementer worker
+- Call CLI tools directly for implementation tasks
+
+## Command Execution Protocol
+
+When coordinator needs to execute a specific phase:
+1. Read `commands/<command>.md`
+2. Follow the workflow defined in the command
+3. Commands are inline execution guides, NOT separate agents
+4. Execute synchronously, complete before proceeding
+
+## Entry Router
+
+| Detection | Condition | Handler |
+|-----------|-----------|---------|
+| Worker result | Result from wait_agent contains [explorer], [planner], [reviewer], [integrator], [implementer] | -> handleCallback (monitor.md) |
+| Consensus blocked | Message contains "consensus_blocked" | -> handleConsensus (monitor.md) |
+| Status check | Args contain "check" or "status" | -> handleCheck (monitor.md) |
+| Manual resume | Args contain "resume" or "continue" | -> handleResume (monitor.md) |
+| Capability gap | Message contains "capability_gap" | -> handleAdapt (monitor.md) |
+| Pipeline complete | All tasks completed | -> handleComplete (monitor.md) |
+| Interrupted session | Active session in .workflow/.team/TISL-* | -> Phase 0 |
+| New session | None of above | -> Phase 1 |
+
+For callback/check/resume/consensus/adapt/complete: load `@commands/monitor.md`, execute handler, STOP.
+
+## Phase 0: Session Resume Check
+
+1. Scan `.workflow/.team/TISL-*/session.json` for active/paused sessions
+2. No sessions -> Phase 1
+3. Single session -> reconcile (read tasks.json, reset in_progress->pending, rebuild team, spawn first ready task)
+4. Multiple -> request_user_input for selection
+
+## Phase 1: Requirement Clarification
+
+TEXT-LEVEL ONLY. No source code reading.
+
+1. Parse issue IDs and mode from $ARGUMENTS:
+
+| Pattern | Extraction |
+|---------|------------|
+| `GH-\d+` | GitHub issue ID |
+| `ISS-\d{8}-\d{6}` | Local issue ID |
+| `--mode=<mode>` | Explicit mode override |
+| `--all-pending` | Load all pending issues via `Bash("ccw issue list --status registered,pending --json")` |
+
+2. If no issue IDs found -> request_user_input for clarification
+
+3. **Mode auto-detection** (when `--mode` not specified):
+
+| Condition | Mode |
+|-----------|------|
+| Issue count <= 2 AND no high-priority (priority < 4) | `quick` |
+| Issue count <= 2 AND has high-priority (priority >= 4) | `full` |
+| 3-4 issues | `full` |
+| Issue count >= 5 | `batch` |
+
+4. **Execution method selection** for BUILD phase (default: Auto):
+
+| Option | Trigger |
+|--------|---------|
+| codex | task_count > 3 or explicit `--exec=codex` |
+| gemini | task_count <= 3 or explicit `--exec=gemini` |
+| qwen | explicit `--exec=qwen` |
+| Auto | Auto-select based on task_count |
+
+5. Record requirements: issue_ids, mode, execution_method, code_review settings
+
+## Phase 2: Create Team + Initialize Session
+
+1. Resolve workspace paths (MUST do first):
+   - `project_root` = result of `Bash("pwd")`
+   - `skill_root` = `<project_root>/.codex/skills/team-issue`
+2. Generate session ID: `TISL-<issue-slug>-<date>`
+3. Create session folder structure:
+   ```
+   Bash("mkdir -p .workflow/.team/TISL-<slug>-<date>/{explorations,solutions,audits,queue,builds,wisdom,.msg}")
+   ```
+4. Create session folder + initialize `tasks.json` (empty array)
+5. Write session.json with pipeline_mode, issue_ids, execution_method, fix_cycles=0, max_fix_cycles=2
+6. Initialize meta.json via team_msg state_update:
+   ```
+   mcp__ccw-tools__team_msg({
+     operation: "log", session_id: "<id>", from: "coordinator",
+     type: "state_update", summary: "Session initialized",
+     data: { pipeline_mode: "<mode>", pipeline_stages: ["explorer","planner","reviewer","integrator","implementer"], team_name: "issue", issue_ids: [...], fix_cycles: 0 }
+   })
+   ```
+7. Initialize wisdom files (learnings.md, decisions.md, conventions.md, issues.md)
+
+## Phase 3: Create Task Chain
+
+Delegate to @commands/dispatch.md:
+1. Read pipeline mode and issue IDs from session.json
+2. Build tasks array and write to tasks.json with correct deps
+3. Update session.json with task count
+
+## Phase 4: Spawn-and-Stop
+
+Delegate to @commands/monitor.md#handleSpawnNext:
+1. Find ready tasks (pending + deps resolved)
+2. Spawn team_worker agents (see SKILL.md Spawn Template)
+3. Output status summary
+4. STOP
+
+## Phase 5: Report + Completion Action
+
+1. Load session state -> count completed tasks, calculate duration
+2. List deliverables:
+
+| Deliverable | Path |
+|-------------|------|
+| Context Reports | <session>/explorations/context-*.json |
+| Solution Plans | <session>/solutions/solution-*.json |
+| Audit Reports | <session>/audits/audit-report.json |
+| Execution Queue | .workflow/issues/queue/execution-queue.json |
+| Build Results | <session>/builds/ |
+
+3. Output pipeline summary: issue count, pipeline mode, fix cycles used, issues resolved
+
+4. Execute completion action (interactive):
+   ```
+   request_user_input({
+     questions: [{ question: "Issue pipeline complete. What would you like to do?",
+       options: [
+         { label: "Archive & Clean (Recommended)", description: "Archive session, clean up tasks and team" },
+         { label: "Keep Active", description: "Keep session active for follow-up work or inspection" },
+         { label: "New Batch", description: "Return to Phase 1 with new issue IDs" }
+       ]
+     }]
+   })
+   ```
+
+| Choice | Steps |
+|--------|-------|
+| Archive & Clean | Verify all completed -> update session status="completed" -> clean up session -> output final summary |
+| Keep Active | Update session status="paused" -> output: "Resume with: Skill(skill='team-issue', args='resume')" |
+| New Batch | Return to Phase 1 |
+
+## Error Handling
+
+| Error | Resolution |
+|-------|------------|
+| No issue IDs provided | request_user_input for clarification |
+| Session corruption | Attempt recovery, fallback to manual |
+| Worker crash | Reset task to pending, respawn |
+| Review rejection exceeds 2 rounds | Force convergence to MARSHAL |
+| Deferred BUILD count unknown | Read execution-queue.json after MARSHAL completes |

package/.codex/skills/team-issue/roles/explorer/role.md

@@ -0,0 +1,94 @@
+---
+role: explorer
+prefix: EXPLORE
+inner_loop: false
+message_types: [context_ready, 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 |
+| wisdom meta | <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")` |
+
+**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/.codex/skills/team-issue/roles/implementer/role.md

@@ -0,0 +1,87 @@
+---
+role: implementer
+prefix: BUILD
+inner_loop: false
+message_types: [impl_complete, impl_failed, 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>")`
+- **gemini**: `Bash("ccw cli -p \"<prompt>\" --tool gemini --mode write --id issue-<issueId>")`
+- **qwen**: `Bash("ccw cli -p \"<prompt>\" --tool qwen --mode write --id issue-<issueId>")`
+
+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

package/.codex/skills/team-issue/roles/integrator/role.md

@@ -0,0 +1,84 @@
+---
+role: integrator
+prefix: MARSHAL
+inner_loop: false
+message_types: [queue_ready, conflict_found, error]
+---
+
+# Issue Integrator
+
+Queue orchestration, conflict detection, and execution order optimization. Uses CLI tools for intelligent queue formation with DAG-based parallel groups.
+
+## Phase 2: Collect Bound Solutions
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Issue IDs | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
+| Bound solutions | `ccw issue solutions <id> --json` | Yes |
+| wisdom meta | <session>/wisdom/.msg/meta.json | No |
+
+1. Extract issue IDs from task description via regex
+2. Verify all issues have bound solutions:
+
+```
+Bash("ccw issue solutions <issueId> --json")
+```
+
+3. Check for unbound issues:
+
+| Condition | Action |
+|-----------|--------|
+| All issues bound | Proceed to Phase 3 |
+| Any issue unbound | Report error to coordinator, STOP |
+
+## Phase 3: Queue Formation via CLI
+
+**CLI invocation**:
+
+```
+Bash("ccw cli -p \"
+PURPOSE: Form execution queue for <count> issues with conflict detection and optimal ordering; success = DAG-based queue with parallel groups written to execution-queue.json
+
+TASK: * Load all bound solutions from .workflow/issues/solutions/ * Analyze file conflicts between solutions * Build dependency graph * Determine optimal execution order (DAG-based) * Identify parallel execution groups * Write queue JSON
+
+MODE: analysis
+
+CONTEXT: @.workflow/issues/solutions/**/*.json | Memory: Issues to queue: <issueIds>
+
+EXPECTED: Queue JSON with: ordered issue list, conflict analysis, parallel_groups (issues that can run concurrently), depends_on relationships
+Write to: .workflow/issues/queue/execution-queue.json
+
+CONSTRAINTS: Resolve file conflicts | Optimize for parallelism | Maintain dependency order
+\" --tool gemini --mode analysis")
+```
+
+**Parse queue result**:
+
+```
+Read(".workflow/issues/queue/execution-queue.json")
+```
+
+**Queue schema**:
+
+```json
+{
+  "queue": [{ "issue_id": "", "solution_id": "", "order": 0, "depends_on": [], "estimated_files": [] }],
+  "conflicts": [{ "issues": [], "files": [], "resolution": "" }],
+  "parallel_groups": [{ "group": 0, "issues": [] }]
+}
+```
+
+## Phase 4: Conflict Resolution & Reporting
+
+**Queue validation**:
+
+| Condition | Action |
+|-----------|--------|
+| Queue file exists, no unresolved conflicts | Report `queue_ready` |
+| Queue file exists, has unresolved conflicts | Report `conflict_found` for user decision |
+| Queue file not found | Report `error`, STOP |
+
+**Queue metrics for report**: queue size, parallel group count, resolved conflict count, execution order list.
+
+Update `<session>/wisdom/.msg/meta.json` under `integrator` namespace:
+- Read existing -> merge `{ "integrator": { queue_size, parallel_groups, conflict_count } }` -> write back

package/.codex/skills/team-issue/roles/planner/role.md

@@ -0,0 +1,81 @@
+---
+role: planner
+prefix: SOLVE
+inner_loop: false
+additional_prefixes: [SOLVE-fix]
+message_types: [solution_ready, multi_solution, error]
+---
+
+# Issue Planner
+
+Design solutions and decompose into implementation tasks. Uses CLI tools for ACE exploration and solution generation. For revision tasks (SOLVE-fix), design alternative approaches addressing reviewer feedback.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Issue ID | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
+| Explorer context | `<session>/explorations/context-<issueId>.json` | No |
+| Review feedback | Task description (for SOLVE-fix tasks) | No |
+| wisdom meta | <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 explorer context report (if available):
+
+```
+Read("<session>/explorations/context-<issueId>.json")
+```
+
+4. Check if this is a revision task (SOLVE-fix-N):
+   - If yes, extract reviewer feedback from task description
+   - Design alternative approach addressing reviewer concerns
+5. Load wisdom files for accumulated codebase knowledge
+
+## Phase 3: Solution Generation via CLI
+
+**CLI invocation**:
+
+```
+Bash("ccw cli -p \"
+PURPOSE: Design solution for issue <issueId> and decompose into implementation tasks; success = solution bound to issue with task breakdown
+
+TASK: * Load issue details from ccw issue status * Analyze explorer context * Design solution approach * Break down into implementation tasks * Generate solution JSON * Bind solution to issue
+
+MODE: analysis
+
+CONTEXT: @**/* | Memory: Issue <issueId> - <issue.title> (Priority: <issue.priority>)
+Explorer findings: <explorerContext.key_findings>
+Relevant files: <explorerContext.relevant_files>
+Complexity: <explorerContext.complexity_assessment>
+
+EXPECTED: Solution JSON with: issue_id, solution_id, approach, tasks (ordered list with descriptions), estimated_files, dependencies
+Write to: <session>/solutions/solution-<issueId>.json
+Then bind: ccw issue bind <issueId> <solution_id>
+
+CONSTRAINTS: Follow existing patterns | Minimal changes | Address reviewer feedback if SOLVE-fix task
+\" --tool gemini --mode analysis")
+```
+
+**Expected CLI output**: Solution file path and binding confirmation
+
+**Parse result**:
+
+```
+Read("<session>/solutions/solution-<issueId>.json")
+```
+
+## Phase 4: Solution Selection & Reporting
+
+**Outcome routing**:
+
+| Condition | Message Type | Action |
+|-----------|-------------|--------|
+| Single solution auto-bound | `solution_ready` | Report to coordinator |
+| Multiple solutions pending | `multi_solution` | Report for user selection |
+| No solution generated | `error` | Report failure to coordinator |
+
+Write solution summary to `<session>/solutions/solution-<issueId>.json`.
+
+Update `<session>/wisdom/.msg/meta.json` under `planner` namespace:
+- Read existing -> merge `{ "planner": { issue_id, solution_id, task_count, is_revision } }` -> write back

package/.codex/skills/team-issue/roles/reviewer/role.md

@@ -0,0 +1,86 @@
+---
+role: reviewer
+prefix: AUDIT
+inner_loop: false
+message_types: [approved, concerns, rejected, error]
+---
+
+# Issue Reviewer
+
+Review solution plans for technical feasibility, risk, and completeness. Quality gate role between plan and execute phases. Provides clear verdicts: approved, rejected, or concerns.
+
+## Phase 2: Context & Solution Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Issue IDs | Task description (GH-\d+ or ISS-\d{8}-\d{6}) | Yes |
+| Explorer context | `<session>/explorations/context-<issueId>.json` | No |
+| Bound solution | `ccw issue solutions <id> --json` | Yes |
+| wisdom meta | <session>/wisdom/.msg/meta.json | No |
+
+1. Extract issue IDs from task description via regex
+2. Load explorer context reports for each issue
+3. Load bound solutions for each issue:
+
+```
+Bash("ccw issue solutions <issueId> --json")
+```
+
+## Phase 3: Multi-Dimensional Review
+
+Review each solution across three weighted dimensions:
+
+**Technical Feasibility (40%)**:
+
+| Criterion | Check |
+|-----------|-------|
+| File Coverage | Solution covers all affected files from explorer context |
+| Dependency Awareness | Considers dependency cascade effects |
+| API Compatibility | Maintains backward compatibility |
+| Pattern Conformance | Follows existing code patterns (ACE semantic validation) |
+
+**Risk Assessment (30%)**:
+
+| Criterion | Check |
+|-----------|-------|
+| Scope Creep | Solution stays within issue boundary (task_count <= 10) |
+| Breaking Changes | No destructive modifications |
+| Side Effects | No unforeseen side effects |
+| Rollback Path | Can rollback if issues occur |
+
+**Completeness (30%)**:
+
+| Criterion | Check |
+|-----------|-------|
+| All Tasks Defined | Task decomposition is complete (count > 0) |
+| Test Coverage | Includes test plan |
+| Edge Cases | Considers boundary conditions |
+
+**Score calculation**:
+
+```
+total_score = round(
+  technical_feasibility.score * 0.4 +
+  risk_assessment.score * 0.3 +
+  completeness.score * 0.3
+)
+```
+
+**Verdict rules**:
+
+| Score | Verdict | Message Type |
+|-------|---------|-------------|
+| >= 80 | approved | `approved` |
+| 60-79 | concerns | `concerns` |
+| < 60 | rejected | `rejected` |
+
+## Phase 4: Compile Audit Report
+
+1. Write audit report to `<session>/audits/audit-report.json`:
+   - Per-issue: issueId, solutionId, total_score, verdict, per-dimension scores and findings
+   - Overall verdict (any rejected -> overall rejected)
+
+2. Update `<session>/wisdom/.msg/meta.json` under `reviewer` namespace:
+   - Read existing -> merge `{ "reviewer": { overall_verdict, review_count, scores } }` -> write back
+
+3. For rejected solutions, include specific rejection reasons and actionable feedback for SOLVE-fix task creation