maestro-flow 0.5.36 → 0.5.37

package/.claude/skills/team-ultra-analyze/roles/discussant/role.md

@@ -1,107 +1,107 @@
----
-role: discussant
-prefix: DISCUSS
-inner_loop: false
-message_types:
-  success: discussion_processed
-  error: error
----
-
-# Discussant
-
-Process analysis results and user feedback. Execute direction adjustments, deep-dive explorations, or targeted Q&A based on discussion type. Update discussion timeline.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Analysis results | `<session>/analyses/*.json` | Yes |
-| Exploration results | `<session>/explorations/*.json` | No |
-
-1. Extract session path, topic, round, discussion type, user feedback:
-
-| Field | Pattern | Default |
-|-------|---------|---------|
-| sessionFolder | `session:\s*(.+)` | required |
-| topic | `topic:\s*(.+)` | required |
-| round | `round:\s*(\d+)` | 1 |
-| discussType | `type:\s*(.+)` | "initial" |
-| userFeedback | `user_feedback:\s*(.+)` | empty |
-
-2. Read all analysis and exploration results
-3. Aggregate current findings, insights, open questions
-
-## Phase 3: Discussion Processing
-
-Select strategy by discussion type:
-
-| Type | Mode | Description |
-|------|------|-------------|
-| initial | inline | Aggregate all analyses: convergent themes, conflicts, top discussion points |
-| deepen | cli | Use CLI tool to investigate open questions deeper |
-| direction-adjusted | cli | Re-analyze via `maestro delegate` from adjusted perspective |
-| specific-questions | cli | Targeted exploration answering user questions |
-
-**initial**: Cross-perspective summary -- identify convergent themes, conflicting views, top 5 discussion points and open questions from all analyses.
-
-**deepen**: Use CLI tool for deep investigation:
-```javascript
-Bash({
-  command: `maestro delegate "PURPOSE: Investigate open questions and uncertain insights; success = evidence-based findings
-TASK: • Focus on open questions: <questions> • Find supporting evidence • Validate uncertain insights • Document findings
-MODE: analysis
-CONTEXT: @**/* | Memory: Session <session-folder>, previous analyses
-EXPECTED: JSON output with investigation results | Write to <session>/discussions/deepen-<num>.json
-CONSTRAINTS: Evidence-based analysis only
-" --tool gemini --mode analysis --rule analysis-trace-code-execution`,
-  run_in_background: false
-})
-```
-
-**direction-adjusted**: CLI re-analysis from adjusted focus:
-```javascript
-Bash({
-  command: `maestro delegate "Re-analyze '<topic>' with adjusted focus on '<userFeedback>'" --to gemini --mode analysis`,
-  run_in_background: false
-})
-```
-
-**specific-questions**: Use CLI tool for targeted Q&A:
-```javascript
-Bash({
-  command: `maestro delegate "PURPOSE: Answer specific user questions about <topic>; success = clear, evidence-based answers
-TASK: • Answer: <userFeedback> • Provide code references • Explain context
-MODE: analysis
-CONTEXT: @**/* | Memory: Session <session-folder>
-EXPECTED: JSON output with answers and evidence | Write to <session>/discussions/questions-<num>.json
-CONSTRAINTS: Direct answers with code references
-" --tool gemini --mode analysis`,
-  run_in_background: false
-})
-```
-
-## Phase 4: Update Discussion Timeline
-
-1. Write round content to `<session>/discussions/discussion-round-<num>.json`:
-```json
-{
-  "round": 1, "type": "initial", "user_feedback": "...",
-  "updated_understanding": { "confirmed": [], "corrected": [], "new_insights": [] },
-  "new_findings": [], "new_questions": [], "timestamp": "..."
-}
-```
-
-2. Append round section to `<session>/discussion.md`:
-```markdown
-### Round <N> - Discussion (<timestamp>)
-#### Type: <discussType>
-#### User Input: <userFeedback or "(Initial discussion round)">
-#### Updated Understanding
-**Confirmed**: <list> | **Corrected**: <list> | **New Insights**: <list>
-#### New Findings / Open Questions
-```
-
-Update `<session>/wisdom/.msg/meta.json` under `discussant` namespace:
-- Read existing -> merge `{ "discussant": { round, type, new_insight_count, corrected_count } }` -> write back
+---
+role: discussant
+prefix: DISCUSS
+inner_loop: false
+message_types:
+  success: discussion_processed
+  error: error
+---
+
+# Discussant
+
+Process analysis results and user feedback. Execute direction adjustments, deep-dive explorations, or targeted Q&A based on discussion type. Update discussion timeline.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Analysis results | `<session>/analyses/*.json` | Yes |
+| Exploration results | `<session>/explorations/*.json` | No |
+
+1. Extract session path, topic, round, discussion type, user feedback:
+
+| Field | Pattern | Default |
+|-------|---------|---------|
+| sessionFolder | `session:\s*(.+)` | required |
+| topic | `topic:\s*(.+)` | required |
+| round | `round:\s*(\d+)` | 1 |
+| discussType | `type:\s*(.+)` | "initial" |
+| userFeedback | `user_feedback:\s*(.+)` | empty |
+
+2. Read all analysis and exploration results
+3. Aggregate current findings, insights, open questions
+
+## Phase 3: Discussion Processing
+
+Select strategy by discussion type:
+
+| Type | Mode | Description |
+|------|------|-------------|
+| initial | inline | Aggregate all analyses: convergent themes, conflicts, top discussion points |
+| deepen | cli | Use CLI tool to investigate open questions deeper |
+| direction-adjusted | cli | Re-analyze via `maestro delegate` from adjusted perspective |
+| specific-questions | cli | Targeted exploration answering user questions |
+
+**initial**: Cross-perspective summary -- identify convergent themes, conflicting views, top 5 discussion points and open questions from all analyses.
+
+**deepen**: Use CLI tool for deep investigation:
+```javascript
+Bash({
+  command: `maestro delegate "PURPOSE: Investigate open questions and uncertain insights; success = evidence-based findings
+TASK: • Focus on open questions: <questions> • Find supporting evidence • Validate uncertain insights • Document findings
+MODE: analysis
+CONTEXT: @**/* | Memory: Session <session-folder>, previous analyses
+EXPECTED: JSON output with investigation results | Write to <session>/discussions/deepen-<num>.json
+CONSTRAINTS: Evidence-based analysis only
+" --tool agy --mode analysis --rule analysis-trace-code-execution`,
+  run_in_background: false
+})
+```
+
+**direction-adjusted**: CLI re-analysis from adjusted focus:
+```javascript
+Bash({
+  command: `maestro delegate "Re-analyze '<topic>' with adjusted focus on '<userFeedback>'" --to agy --mode analysis`,
+  run_in_background: false
+})
+```
+
+**specific-questions**: Use CLI tool for targeted Q&A:
+```javascript
+Bash({
+  command: `maestro delegate "PURPOSE: Answer specific user questions about <topic>; success = clear, evidence-based answers
+TASK: • Answer: <userFeedback> • Provide code references • Explain context
+MODE: analysis
+CONTEXT: @**/* | Memory: Session <session-folder>
+EXPECTED: JSON output with answers and evidence | Write to <session>/discussions/questions-<num>.json
+CONSTRAINTS: Direct answers with code references
+" --tool agy --mode analysis`,
+  run_in_background: false
+})
+```
+
+## Phase 4: Update Discussion Timeline
+
+1. Write round content to `<session>/discussions/discussion-round-<num>.json`:
+```json
+{
+  "round": 1, "type": "initial", "user_feedback": "...",
+  "updated_understanding": { "confirmed": [], "corrected": [], "new_insights": [] },
+  "new_findings": [], "new_questions": [], "timestamp": "..."
+}
+```
+
+2. Append round section to `<session>/discussion.md`:
+```markdown
+### Round <N> - Discussion (<timestamp>)
+#### Type: <discussType>
+#### User Input: <userFeedback or "(Initial discussion round)">
+#### Updated Understanding
+**Confirmed**: <list> | **Corrected**: <list> | **New Insights**: <list>
+#### New Findings / Open Questions
+```
+
+Update `<session>/wisdom/.msg/meta.json` under `discussant` namespace:
+- Read existing -> merge `{ "discussant": { round, type, new_insight_count, corrected_count } }` -> write back

package/.claude/skills/team-ultra-analyze/roles/explorer/role.md

@@ -1,82 +1,82 @@
----
-role: explorer
-prefix: EXPLORE
-inner_loop: false
-message_types:
-  success: exploration_ready
-  error: error
----
-
-# Codebase Explorer
-
-Explore codebase structure through cli-explore-agent, collecting structured context (files, patterns, findings) for downstream analysis. One explorer per analysis perspective.
-
-## Phase 2: Context & Scope Assessment
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-
-1. Load debug specs: Run `ccw spec load --category debug` for known issues and root-cause notes
-2. Extract session path, topic, perspective, dimensions from task description:
-
-| Field | Pattern | Default |
-|-------|---------|---------|
-| sessionFolder | `session:\s*(.+)` | required |
-| topic | `topic:\s*(.+)` | required |
-| perspective | `perspective:\s*(.+)` | "general" |
-| dimensions | `dimensions:\s*(.+)` | "general" |
-
-2. Determine exploration number from task subject (EXPLORE-N)
-3. Build exploration strategy by perspective:
-
-| Perspective | Focus | Search Depth |
-|-------------|-------|-------------|
-| general | Overall codebase structure and patterns | broad |
-| technical | Implementation details, code patterns, feasibility | medium |
-| architectural | System design, module boundaries, interactions | broad |
-| business | Business logic, domain models, value flows | medium |
-| domain_expert | Domain patterns, standards, best practices | deep |
-
-## Phase 3: Codebase Exploration
-
-**Primary: `maestro explore`** (structured multi-prompt):
-
-```bash
-maestro explore \
-  "FIND: <topic> patterns and implementations
-SCOPE: src/
-ATTENTION: <perspective>-specific concerns
-EXPECTED: file:line evidence with relevance" \
-  "FIND: module boundaries and relationships for <topic>
-SCOPE: src/
-EXCLUDE: tests, generated code
-EXPECTED: dependency pairs and architectural insights" \
-  --max-turns 3 --json
-```
-
-Parse JSON results → extract relevant_files, patterns, key_findings.
-
-**Fallback: `maestro delegate`** (when explore results insufficient):
-
-```bash
-maestro delegate "PURPOSE: Explore codebase for <topic> from <perspective> perspective
-TASK: Search for topic-related patterns | Identify key files and relationships | Extract architectural insights
-EXPECTED: JSON with relevant_files, patterns, key_findings
-CONSTRAINTS: Focus on <perspective> angle
-" --tool gemini --mode analysis --rule analysis-analyze-code-patterns
-```
-
-## Phase 4: Result Validation
-
-| Check | Method | Action on Failure |
-|-------|--------|-------------------|
-| Output file exists | Read output path | Create empty result, run ACE fallback |
-| Has relevant_files | Array length > 0 | Trigger ACE supplementary search |
-| Has key_findings | Array length > 0 | Note partial results, proceed |
-
-Write validated exploration to `<session>/explorations/exploration-<num>.json`.
-
-Update `<session>/wisdom/.msg/meta.json` under `explorer` namespace:
-- Read existing -> merge `{ "explorer": { perspective, file_count, finding_count } }` -> write back
+---
+role: explorer
+prefix: EXPLORE
+inner_loop: false
+message_types:
+  success: exploration_ready
+  error: error
+---
+
+# Codebase Explorer
+
+Explore codebase structure through cli-explore-agent, collecting structured context (files, patterns, findings) for downstream analysis. One explorer per analysis perspective.
+
+## Phase 2: Context & Scope Assessment
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+
+1. Load debug specs: Run `ccw spec load --category debug` for known issues and root-cause notes
+2. Extract session path, topic, perspective, dimensions from task description:
+
+| Field | Pattern | Default |
+|-------|---------|---------|
+| sessionFolder | `session:\s*(.+)` | required |
+| topic | `topic:\s*(.+)` | required |
+| perspective | `perspective:\s*(.+)` | "general" |
+| dimensions | `dimensions:\s*(.+)` | "general" |
+
+2. Determine exploration number from task subject (EXPLORE-N)
+3. Build exploration strategy by perspective:
+
+| Perspective | Focus | Search Depth |
+|-------------|-------|-------------|
+| general | Overall codebase structure and patterns | broad |
+| technical | Implementation details, code patterns, feasibility | medium |
+| architectural | System design, module boundaries, interactions | broad |
+| business | Business logic, domain models, value flows | medium |
+| domain_expert | Domain patterns, standards, best practices | deep |
+
+## Phase 3: Codebase Exploration
+
+**Primary: `maestro explore`** (structured multi-prompt):
+
+```bash
+maestro explore \
+  "FIND: <topic> patterns and implementations
+SCOPE: src/
+ATTENTION: <perspective>-specific concerns
+EXPECTED: file:line evidence with relevance" \
+  "FIND: module boundaries and relationships for <topic>
+SCOPE: src/
+EXCLUDE: tests, generated code
+EXPECTED: dependency pairs and architectural insights" \
+  --max-turns 3 --json
+```
+
+Parse JSON results → extract relevant_files, patterns, key_findings.
+
+**Fallback: `maestro delegate`** (when explore results insufficient):
+
+```bash
+maestro delegate "PURPOSE: Explore codebase for <topic> from <perspective> perspective
+TASK: Search for topic-related patterns | Identify key files and relationships | Extract architectural insights
+EXPECTED: JSON with relevant_files, patterns, key_findings
+CONSTRAINTS: Focus on <perspective> angle
+" --tool agy --mode analysis --rule analysis-analyze-code-patterns
+```
+
+## Phase 4: Result Validation
+
+| Check | Method | Action on Failure |
+|-------|--------|-------------------|
+| Output file exists | Read output path | Create empty result, run ACE fallback |
+| Has relevant_files | Array length > 0 | Trigger ACE supplementary search |
+| Has key_findings | Array length > 0 | Note partial results, proceed |
+
+Write validated exploration to `<session>/explorations/exploration-<num>.json`.
+
+Update `<session>/wisdom/.msg/meta.json` under `explorer` namespace:
+- Read existing -> merge `{ "explorer": { perspective, file_count, finding_count } }` -> write back

package/.claude/skills/team-ultra-analyze/roles/synthesizer/role.md

@@ -1,78 +1,78 @@
----
-role: synthesizer
-prefix: SYNTH
-inner_loop: false
-message_types:
-  success: synthesis_ready
-  error: error
----
-
-# Synthesizer
-
-Integrate all explorations, analyses, and discussions into final conclusions. Cross-perspective theme extraction, conflict resolution, evidence consolidation, and recommendation prioritization. Pure integration role -- no external tools or CLI calls.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| All artifacts | `<session>/explorations/*.json`, `analyses/*.json`, `discussions/*.json` | Yes |
-| Decision trail | From wisdom/.msg/meta.json | No |
-
-1. Extract session path and topic from task description
-2. Read all exploration, analysis, and discussion round files
-3. Load decision trail and current understanding from meta.json
-4. Select synthesis strategy:
-
-| Condition | Strategy |
-|-----------|----------|
-| Single analysis, no discussions | simple (Quick mode summary) |
-| Multiple analyses, >2 discussion rounds | deep (track evolution) |
-| Default | standard (cross-perspective integration) |
-
-## Phase 3: Cross-Perspective Synthesis
-
-Execute synthesis across four dimensions:
-
-**1. Theme Extraction**: Identify convergent themes across all analysis perspectives. Cluster insights by similarity, rank by cross-perspective confirmation count.
-
-**2. Conflict Resolution**: Identify contradictions between perspectives. Present both sides with trade-off analysis when irreconcilable.
-
-**3. Evidence Consolidation**: Deduplicate findings, aggregate by file reference. Map evidence to conclusions with confidence levels:
-
-| Level | Criteria |
-|-------|----------|
-| High | Multiple sources confirm, strong evidence |
-| Medium | Single source or partial evidence |
-| Low | Speculative, needs verification |
-
-**4. Recommendation Prioritization**: Sort all recommendations by priority (high > medium > low), deduplicate, cap at 10.
-
-Integrate decision trail from discussion rounds into final narrative.
-
-## Phase 4: Write Conclusions
-
-1. Write `<session>/conclusions.json`:
-```json
-{
-  "session_id": "...", "topic": "...", "completed": "ISO-8601",
-  "summary": "Executive summary...",
-  "key_conclusions": [{"point": "...", "evidence": "...", "confidence": "high"}],
-  "recommendations": [{"action": "...", "rationale": "...", "priority": "high"}],
-  "open_questions": ["..."],
-  "decision_trail": [{"round": 1, "decision": "...", "context": "..."}],
-  "cross_perspective_synthesis": { "convergent_themes": [], "conflicts_resolved": [], "unique_contributions": [] },
-  "_metadata": { "explorations": 3, "analyses": 3, "discussions": 2, "strategy": "standard" }
-}
-```
-
-2. Append conclusions section to `<session>/discussion.md`:
-```markdown
-## Conclusions
-### Summary / Key Conclusions / Recommendations / Remaining Questions
-## Decision Trail / Current Understanding (Final) / Session Statistics
-```
-
-Update `<session>/wisdom/.msg/meta.json` under `synthesizer` namespace:
-- Read existing -> merge `{ "synthesizer": { conclusion_count, recommendation_count, open_question_count } }` -> write back
+---
+role: synthesizer
+prefix: SYNTH
+inner_loop: false
+message_types:
+  success: synthesis_ready
+  error: error
+---
+
+# Synthesizer
+
+Integrate all explorations, analyses, and discussions into final conclusions. Cross-perspective theme extraction, conflict resolution, evidence consolidation, and recommendation prioritization. Pure integration role -- no external tools or CLI calls.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| All artifacts | `<session>/explorations/*.json`, `analyses/*.json`, `discussions/*.json` | Yes |
+| Decision trail | From wisdom/.msg/meta.json | No |
+
+1. Extract session path and topic from task description
+2. Read all exploration, analysis, and discussion round files
+3. Load decision trail and current understanding from meta.json
+4. Select synthesis strategy:
+
+| Condition | Strategy |
+|-----------|----------|
+| Single analysis, no discussions | simple (Quick mode summary) |
+| Multiple analyses, >2 discussion rounds | deep (track evolution) |
+| Default | standard (cross-perspective integration) |
+
+## Phase 3: Cross-Perspective Synthesis
+
+Execute synthesis across four dimensions:
+
+**1. Theme Extraction**: Identify convergent themes across all analysis perspectives. Cluster insights by similarity, rank by cross-perspective confirmation count.
+
+**2. Conflict Resolution**: Identify contradictions between perspectives. Present both sides with trade-off analysis when irreconcilable.
+
+**3. Evidence Consolidation**: Deduplicate findings, aggregate by file reference. Map evidence to conclusions with confidence levels:
+
+| Level | Criteria |
+|-------|----------|
+| High | Multiple sources confirm, strong evidence |
+| Medium | Single source or partial evidence |
+| Low | Speculative, needs verification |
+
+**4. Recommendation Prioritization**: Sort all recommendations by priority (high > medium > low), deduplicate, cap at 10.
+
+Integrate decision trail from discussion rounds into final narrative.
+
+## Phase 4: Write Conclusions
+
+1. Write `<session>/conclusions.json`:
+```json
+{
+  "session_id": "...", "topic": "...", "completed": "ISO-8601",
+  "summary": "Executive summary...",
+  "key_conclusions": [{"point": "...", "evidence": "...", "confidence": "high"}],
+  "recommendations": [{"action": "...", "rationale": "...", "priority": "high"}],
+  "open_questions": ["..."],
+  "decision_trail": [{"round": 1, "decision": "...", "context": "..."}],
+  "cross_perspective_synthesis": { "convergent_themes": [], "conflicts_resolved": [], "unique_contributions": [] },
+  "_metadata": { "explorations": 3, "analyses": 3, "discussions": 2, "strategy": "standard" }
+}
+```
+
+2. Append conclusions section to `<session>/discussion.md`:
+```markdown
+## Conclusions
+### Summary / Key Conclusions / Recommendations / Remaining Questions
+## Decision Trail / Current Understanding (Final) / Session Statistics
+```
+
+Update `<session>/wisdom/.msg/meta.json` under `synthesizer` namespace:
+- Read existing -> merge `{ "synthesizer": { conclusion_count, recommendation_count, open_question_count } }` -> write back