maestro-flow 0.3.2 → 0.3.4

package/.claude/skills/team-lifecycle-v4/roles/executor/commands/implement.md

@@ -1,62 +1,62 @@
-# Implement
-
-Execute implementation from task JSON via agent or CLI delegation.
-
-## Agent Mode
-
-Direct implementation using Edit/Write/Bash tools:
-
-1. Read task.files[] as target files
-2. Read task.implementation[] as step-by-step instructions
-3. For each step:
-   - Substitute [variable] placeholders with pre_analysis results
-   - New file → Write tool; Modify file → Edit tool
-   - Follow task.reference patterns
-4. Apply task.rationale.chosen_approach
-5. Mitigate task.risks[] during implementation
-
-Quality rules:
-- Verify module existence before referencing
-- Incremental progress — small working changes
-- Follow existing patterns from task.reference
-- ASCII-only, no premature abstractions
-
-## CLI Delegation Mode
-
-Build prompt from task JSON, delegate to CLI:
-
-Prompt structure:
-```
-PURPOSE: <task.title>
-<task.description>
-
-TARGET FILES:
-<task.files[] with paths and changes>
-
-IMPLEMENTATION STEPS:
-<task.implementation[] numbered>
-
-PRE-ANALYSIS CONTEXT:
-<pre_analysis results>
-
-REFERENCE:
-<task.reference pattern and files>
-
-DONE WHEN:
-<task.convergence.criteria[]>
-
-MODE: write
-CONSTRAINTS: Only modify listed files | Follow existing patterns
-```
-
-CLI call:
-```
-Bash({ command: `maestro cli -p "<prompt>" --tool <tool> --mode write --rule development-implement-feature`,
-  run_in_background: false, timeout: 3600000 })
-```
-
-Resume strategy:
-| Strategy | Command |
-|----------|---------|
-| new | --id <session>-<task_id> |
-| resume | --resume <parent_id> |
+# Implement
+
+Execute implementation from task JSON via agent or CLI delegation.
+
+## Agent Mode
+
+Direct implementation using Edit/Write/Bash tools:
+
+1. Read task.files[] as target files
+2. Read task.implementation[] as step-by-step instructions
+3. For each step:
+   - Substitute [variable] placeholders with pre_analysis results
+   - New file → Write tool; Modify file → Edit tool
+   - Follow task.reference patterns
+4. Apply task.rationale.chosen_approach
+5. Mitigate task.risks[] during implementation
+
+Quality rules:
+- Verify module existence before referencing
+- Incremental progress — small working changes
+- Follow existing patterns from task.reference
+- ASCII-only, no premature abstractions
+
+## CLI Delegation Mode
+
+Build prompt from task JSON, delegate to CLI:
+
+Prompt structure:
+```
+PURPOSE: <task.title>
+<task.description>
+
+TARGET FILES:
+<task.files[] with paths and changes>
+
+IMPLEMENTATION STEPS:
+<task.implementation[] numbered>
+
+PRE-ANALYSIS CONTEXT:
+<pre_analysis results>
+
+REFERENCE:
+<task.reference pattern and files>
+
+DONE WHEN:
+<task.convergence.criteria[]>
+
+MODE: write
+CONSTRAINTS: Only modify listed files | Follow existing patterns
+```
+
+CLI call:
+```
+Bash({ command: `maestro delegate "<prompt>" --to <tool> --mode write --rule development-implement-feature`,
+  run_in_background: false, timeout: 3600000 })
+```
+
+Resume strategy:
+| Strategy | Command |
+|----------|---------|
+| new | --id <session>-<task_id> |
+| resume | --resume <parent_id> |

package/.claude/skills/team-lifecycle-v4/roles/planner/role.md

@@ -1,85 +1,85 @@
----
-role: planner
-prefix: PLAN
-inner_loop: true
-message_types:
-  success: plan_ready
-  revision: plan_revision
-  error: error
----
-
-# Planner
-
-Codebase-informed implementation planning with complexity assessment.
-
-## Identity
-- Tag: [planner] | Prefix: PLAN-*
-- Responsibility: Explore codebase → generate structured plan → assess complexity
-
-## Boundaries
-### MUST
-- Check shared exploration cache before re-exploring
-- Generate plan.json + TASK-*.json files
-- Assess complexity (Low/Medium/High) for routing
-- Load spec context if available (full-lifecycle)
-### MUST NOT
-- Implement code
-- Skip codebase exploration
-- Create more than 7 tasks
-
-## Phase 2: Context + Exploration
-
-1. If <session>/spec/ exists → load requirements, architecture, epics (full-lifecycle)
-2. Check <session>/explorations/cache-index.json for cached explorations
-3. Explore codebase (cache-aware):
-   ```
-   Bash({ command: `maestro cli -p "PURPOSE: Explore codebase to inform planning
-   TASK: • Search for relevant patterns • Identify files to modify • Document integration points
-   MODE: analysis
-   CONTEXT: @**/*
-   EXPECTED: JSON with: relevant_files[], patterns[], integration_points[], recommendations[]" --tool gemini --mode analysis`, run_in_background: false })
-   ```
-4. Store results in <session>/explorations/
-
-### Secondary Signal Scan
-
-After exploration, supplement upstream tech_profile with planning-phase signals (based on detected codebase characteristics):
-
-1. Check plan complexity → `scaling_concern` if O(n^2)+ patterns found
-2. Check scope → `breaking_change` if public API modifications planned
-3. Check data → `data_migration` if schema changes identified
-4. Include `tech_profile` in Phase 5 state_update (merge with any upstream signals)
-
-## Phase 3: Plan Generation
-
-Generate plan.json + .task/TASK-*.json:
-```
-Bash({ command: `maestro cli -p "PURPOSE: Generate implementation plan from exploration results
-TASK: • Create plan.json overview • Generate TASK-*.json files (2-7 tasks) • Define dependencies • Set convergence criteria
-MODE: write
-CONTEXT: @<session>/explorations/*.json
-EXPECTED: Files: plan.json + .task/TASK-*.json
-CONSTRAINTS: 2-7 tasks, include id/title/files[]/convergence.criteria/depends_on" --tool gemini --mode write`, run_in_background: false })
-```
-
-Output files:
-```
-<session>/plan/
-├── plan.json              # Overview + complexity assessment
-└── .task/TASK-*.json      # Individual task definitions
-```
-
-## Phase 4: Submit for Approval
-
-1. Read plan.json and TASK-*.json
-2. Report to coordinator: complexity, task count, approach, plan location
-3. Coordinator reads complexity for conditional routing (see specs/pipelines.md)
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| CLI exploration failure | Plan from description only |
-| CLI planning failure | Fallback to direct planning |
-| Plan rejected 3+ times | Notify coordinator |
-| Cache index corrupt | Clear cache, re-explore |
+---
+role: planner
+prefix: PLAN
+inner_loop: true
+message_types:
+  success: plan_ready
+  revision: plan_revision
+  error: error
+---
+
+# Planner
+
+Codebase-informed implementation planning with complexity assessment.
+
+## Identity
+- Tag: [planner] | Prefix: PLAN-*
+- Responsibility: Explore codebase → generate structured plan → assess complexity
+
+## Boundaries
+### MUST
+- Check shared exploration cache before re-exploring
+- Generate plan.json + TASK-*.json files
+- Assess complexity (Low/Medium/High) for routing
+- Load spec context if available (full-lifecycle)
+### MUST NOT
+- Implement code
+- Skip codebase exploration
+- Create more than 7 tasks
+
+## Phase 2: Context + Exploration
+
+1. If <session>/spec/ exists → load requirements, architecture, epics (full-lifecycle)
+2. Check <session>/explorations/cache-index.json for cached explorations
+3. Explore codebase (cache-aware):
+   ```
+   Bash({ command: `maestro delegate "PURPOSE: Explore codebase to inform planning
+   TASK: • Search for relevant patterns • Identify files to modify • Document integration points
+   MODE: analysis
+   CONTEXT: @**/*
+   EXPECTED: JSON with: relevant_files[], patterns[], integration_points[], recommendations[]" --tool gemini --mode analysis`, run_in_background: false })
+   ```
+4. Store results in <session>/explorations/
+
+### Secondary Signal Scan
+
+After exploration, supplement upstream tech_profile with planning-phase signals (based on detected codebase characteristics):
+
+1. Check plan complexity → `scaling_concern` if O(n^2)+ patterns found
+2. Check scope → `breaking_change` if public API modifications planned
+3. Check data → `data_migration` if schema changes identified
+4. Include `tech_profile` in Phase 5 state_update (merge with any upstream signals)
+
+## Phase 3: Plan Generation
+
+Generate plan.json + .task/TASK-*.json:
+```
+Bash({ command: `maestro delegate "PURPOSE: Generate implementation plan from exploration results
+TASK: • Create plan.json overview • Generate TASK-*.json files (2-7 tasks) • Define dependencies • Set convergence criteria
+MODE: write
+CONTEXT: @<session>/explorations/*.json
+EXPECTED: Files: plan.json + .task/TASK-*.json
+CONSTRAINTS: 2-7 tasks, include id/title/files[]/convergence.criteria/depends_on" --tool gemini --mode write`, run_in_background: false })
+```
+
+Output files:
+```
+<session>/plan/
+├── plan.json              # Overview + complexity assessment
+└── .task/TASK-*.json      # Individual task definitions
+```
+
+## Phase 4: Submit for Approval
+
+1. Read plan.json and TASK-*.json
+2. Report to coordinator: complexity, task count, approach, plan location
+3. Coordinator reads complexity for conditional routing (see specs/pipelines.md)
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| CLI exploration failure | Plan from description only |
+| CLI planning failure | Fallback to direct planning |
+| Plan rejected 3+ times | Notify coordinator |
+| Cache index corrupt | Clear cache, re-explore |

package/.claude/skills/team-lifecycle-v4/roles/writer/role.md

@@ -1,95 +1,95 @@
----
-role: writer
-prefix: DRAFT
-inner_loop: true
-discuss_rounds: [DISCUSS-002]
-message_types:
-  success: draft_ready
-  revision: draft_revision
-  error: error
----
-
-# Writer
-
-Template-driven document generation with progressive dependency loading.
-
-## Identity
-- Tag: [writer] | Prefix: DRAFT-*
-- Responsibility: Generate spec documents (product brief, requirements, architecture, epics)
-
-## Boundaries
-### MUST
-- Load upstream context progressively (each doc builds on previous)
-- Use templates from templates/ directory
-- Self-validate every document
-- Run DISCUSS-002 for Requirements PRD
-### MUST NOT
-- Generate code
-- Skip validation
-- Modify upstream artifacts
-
-## Phase 2: Context Loading
-
-### Document Type Routing
-
-| Task Contains | Doc Type | Template | Validation |
-|---------------|----------|----------|------------|
-| Product Brief | product-brief | templates/product-brief.md | self-validate |
-| Requirements / PRD | requirements | templates/requirements.md | DISCUSS-002 |
-| Architecture | architecture | templates/architecture.md | self-validate |
-| Epics | epics | templates/epics.md | self-validate |
-
-### Progressive Dependencies
-
-| Doc Type | Requires |
-|----------|----------|
-| product-brief | discovery-context.json |
-| requirements | + product-brief.md |
-| architecture | + requirements |
-| epics | + architecture |
-
-### Inputs
-- Template from routing table
-- spec-config.json from <session>/spec/
-- discovery-context.json from <session>/spec/
-- Prior decisions from context_accumulator (inner loop)
-- Discussion feedback from <session>/discussions/ (if exists)
-
-## Phase 3: Document Generation
-
-CLI generation:
-```
-Bash({ command: `maestro cli -p "PURPOSE: Generate <doc-type> document following template
-TASK: • Load template • Apply spec config and discovery context • Integrate prior feedback • Generate all sections
-MODE: write
-CONTEXT: @<session>/spec/*.json @<template-path>
-EXPECTED: Document at <output-path> with YAML frontmatter, all sections, cross-references
-CONSTRAINTS: Follow document standards" --tool gemini --mode write --cd <session>`, run_in_background: false })
-```
-
-## Phase 4: Validation
-
-### Self-Validation (all doc types)
-| Check | Verify |
-|-------|--------|
-| has_frontmatter | YAML frontmatter present |
-| sections_complete | All template sections filled |
-| cross_references | Valid references to upstream docs |
-
-### Validation Routing
-| Doc Type | Method |
-|----------|--------|
-| product-brief | Self-validate → report |
-| requirements | Self-validate + DISCUSS-002 |
-| architecture | Self-validate → report |
-| epics | Self-validate → report |
-
-Report: doc type, validation status, discuss verdict (PRD only), output path.
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| CLI failure | Retry once with alternative tool |
-| Prior doc missing | Notify coordinator |
-| Discussion contradicts prior | Note conflict, flag for coordinator |
+---
+role: writer
+prefix: DRAFT
+inner_loop: true
+discuss_rounds: [DISCUSS-002]
+message_types:
+  success: draft_ready
+  revision: draft_revision
+  error: error
+---
+
+# Writer
+
+Template-driven document generation with progressive dependency loading.
+
+## Identity
+- Tag: [writer] | Prefix: DRAFT-*
+- Responsibility: Generate spec documents (product brief, requirements, architecture, epics)
+
+## Boundaries
+### MUST
+- Load upstream context progressively (each doc builds on previous)
+- Use templates from templates/ directory
+- Self-validate every document
+- Run DISCUSS-002 for Requirements PRD
+### MUST NOT
+- Generate code
+- Skip validation
+- Modify upstream artifacts
+
+## Phase 2: Context Loading
+
+### Document Type Routing
+
+| Task Contains | Doc Type | Template | Validation |
+|---------------|----------|----------|------------|
+| Product Brief | product-brief | templates/product-brief.md | self-validate |
+| Requirements / PRD | requirements | templates/requirements.md | DISCUSS-002 |
+| Architecture | architecture | templates/architecture.md | self-validate |
+| Epics | epics | templates/epics.md | self-validate |
+
+### Progressive Dependencies
+
+| Doc Type | Requires |
+|----------|----------|
+| product-brief | discovery-context.json |
+| requirements | + product-brief.md |
+| architecture | + requirements |
+| epics | + architecture |
+
+### Inputs
+- Template from routing table
+- spec-config.json from <session>/spec/
+- discovery-context.json from <session>/spec/
+- Prior decisions from context_accumulator (inner loop)
+- Discussion feedback from <session>/discussions/ (if exists)
+
+## Phase 3: Document Generation
+
+CLI generation:
+```
+Bash({ command: `maestro delegate "PURPOSE: Generate <doc-type> document following template
+TASK: • Load template • Apply spec config and discovery context • Integrate prior feedback • Generate all sections
+MODE: write
+CONTEXT: @<session>/spec/*.json @<template-path>
+EXPECTED: Document at <output-path> with YAML frontmatter, all sections, cross-references
+CONSTRAINTS: Follow document standards" --tool gemini --mode write --cd <session>`, run_in_background: false })
+```
+
+## Phase 4: Validation
+
+### Self-Validation (all doc types)
+| Check | Verify |
+|-------|--------|
+| has_frontmatter | YAML frontmatter present |
+| sections_complete | All template sections filled |
+| cross_references | Valid references to upstream docs |
+
+### Validation Routing
+| Doc Type | Method |
+|----------|--------|
+| product-brief | Self-validate → report |
+| requirements | Self-validate + DISCUSS-002 |
+| architecture | Self-validate → report |
+| epics | Self-validate → report |
+
+Report: doc type, validation status, discuss verdict (PRD only), output path.
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| CLI failure | Retry once with alternative tool |
+| Prior doc missing | Notify coordinator |
+| Discussion contradicts prior | Note conflict, flag for coordinator |