maestro-flow 0.5.36 → 0.5.37

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

@@ -1,87 +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
+---
+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/Agy), 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>` |
+| agy | task_count <= 3 or explicit | `maestro delegate --to agy --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|Agy|Qwen|Auto`) | Yes |
+| Code review | Task description (`code_review: Skip|Agy 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 -> agy, 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 })`
+- **agy**: `Bash("maestro delegate \\\"<prompt>\" --to agy --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

@@ -1,84 +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
+---
+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 agy --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

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

@@ -1,81 +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("maestro delegate \\\"
-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", { run_in_background: false })
-```
-
-**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
+---
+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("maestro delegate \\\"
+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 agy --mode analysis", { run_in_background: false })
+```
+
+**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