maestro-flow 0.5.31 → 0.5.33

package/.claude/skills/team-issue/roles/coordinator/commands/monitor.md

@@ -0,0 +1,229 @@
+# Monitor Pipeline
+
+Event-driven pipeline coordination. Beat model: coordinator wake -> process -> spawn -> STOP.
+
+## Constants
+
+- SPAWN_MODE: background
+- ONE_STEP_PER_INVOCATION: true
+- FAST_ADVANCE_AWARE: true
+- WORKER_AGENT: team-worker
+- MAX_FIX_CYCLES: 2
+
+## Handler Router
+
+| Source | Handler |
+|--------|---------|
+| Message contains [explorer], [planner], [reviewer], [integrator], [implementer] | handleCallback |
+| "consensus_blocked" | handleConsensus |
+| "capability_gap" | handleAdapt |
+| "check" or "status" | handleCheck |
+| "resume" or "continue" | handleResume |
+| All tasks completed | handleComplete |
+| Default | handleSpawnNext |
+
+## handleCallback
+
+Worker completed. Process and advance.
+
+1. Parse message to identify role and task ID:
+
+| Message Pattern | Role Detection |
+|----------------|---------------|
+| `[explorer]` or task ID `EXPLORE-*` | explorer |
+| `[planner]` or task ID `SOLVE-*` | planner |
+| `[reviewer]` or task ID `AUDIT-*` | reviewer |
+| `[integrator]` or task ID `MARSHAL-*` | integrator |
+| `[implementer]` or task ID `BUILD-*` | implementer |
+
+2. Mark task as completed: `TaskUpdate({ taskId: "<task-id>", status: "completed" })`
+3. Record completion in session state
+
+4. **Review gate check** (when reviewer completes):
+   - If completed task is AUDIT-* AND pipeline is full or batch:
+   - Read audit report from `<session>/audits/audit-report.json`
+   - Read .msg/meta.json for fix_cycles
+
+   | Verdict | fix_cycles < max | Action |
+   |---------|-----------------|--------|
+   | rejected | Yes | Increment fix_cycles, create SOLVE-fix + AUDIT re-review tasks (see dispatch.md Review-Fix Cycle), proceed to handleSpawnNext |
+   | rejected | No (>= max) | Force proceed — log warning, unblock MARSHAL |
+   | concerns | - | Log concerns, proceed to MARSHAL (non-blocking) |
+   | approved | - | Proceed to MARSHAL via handleSpawnNext |
+
+   - Log team_msg with type "review_result" or "fix_required"
+   - If force proceeding past rejection, mark skipped fix tasks as completed (skip)
+
+5. **Deferred BUILD task creation** (when integrator completes):
+   - If completed task is MARSHAL-* AND pipeline is batch:
+   - Read execution queue from `.workflow/issues/queue/execution-queue.json`
+   - Parse parallel_groups to determine BUILD task count M
+   - Create BUILD-001..M tasks dynamically (see dispatch.md Batch Pipeline BUILD section)
+   - Proceed to handleSpawnNext
+
+6. Proceed to handleSpawnNext
+
+## handleCheck
+
+Read-only status report, then STOP.
+
+**Worker Progress** (from message bus):
+
+Before generating status output, read worker milestones:
+
+```javascript
+const progressMsgs = mcp__maestro__team_msg({
+  operation: "list", session_id: sessionId, type: "progress", last: 50
+})
+const blockerMsgs = mcp__maestro__team_msg({
+  operation: "list", session_id: sessionId, type: "blocker", last: 10
+})
+
+// Aggregate latest milestone per task
+const taskProgress = {}
+for (const msg of (progressMsgs.result?.messages || [])) {
+  const tid = msg.data?.task_id
+  if (tid && (!taskProgress[tid] || msg.ts > taskProgress[tid].ts)) {
+    taskProgress[tid] = { phase: msg.data.phase, pct: msg.data.progress_pct, ts: msg.ts }
+  }
+}
+```
+
+Include in status output:
+- Per-worker latest milestone (phase + progress_pct) next to task status
+- Active blockers section (if any blockerMsgs found)
+
+```
+[coordinator] Pipeline Status (<pipeline-mode>)
+[coordinator] Progress: <done>/<total> (<pct>%)
+[coordinator] Active: <workers with elapsed time>
+[coordinator] Ready: <pending tasks with resolved deps>
+[coordinator] Fix Cycles: <fix_cycles>/<max_fix_cycles>
+[coordinator] Commands: 'resume' to advance | 'check' to refresh
+```
+
+## handleResume
+
+1. Audit task list: Tasks stuck in "in_progress" -> reset to "pending"
+2. Proceed to handleSpawnNext
+
+## handleSpawnNext
+
+Find ready tasks, spawn workers, STOP.
+
+1. Collect: completedSubjects, inProgressSubjects, readySubjects
+2. No ready + work in progress -> report waiting, STOP
+3. No ready + nothing in progress -> handleComplete
+4. Has ready -> for each:
+   a. TaskUpdate -> in_progress
+   b. team_msg log -> task_unblocked
+   c. Spawn team-worker (see SKILL.md Spawn Template):
+      ```
+      Agent({
+        subagent_type: "team-worker",
+        description: "Spawn <role> worker for <task-id>",
+        team_name: "issue",
+        name: "<role>",
+        run_in_background: true,
+        prompt: `## Role Assignment
+      role: <role>
+      role_spec: ~  or <project>/.claude/skills/team-issue/roles/<role>/role.md
+      session: <session-folder>
+      session_id: <session-id>
+      team_name: issue
+      requirement: <task-description>
+      inner_loop: false
+
+      ## Progress Milestones
+      session_id: <session-id>
+      Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
+      Report blockers immediately via team_msg type="blocker".
+      Report completion via team_msg type="task_complete" after final SendMessage.
+
+      Read role_spec file to load Phase 2-4 domain instructions.
+      Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`
+      })
+      ```
+   d. Add to active_workers
+
+5. Parallel spawn rules:
+
+| Pipeline | Scenario | Spawn Behavior |
+|----------|----------|---------------|
+| Quick | All stages | One worker at a time |
+| Full | All stages | One worker at a time |
+| Batch | EXPLORE-001..N unblocked | Spawn ALL N explorer workers in parallel (max 5) |
+| Batch | BUILD-001..M unblocked | Spawn ALL M implementer workers in parallel (max 3) |
+| Batch | Other stages | One worker at a time |
+
+**Parallel spawn** (Batch mode with multiple ready tasks for same role):
+```
+Agent({
+  subagent_type: "team-worker",
+  name: "<role>-<N>",
+  team_name: "issue",
+  run_in_background: true,
+  prompt: `## Role Assignment
+role: <role>
+role_spec: ~  or <project>/.claude/skills/team-issue/roles/<role>/role.md
+session: <session-folder>
+session_id: <session-id>
+team_name: issue
+requirement: <task-description>
+agent_name: <role>-<N>
+inner_loop: false
+
+## Progress Milestones
+session_id: <session-id>
+Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
+Report blockers immediately via team_msg type="blocker".
+Report completion via team_msg type="task_complete" after final SendMessage.
+
+Read role_spec file to load Phase 2-4 domain instructions.
+Execute built-in Phase 1 (task discovery, owner=<role>-<N>) -> role Phase 2-4 -> built-in Phase 5 (report).`
+})
+```
+
+6. Update session, output summary, STOP
+
+## handleComplete
+
+Pipeline done. Generate report and completion action.
+
+Completion check by mode:
+| Mode | Completion Condition |
+|------|---------------------|
+| quick | All 4 tasks completed |
+| full | All 5 tasks (+ any fix cycle tasks) completed |
+| batch | All N EXPLORE + N SOLVE + 1 AUDIT + 1 MARSHAL + M BUILD (+ any fix cycle tasks) completed |
+
+1. Verify all tasks completed via TaskList()
+2. If any tasks not completed, return to handleSpawnNext
+3. If all completed -> transition to coordinator Phase 5
+
+## handleConsensus
+
+Handle consensus_blocked signals.
+
+| Severity | Action |
+|----------|--------|
+| HIGH | Pause pipeline, notify user with findings summary |
+| MEDIUM | Log finding, attempt to continue |
+| LOW | Log finding, continue pipeline |
+
+## handleAdapt
+
+Capability gap reported mid-pipeline.
+
+1. Parse gap description
+2. Check if existing role covers it -> redirect
+3. Role count < 6 -> generate dynamic role-spec in <session>/role-specs/
+4. Create new task, spawn worker
+5. Role count >= 6 -> merge or pause
+
+## Fast-Advance Reconciliation
+
+On every coordinator wake:
+1. Read team_msg entries with type="fast_advance"
+2. Sync active_workers with spawned successors
+3. No duplicate spawns

package/.claude/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 (NOT `general-purpose`)
+- Follow Command Execution Protocol for dispatch and monitor commands
+- Respect pipeline stage dependencies (blockedBy)
+- Stop after spawning workers — wait for callbacks
+- 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 callback | Message 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 (audit TaskList, reset in_progress->pending, rebuild team, spawn first ready task)
+4. Multiple -> AskUserQuestion 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 -> AskUserQuestion 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({ command: "pwd" })`
+   - `skill_root` = `<project_root>/.claude/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. TeamCreate with team name `issue`
+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__maestro__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. Create tasks for selected pipeline with correct blockedBy
+3. Update session.json with task count
+
+## Phase 4: Spawn-and-Stop
+
+Delegate to @commands/monitor.md#handleSpawnNext:
+1. Find ready tasks (pending + blockedBy 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):
+   ```
+   AskUserQuestion({
+     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" -> TeamDelete() -> 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 | AskUserQuestion 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/.claude/skills/team-issue/roles/explorer/role.md

@@ -0,0 +1,102 @@
+---
+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: `(project_root_path, query)` |
+| Medium/High | CLI exploration: `Bash("maestro delegate \\\"<exploration_prompt>\" --to 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"
+}
+```
+
+### Tech Profile Scan
+
+After exploration, scan findings for context-aware trigger signals (based on detected codebase characteristics):
+
+1. Check relevant_files and dependencies → signals (`sql_detected`, `auth_detected`, `api_surface`)
+2. Check code patterns in explored files → risk signals (`injection_risk`, `eval_usage`, `perf_sensitive`)
+3. Include `tech_profile` in Phase 5 state_update data
+
+## 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/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 | `maestro delegate --to codex --mode write --id issue-<issueId>` |
+| gemini | task_count <= 3 or explicit | `maestro delegate --to gemini --mode write --id issue-<issueId>` |
+| qwen | explicit | `maestro delegate --to 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("maestro delegate \\\"<prompt>\" --to codex --mode write --id issue-<issueId>", { run_in_background: false })`
+- **gemini**: `Bash("maestro delegate \\\"<prompt>\" --to gemini --mode write --id issue-<issueId>", { run_in_background: false })`
+- **qwen**: `Bash("maestro delegate \\\"<prompt>\" --to qwen --mode write --id issue-<issueId>", { run_in_background: false })`
+
+On CLI failure, resume: `maestro delegate "Continue" --resume issue-<issueId> --to <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/.claude/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("maestro delegate \\\"
+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", { run_in_background: false })
+```
+
+**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