Refactor architecture optimization and issue resolution workflows

- Enhanced multi-perspective discussion capabilities in discuss-subagent for architecture optimization, integrating CLI tools for structured analysis and recommendations.
- Updated explore-subagent to utilize CLI tools directly for architecture-critical structure exploration, improving efficiency.
- Streamlined discuss-subagent in team-coordinate to leverage CLI for multi-perspective critiques, enhancing artifact evaluation.
- Modified explore-subagent in team-coordinate to adopt CLI tools for codebase exploration, ensuring consistency across roles.
- Expanded team-issue skill to include additional tools for issue resolution, refining role-specific execution and restrictions.
- Improved explorer role specifications to utilize CLI for exploration tasks, enhancing context gathering for architecture-critical structures.
- Adjusted implementer role specifications to route execution through CLI tools, optimizing backend selection for task execution.
- Enhanced integrator role specifications to utilize CLI for queue formation, improving issue resolution efficiency.
- Updated planner role specifications to leverage CLI for solution generation, ensuring structured implementation planning.
- Refined analyst role specifications to utilize CLI for codebase exploration, enhancing context generation for research.
- Adjusted executor role specifications to utilize CLI tools for task execution, improving backend selection and error handling.
- Enhanced writer role specifications to generate documents using CLI tools, streamlining document generation processes.
- Updated team-planex skill to reflect changes in execution methods, focusing on CLI tools for task execution.
- Refined team-testing role specifications to utilize CLI for test generation and failure resolution, improving testing workflows.
- Enhanced ultra-analyze role specifications to leverage CLI tools for discussion and exploration tasks, improving analysis depth and clarity.

.claude/skills/team-issue/role-specs/integrator.md

@@ -34,32 +34,25 @@ Bash("ccw issue solutions <issueId> --json")
 | All issues bound | Proceed to Phase 3 |
 | Any issue unbound | Report error to coordinator, STOP |
 
-## Phase 3: Queue Formation via issue-queue-agent
+## Phase 3: Queue Formation via CLI
 
-**Agent invocation**:
+**CLI invocation**:
 
 ```
-Agent({
-  subagent_type: "issue-queue-agent",
-  run_in_background: false,
-  description: "Form queue for <count> issues",
-  prompt: "
-## Issues to Queue
-Issue IDs: <issueIds>
+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
 
-## Bound Solutions
-<solution list with issue_id, solution_id, task_count>
+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
 
-## Instructions
-1. Load all bound solutions from .workflow/issues/solutions/
-2. Analyze file conflicts between solutions using Gemini CLI
-3. Determine optimal execution order (DAG-based)
-4. Produce ordered execution queue
+MODE: analysis
 
-## Expected Output
-Write queue to: .workflow/issues/queue/execution-queue.json
-"
-})
+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: true })
 ```
 
 **Parse queue result**: