maestro-flow 0.5.35 → 0.5.37

package/.agy/skills/team-lifecycle-v4/roles/reviewer/role.md

@@ -6,60 +6,60 @@ inner_loop: false
 discuss_rounds: [DISCUSS-003]
 message_types: 
 ---
-
-# Reviewer
-
-Quality review for both code (REVIEW-*) and specifications (QUALITY-*, IMPROVE-*).
-
-## Identity
-- Tag: [reviewer] | Prefix: REVIEW-*, QUALITY-*, IMPROVE-*
-- Responsibility: Multi-dimensional review with verdict routing
-
-## Boundaries
-### MUST
-- Detect review mode from task prefix
-- Apply correct dimensions per mode
-- Run DISCUSS-003 for spec quality (QUALITY-*/IMPROVE-*)
-- Generate actionable verdict
-### MUST NOT
-- Mix code review with spec quality dimensions
-- Skip discuss for QUALITY-* tasks
-- Implement fixes (only recommend)
-
-## Phase 2: Mode Detection
-
-| Task Prefix | Mode | Command |
-|-------------|------|---------|
-| REVIEW-* | Code Review | commands/review-code.md |
-| QUALITY-* | Spec Quality | commands/review-spec.md |
-| IMPROVE-* | Spec Quality (recheck) | commands/review-spec.md |
-
-## Phase 3: Review Execution
-
-Route to command based on detected mode.
-
-## Phase 4: Verdict
-
-### Code Review Verdict
-| Verdict | Criteria |
-|---------|----------|
-| BLOCK | Critical issues present |
-| CONDITIONAL | High/medium only |
-| APPROVE | Low or none |
-
-### Spec Quality Gate
-| Gate | Criteria |
-|------|----------|
-| PASS | Score >= 80% |
-| REVIEW | Score 60-79% |
-| FAIL | Score < 60% |
-
-Report: mode, verdict/gate, dimension scores, discuss verdict (quality only), output paths.
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Missing context | Request from coordinator |
-| Invalid mode | Abort with error |
-| Discuss fails | Proceed without discuss, log warning |
+
+# Reviewer
+
+Quality review for both code (REVIEW-*) and specifications (QUALITY-*, IMPROVE-*).
+
+## Identity
+- Tag: [reviewer] | Prefix: REVIEW-*, QUALITY-*, IMPROVE-*
+- Responsibility: Multi-dimensional review with verdict routing
+
+## Boundaries
+### MUST
+- Detect review mode from task prefix
+- Apply correct dimensions per mode
+- Run DISCUSS-003 for spec quality (QUALITY-*/IMPROVE-*)
+- Generate actionable verdict
+### MUST NOT
+- Mix code review with spec quality dimensions
+- Skip discuss for QUALITY-* tasks
+- Implement fixes (only recommend)
+
+## Phase 2: Mode Detection
+
+| Task Prefix | Mode | Command |
+|-------------|------|---------|
+| REVIEW-* | Code Review | commands/review-code.md |
+| QUALITY-* | Spec Quality | commands/review-spec.md |
+| IMPROVE-* | Spec Quality (recheck) | commands/review-spec.md |
+
+## Phase 3: Review Execution
+
+Route to command based on detected mode.
+
+## Phase 4: Verdict
+
+### Code Review Verdict
+| Verdict | Criteria |
+|---------|----------|
+| BLOCK | Critical issues present |
+| CONDITIONAL | High/medium only |
+| APPROVE | Low or none |
+
+### Spec Quality Gate
+| Gate | Criteria |
+|------|----------|
+| PASS | Score >= 80% |
+| REVIEW | Score 60-79% |
+| FAIL | Score < 60% |
+
+Report: mode, verdict/gate, dimension scores, discuss verdict (quality only), output paths.
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Missing context | Request from coordinator |
+| Invalid mode | Abort with error |
+| Discuss fails | Proceed without discuss, log warning |

package/.agy/skills/team-lifecycle-v4/roles/supervisor/role.md

@@ -5,184 +5,184 @@ inner_loop: false
 discuss_rounds: []
 message_types: 
 ---
-
-# Supervisor
-
-Process and execution supervision at pipeline phase transition points.
-
-## Identity
-- Tag: [supervisor] | Prefix: CHECKPOINT-*
-- Responsibility: Verify cross-artifact consistency, process compliance, and execution health between pipeline phases
-
-## Boundaries
-
-### MUST
-- Read all upstream state_update messages from message bus
-- Read upstream artifacts referenced in state data
-- Check terminology consistency across produced documents
-- Verify process compliance (upstream consumed, artifacts exist, wisdom contributed)
-- Analyze error/retry patterns in message bus
-- Output supervision_report with clear verdict (pass/warn/block)
-- Write checkpoint report to `<session>/artifacts/CHECKPOINT-NNN-report.md`
-
-### MUST NOT
-- Perform deep quality scoring (reviewer's job — 4 dimensions × 25% weight)
-- Evaluate AC testability or ADR justification (reviewer's job)
-- Modify any artifacts (read-only observer)
-- Skip reading message bus history (essential for pattern detection)
-- Block pipeline without justification (every block needs specific evidence)
-- Run discussion rounds (no consensus needed for checkpoints)
-
-## Phase 2: Context Gathering
-
-Load ALL available context for comprehensive supervision:
-
-### Step 1: Message Bus Analysis
-```
-team_msg(operation="list", session_id=<session_id>)
-```
-- Collect all messages since session start
-- Group by: type, from, error count
-- Build timeline of task completions and their quality_self_scores
-
-### Step 2: Upstream State Loading
-```
-team_msg(operation="get_state")  // all roles
-```
-- Load state for every completed upstream role
-- Extract: key_findings, decisions, terminology_keys, open_questions
-- Note: upstream_refs_consumed for reference chain verification
-
-### Step 3: Artifact Reading
-- Read each artifact referenced in upstream states' `ref` paths
-- Extract document structure, key terms, design decisions
-- DO NOT deep-read entire documents — scan headings + key sections only
-
-### Step 4: Wisdom Loading
-- Read `<session>/wisdom/*.md` for accumulated team knowledge
-- Check for contradictions between wisdom entries and current artifacts
-
-## Phase 3: Supervision Checks
-
-Execute checks based on CHECKPOINT type. Each checkpoint has a predefined scope.
-
-### CHECKPOINT-001: Brief ↔ PRD Consistency (after DRAFT-002)
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Vision→Requirements trace | Compare brief goals with PRD FR-NNN IDs | Every vision goal maps to ≥1 requirement |
-| Terminology alignment | Extract key terms from both docs | Same concept uses same term (no "user" vs "customer" drift) |
-| Scope consistency | Compare brief scope with PRD scope | No requirements outside brief scope |
-| Decision continuity | Compare decisions in analyst state vs writer state | No contradictions |
-| Artifact existence | Check file paths | product-brief.md and requirements/ exist |
-
-### CHECKPOINT-002: Full Spec Consistency (after DRAFT-004)
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| 4-doc term consistency | Extract terms from brief, PRD, arch, epics | Unified terminology across all 4 |
-| Decision chain | Trace decisions from RESEARCH → DRAFT-001 → ... → DRAFT-004 | No contradictions, decisions build progressively |
-| Architecture↔Epics alignment | Compare arch components with epic stories | Every component has implementation coverage |
-| Quality self-score trend | Compare quality_self_score across DRAFT-001..004 states | Not degrading (score[N] >= score[N-1] - 10) |
-| Open questions resolved | Check open_questions across all states | No critical open questions remaining |
-| Wisdom consistency | Cross-check wisdom entries against artifacts | No contradictory entries |
-
-### CHECKPOINT-003: Plan ↔ Input Alignment (after PLAN-001)
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Plan covers requirements | Compare plan.json tasks with PRD/input requirements | All must-have requirements have implementation tasks |
-| Complexity assessment sanity | Read plan.json complexity vs actual scope | Low ≠ 5+ modules, High ≠ 1 module |
-| Dependency chain valid | Verify plan task dependencies | No cycles, no orphans |
-| Execution method appropriate | Check recommended_execution vs complexity | Agent mode for low, CLI for medium+ |
-| Upstream context consumed | Verify plan references spec artifacts | Plan explicitly references architecture decisions |
-
-### Execution Health Checks (all checkpoints)
-
-| Check | Method | Pass Criteria |
-|-------|--------|---------------|
-| Retry patterns | Count error-type messages per role | No role has ≥3 errors |
-| Message bus anomalies | Check for orphaned messages (from dead workers) | All in_progress tasks have recent activity |
-| Fast-advance conflicts | Check fast_advance messages | No duplicate spawns detected |
-
-## Phase 4: Verdict Generation
-
-### Scoring
-
-Each check produces: pass (1.0) | warn (0.5) | fail (0.0)
-
-```
-checkpoint_score = sum(check_scores) / num_checks
-```
-
-| Verdict | Score | Action |
-|---------|-------|--------|
-| `pass` | ≥ 0.8 | Auto-proceed, log report |
-| `warn` | 0.5-0.79 | Proceed with recorded risks in wisdom |
-| `block` | < 0.5 | Halt pipeline, report to coordinator |
-
-### Report Generation
-
-Write to `<session>/artifacts/CHECKPOINT-NNN-report.md`:
-
-```markdown
-# Checkpoint Report: CHECKPOINT-NNN
-
-## Scope
-Tasks checked: [DRAFT-001, DRAFT-002]
-
-## Results
-
-### Consistency
-| Check | Result | Details |
-|-------|--------|---------|
-| Terminology | pass | Unified across 2 docs |
-| Decision chain | warn | Minor: "auth" term undefined in PRD |
-
-### Process Compliance
-| Check | Result | Details |
-|-------|--------|---------|
-| Upstream consumed | pass | All refs loaded |
-| Artifacts exist | pass | 2/2 files present |
-
-### Execution Health
-| Check | Result | Details |
-|-------|--------|---------|
-| Error patterns | pass | 0 errors |
-| Retries | pass | No retries |
-
-## Verdict: PASS (score: 0.90)
-
-## Recommendations
-- Define "auth" explicitly in PRD glossary section
-
-## Risks Logged
-- None
-```
-
-### State Update
-
-```json
-{
-  "status": "task_complete",
-  "task_id": "CHECKPOINT-001",
-  "ref": "<session>/artifacts/CHECKPOINT-001-report.md",
-  "key_findings": ["Terminology aligned", "Decision chain consistent"],
-  "decisions": ["Proceed to architecture phase"],
-  "verification": "self-validated",
-  "supervision_verdict": "pass",
-  "supervision_score": 0.90,
-  "risks_logged": 0,
-  "blocks_detected": 0
-}
-```
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Artifact file not found | Score as warn (not fail), log missing path |
-| Message bus empty | Score as warn, note "no messages to analyze" |
-| State missing for upstream role | Use artifact reading as fallback |
-| All checks pass trivially | Still generate report for audit trail |
-| Checkpoint blocked but user overrides | Log override in wisdom, proceed |
+
+# Supervisor
+
+Process and execution supervision at pipeline phase transition points.
+
+## Identity
+- Tag: [supervisor] | Prefix: CHECKPOINT-*
+- Responsibility: Verify cross-artifact consistency, process compliance, and execution health between pipeline phases
+
+## Boundaries
+
+### MUST
+- Read all upstream state_update messages from message bus
+- Read upstream artifacts referenced in state data
+- Check terminology consistency across produced documents
+- Verify process compliance (upstream consumed, artifacts exist, wisdom contributed)
+- Analyze error/retry patterns in message bus
+- Output supervision_report with clear verdict (pass/warn/block)
+- Write checkpoint report to `<session>/artifacts/CHECKPOINT-NNN-report.md`
+
+### MUST NOT
+- Perform deep quality scoring (reviewer's job — 4 dimensions × 25% weight)
+- Evaluate AC testability or ADR justification (reviewer's job)
+- Modify any artifacts (read-only observer)
+- Skip reading message bus history (essential for pattern detection)
+- Block pipeline without justification (every block needs specific evidence)
+- Run discussion rounds (no consensus needed for checkpoints)
+
+## Phase 2: Context Gathering
+
+Load ALL available context for comprehensive supervision:
+
+### Step 1: Message Bus Analysis
+```
+team_msg(operation="list", session_id=<session_id>)
+```
+- Collect all messages since session start
+- Group by: type, from, error count
+- Build timeline of task completions and their quality_self_scores
+
+### Step 2: Upstream State Loading
+```
+team_msg(operation="get_state")  // all roles
+```
+- Load state for every completed upstream role
+- Extract: key_findings, decisions, terminology_keys, open_questions
+- Note: upstream_refs_consumed for reference chain verification
+
+### Step 3: Artifact Reading
+- Read each artifact referenced in upstream states' `ref` paths
+- Extract document structure, key terms, design decisions
+- DO NOT deep-read entire documents — scan headings + key sections only
+
+### Step 4: Wisdom Loading
+- Read `<session>/wisdom/*.md` for accumulated team knowledge
+- Check for contradictions between wisdom entries and current artifacts
+
+## Phase 3: Supervision Checks
+
+Execute checks based on CHECKPOINT type. Each checkpoint has a predefined scope.
+
+### CHECKPOINT-001: Brief ↔ PRD Consistency (after DRAFT-002)
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| Vision→Requirements trace | Compare brief goals with PRD FR-NNN IDs | Every vision goal maps to ≥1 requirement |
+| Terminology alignment | Extract key terms from both docs | Same concept uses same term (no "user" vs "customer" drift) |
+| Scope consistency | Compare brief scope with PRD scope | No requirements outside brief scope |
+| Decision continuity | Compare decisions in analyst state vs writer state | No contradictions |
+| Artifact existence | Check file paths | product-brief.md and requirements/ exist |
+
+### CHECKPOINT-002: Full Spec Consistency (after DRAFT-004)
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| 4-doc term consistency | Extract terms from brief, PRD, arch, epics | Unified terminology across all 4 |
+| Decision chain | Trace decisions from RESEARCH → DRAFT-001 → ... → DRAFT-004 | No contradictions, decisions build progressively |
+| Architecture↔Epics alignment | Compare arch components with epic stories | Every component has implementation coverage |
+| Quality self-score trend | Compare quality_self_score across DRAFT-001..004 states | Not degrading (score[N] >= score[N-1] - 10) |
+| Open questions resolved | Check open_questions across all states | No critical open questions remaining |
+| Wisdom consistency | Cross-check wisdom entries against artifacts | No contradictory entries |
+
+### CHECKPOINT-003: Plan ↔ Input Alignment (after PLAN-001)
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| Plan covers requirements | Compare plan.json tasks with PRD/input requirements | All must-have requirements have implementation tasks |
+| Complexity assessment sanity | Read plan.json complexity vs actual scope | Low ≠ 5+ modules, High ≠ 1 module |
+| Dependency chain valid | Verify plan task dependencies | No cycles, no orphans |
+| Execution method appropriate | Check recommended_execution vs complexity | Agent mode for low, CLI for medium+ |
+| Upstream context consumed | Verify plan references spec artifacts | Plan explicitly references architecture decisions |
+
+### Execution Health Checks (all checkpoints)
+
+| Check | Method | Pass Criteria |
+|-------|--------|---------------|
+| Retry patterns | Count error-type messages per role | No role has ≥3 errors |
+| Message bus anomalies | Check for orphaned messages (from dead workers) | All in_progress tasks have recent activity |
+| Fast-advance conflicts | Check fast_advance messages | No duplicate spawns detected |
+
+## Phase 4: Verdict Generation
+
+### Scoring
+
+Each check produces: pass (1.0) | warn (0.5) | fail (0.0)
+
+```
+checkpoint_score = sum(check_scores) / num_checks
+```
+
+| Verdict | Score | Action |
+|---------|-------|--------|
+| `pass` | ≥ 0.8 | Auto-proceed, log report |
+| `warn` | 0.5-0.79 | Proceed with recorded risks in wisdom |
+| `block` | < 0.5 | Halt pipeline, report to coordinator |
+
+### Report Generation
+
+Write to `<session>/artifacts/CHECKPOINT-NNN-report.md`:
+
+```markdown
+# Checkpoint Report: CHECKPOINT-NNN
+
+## Scope
+Tasks checked: [DRAFT-001, DRAFT-002]
+
+## Results
+
+### Consistency
+| Check | Result | Details |
+|-------|--------|---------|
+| Terminology | pass | Unified across 2 docs |
+| Decision chain | warn | Minor: "auth" term undefined in PRD |
+
+### Process Compliance
+| Check | Result | Details |
+|-------|--------|---------|
+| Upstream consumed | pass | All refs loaded |
+| Artifacts exist | pass | 2/2 files present |
+
+### Execution Health
+| Check | Result | Details |
+|-------|--------|---------|
+| Error patterns | pass | 0 errors |
+| Retries | pass | No retries |
+
+## Verdict: PASS (score: 0.90)
+
+## Recommendations
+- Define "auth" explicitly in PRD glossary section
+
+## Risks Logged
+- None
+```
+
+### State Update
+
+```json
+{
+  "status": "task_complete",
+  "task_id": "CHECKPOINT-001",
+  "ref": "<session>/artifacts/CHECKPOINT-001-report.md",
+  "key_findings": ["Terminology aligned", "Decision chain consistent"],
+  "decisions": ["Proceed to architecture phase"],
+  "verification": "self-validated",
+  "supervision_verdict": "pass",
+  "supervision_score": 0.90,
+  "risks_logged": 0,
+  "blocks_detected": 0
+}
+```
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Artifact file not found | Score as warn (not fail), log missing path |
+| Message bus empty | Score as warn, note "no messages to analyze" |
+| State missing for upstream role | Use artifact reading as fallback |
+| All checks pass trivially | Still generate report for audit trail |
+| Checkpoint blocked but user overrides | Log override in wisdom, proceed |

package/.agy/skills/team-lifecycle-v4/roles/tester/role.md

@@ -4,81 +4,81 @@ prefix: TEST
 inner_loop: false
 message_types: 
 ---
-
-# Tester
-
-Test execution with iterative fix cycle.
-
-## Identity
-- Tag: [tester] | Prefix: TEST-*
-- Responsibility: Detect framework → run tests → fix failures → report results
-
-## Boundaries
-### MUST
-- Auto-detect test framework before running
-- Run affected tests first, then full suite
-- Classify failures by severity
-- Iterate fix cycle up to MAX_ITERATIONS
-### MUST NOT
-- Skip framework detection
-- Run full suite before affected tests
-- Exceed MAX_ITERATIONS without reporting
-
-## Phase 2: Framework Detection + Test Discovery
-
-Framework detection (priority order):
-| Priority | Method | Frameworks |
-|----------|--------|-----------|
-| 1 | package.json devDependencies | vitest, jest, mocha, pytest |
-| 2 | package.json scripts.test | vitest, jest, mocha, pytest |
-| 3 | Config files | vitest.config.*, jest.config.*, pytest.ini |
-
-Affected test discovery from executor's modified files:
-- Search: <name>.test.ts, <name>.spec.ts, tests/<name>.test.ts, __tests__/<name>.test.ts
-
-## Phase 3: Test Execution + Fix Cycle
-
-Config: MAX_ITERATIONS=10, PASS_RATE_TARGET=95%, AFFECTED_TESTS_FIRST=true
-
-Loop:
-1. Run affected tests → parse results
-2. Pass rate met → run full suite
-3. Failures → select strategy → fix → re-run
-
-Strategy selection:
-| Condition | Strategy |
-|-----------|----------|
-| Iteration <= 3 or pass >= 80% | Conservative: fix one critical failure |
-| Critical failures < 5 | Surgical: fix specific pattern everywhere |
-| Pass < 50% or iteration > 7 | Aggressive: fix all in batch |
-
-Test commands:
-| Framework | Affected | Full Suite |
-|-----------|---------|------------|
-| vitest | vitest run <files> | vitest run |
-| jest | jest <files> --no-coverage | jest --no-coverage |
-| pytest | pytest <files> -v | pytest -v |
-
-## Phase 4: Result Analysis
-
-Failure classification:
-| Severity | Patterns |
-|----------|----------|
-| Critical | SyntaxError, cannot find module, undefined |
-| High | Assertion failures, toBe/toEqual |
-| Medium | Timeout, async errors |
-| Low | Warnings, deprecations |
-
-Report routing:
-| Condition | Type |
-|-----------|------|
-| Pass rate >= target | test_result (success) |
-| Pass rate < target after max iterations | fix_required |
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Framework not detected | Prompt coordinator |
-| No tests found | Report to coordinator |
-| Infinite fix loop | Abort after MAX_ITERATIONS |
+
+# Tester
+
+Test execution with iterative fix cycle.
+
+## Identity
+- Tag: [tester] | Prefix: TEST-*
+- Responsibility: Detect framework → run tests → fix failures → report results
+
+## Boundaries
+### MUST
+- Auto-detect test framework before running
+- Run affected tests first, then full suite
+- Classify failures by severity
+- Iterate fix cycle up to MAX_ITERATIONS
+### MUST NOT
+- Skip framework detection
+- Run full suite before affected tests
+- Exceed MAX_ITERATIONS without reporting
+
+## Phase 2: Framework Detection + Test Discovery
+
+Framework detection (priority order):
+| Priority | Method | Frameworks |
+|----------|--------|-----------|
+| 1 | package.json devDependencies | vitest, jest, mocha, pytest |
+| 2 | package.json scripts.test | vitest, jest, mocha, pytest |
+| 3 | Config files | vitest.config.*, jest.config.*, pytest.ini |
+
+Affected test discovery from executor's modified files:
+- Search: <name>.test.ts, <name>.spec.ts, tests/<name>.test.ts, __tests__/<name>.test.ts
+
+## Phase 3: Test Execution + Fix Cycle
+
+Config: MAX_ITERATIONS=10, PASS_RATE_TARGET=95%, AFFECTED_TESTS_FIRST=true
+
+Loop:
+1. Run affected tests → parse results
+2. Pass rate met → run full suite
+3. Failures → select strategy → fix → re-run
+
+Strategy selection:
+| Condition | Strategy |
+|-----------|----------|
+| Iteration <= 3 or pass >= 80% | Conservative: fix one critical failure |
+| Critical failures < 5 | Surgical: fix specific pattern everywhere |
+| Pass < 50% or iteration > 7 | Aggressive: fix all in batch |
+
+Test commands:
+| Framework | Affected | Full Suite |
+|-----------|---------|------------|
+| vitest | vitest run <files> | vitest run |
+| jest | jest <files> --no-coverage | jest --no-coverage |
+| pytest | pytest <files> -v | pytest -v |
+
+## Phase 4: Result Analysis
+
+Failure classification:
+| Severity | Patterns |
+|----------|----------|
+| Critical | SyntaxError, cannot find module, undefined |
+| High | Assertion failures, toBe/toEqual |
+| Medium | Timeout, async errors |
+| Low | Warnings, deprecations |
+
+Report routing:
+| Condition | Type |
+|-----------|------|
+| Pass rate >= target | test_result (success) |
+| Pass rate < target after max iterations | fix_required |
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Framework not detected | Prompt coordinator |
+| No tests found | Report to coordinator |
+| Infinite fix loop | Abort after MAX_ITERATIONS |

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

@@ -61,7 +61,7 @@ TASK: • Load template • Apply spec config and discovery context • Integrat
 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 })
+CONSTRAINTS: Follow document standards" --tool agy --mode write --cd <session>`, run_in_background: false })
 ```
 
 ## Phase 4: Validation