maestro-flow 0.1.4 → 0.2.1

package/.claude/commands/maestro-ui-design.md

@@ -1,152 +1,152 @@
----
-name: maestro-ui-design
-description: Generate UI design prototypes with multiple styles via ui-ux-pro-max, user selects winner, solidify as code reference
-argument-hint: "<phase|topic> [--styles N] [--stack <stack>] [--targets <pages>] [--layouts N] [--refine] [--persist] [--full] [-y]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Generate UI design prototypes for a phase or topic. Two workflow paths, auto-selected by skill availability:
-
-1. **Primary (ui-style.md):** Delegates design to ui-ux-pro-max skill. Generates multiple style variants via `--design-system`, user selects, solidifies as code reference. Lightweight and fast.
-2. **Fallback (ui-design.md):** Self-contained 4-layer pipeline (style → animation → layout → assembly) with 6D attribute space, OKLCH tokens, layout templates, and full prototype matrix. Used when ui-ux-pro-max is unavailable or `--full` is requested.
-
-Both paths produce the same output contract: MASTER.md + design-tokens.json + animation-tokens.json + selection.json for downstream plan/execute consumption.
-
-Position in pipeline: analyze -> **ui-design** -> plan -> execute -> verify
-</purpose>
-
-<deferred_reading>
-- [ui-style.md](~/.maestro/workflows/ui-style.md) — read when SKILL_PATH found (primary path)
-- [ui-design.md](~/.maestro/workflows/ui-design.md) — read when SKILL_PATH empty or --full (fallback path)
-- [index.json](~/.maestro/templates/index.json) — read when updating phase metadata
-- [scratch-index.json](~/.maestro/templates/scratch-index.json) — read when operating in scratch mode
-</deferred_reading>
-
-<context>
-$ARGUMENTS — phase number for phase mode, topic text for scratch mode, with optional flags.
-
-**Flags:**
-- `--styles N` — Number of style variants to generate (default: 3, range: 2-5)
-- `--layouts N` — Number of layout variants per target (default: 2, range: 1-3)
-- `--stack <stack>` — Tech stack for implementation guidelines (default: html-tailwind). Options: html-tailwind, react, nextjs, vue, svelte, shadcn
-- `--targets <pages>` — Comma-separated page/component targets to prototype (default: inferred from phase goal or "home")
-- `--refine` — Refinement mode: fine-tune an existing design-ref instead of generating from scratch (ui-design.md only)
-- `--persist` — Save design system with hierarchical page overrides (MASTER.md + pages/)
-- `--full` — Force full 4-layer pipeline (ui-design.md) even when ui-ux-pro-max is available
-- `-y` / `--yes` — Auto mode: skip interactive selection, pick top-scored variant
-
-**Workflow routing:**
-- Default: auto-detect ui-ux-pro-max skill → if found, use `ui-style.md` (lightweight); if not, use `ui-design.md` (self-contained)
-- `--full`: always use `ui-design.md` regardless of skill availability
-- Flags `--layouts N` and `--refine` are only effective with `ui-design.md` (full pipeline)
-
-**Phase mode** (number): resolves phase directory, reads context.md/brainstorm for requirements.
-**Scratch mode** (text): creates `.workflow/scratch/ui-design-{slug}-{date}/` for standalone exploration.
-
-**Output artifacts (in phase or scratch directory):**
-| Artifact | Description |
-|----------|-------------|
-| `design-ref/` | Root directory for all design outputs |
-| `design-ref/MASTER.md` | Selected design system (colors, typography, spacing, effects, anti-patterns) |
-| `design-ref/design-tokens.json` | Production-ready tokens (OKLCH colors, typography.combinations, component_styles, opacity) |
-| `design-ref/animation-tokens.json` | Animation system (duration, easing, transitions, keyframes, interactions) |
-| `design-ref/layout-templates/` | Structural layout templates per target (dom_structure + css_layout_rules) |
-| `design-ref/prototypes/` | Assembled HTML/CSS prototypes (styles x layouts x targets) |
-| `design-ref/prototypes/compare.html` | Interactive matrix comparison page |
-| `design-ref/.intermediates/` | Analysis options, user selections, exploration data |
-| `design-ref/selection.json` | User selection metadata + rationale |
-| `design-ref/pages/{page}.md` | Page-specific design overrides (if --persist) |
-</context>
-
-<execution>
-## Workflow Routing (skill detection)
-
-Detect ui-ux-pro-max skill availability:
-
-```bash
-SKILL_PATH=""
-for path in \
-  "skills/ui-ux-pro-max/scripts/search.py" \
-  "$HOME/.claude/plugins/cache/ui-ux-pro-max-skill/ui-ux-pro-max/*/scripts/search.py"; do
-  expanded=$(ls $path 2>/dev/null | tail -1)
-  if [ -n "$expanded" ]; then SKILL_PATH="$expanded"; break; fi
-done
-[ -z "$SKILL_PATH" ] && SKILL_PATH=$(find "$HOME/.claude/plugins" -path "*/ui-ux-pro-max/*/scripts/search.py" -print -quit 2>/dev/null)
-```
-
-**Route:**
-- **`--full` flag present** → Follow '~/.maestro/workflows/ui-design.md' completely (forced full pipeline)
-- **SKILL_PATH found** → Follow '~/.maestro/workflows/ui-style.md' completely (lightweight, delegates design to ui-ux-pro-max)
-- **SKILL_PATH empty** → Follow '~/.maestro/workflows/ui-design.md' completely (self-contained 4-layer pipeline fallback)
-
-Pass `SKILL_PATH` to the workflow when using ui-style.md.
-
-**Report format on completion:**
-
-```
-=== UI DESIGN READY ===
-Phase:   {phase_name}
-Styles:  {style_count} variants, #{selected} selected
-Layouts: {layout_count} per target
-Targets: {target_list}
-Stack:   {stack}
-Matrix:  {S x L x T} = {total} prototypes
-
-Design System:
-  MASTER.md:        {phase_dir}/design-ref/MASTER.md
-  Tokens:           {phase_dir}/design-ref/design-tokens.json
-  Animation:        {phase_dir}/design-ref/animation-tokens.json
-  Layout Templates: {phase_dir}/design-ref/layout-templates/
-  Prototypes:       {phase_dir}/design-ref/prototypes/
-  Compare:          {phase_dir}/design-ref/prototypes/compare.html
-
-Next steps:
-  Skill({ skill: "maestro-plan", args: "{phase}" })              -- Plan with design reference
-  Skill({ skill: "maestro-ui-design", args: "{phase} --refine" }) -- Refine selected design
-  Skill({ skill: "maestro-analyze", args: "{phase}" })           -- Analyze before planning
-```
-</execution>
-
-<error_codes>
-| Code | Severity | Description | Stage |
-|------|----------|-------------|-------|
-| E001 | error | Phase or topic argument required | parse_input |
-| E002 | error | Phase directory not found | parse_input |
-| E003 | error | Python not available (both paths need Python for ui-ux-pro-max or agent fallback) | setup |
-| E004 | error | --refine requires existing design-ref/ | parse_input |
-| W001 | warning | Design system generation returned partial results | generate |
-| W002 | warning | Prototype rendering failed for one variant | render |
-| W003 | warning | No context.md found, using phase goal only | context |
-| W004 | warning | ui-ux-pro-max not found, falling back to full pipeline | routing |
-</error_codes>
-
-<success_criteria>
-**Both paths (common):**
-- [ ] Requirements extracted from phase context (context.md, brainstorm, spec, or user input)
-- [ ] N style variants generated with contrasting design directions
-- [ ] User selected preferred variant (or auto-selected in -y mode)
-- [ ] MASTER.md written with complete design system specification
-- [ ] design-tokens.json written with production-ready tokens (OKLCH colors, component_styles)
-- [ ] animation-tokens.json written (duration, easing, transitions, keyframes)
-- [ ] selection.json recorded with choice metadata
-- [ ] index.json updated with design_ref status
-
-**ui-style.md path (primary):**
-- [ ] ui-ux-pro-max --design-system called with product/industry/style keywords
-- [ ] Tokens extracted from ui-ux-pro-max output into structured JSON
-
-**ui-design.md path (--full or fallback):**
-- [ ] 6D attribute space used for maximum contrast between variants
-- [ ] Layout templates generated per target (dom_structure + css_layout_rules)
-- [ ] HTML prototypes assembled: styles x layouts x targets
-- [ ] compare.html generated as interactive matrix viewer
-</success_criteria>
-</output>
+---
+name: maestro-ui-design
+description: Generate UI design prototypes with multiple styles via ui-ux-pro-max, user selects winner, solidify as code reference
+argument-hint: "<phase|topic> [--styles N] [--stack <stack>] [--targets <pages>] [--layouts N] [--refine] [--persist] [--full] [-y]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Generate UI design prototypes for a phase or topic. Two workflow paths, auto-selected by skill availability:
+
+1. **Primary (ui-style.md):** Delegates design to ui-ux-pro-max skill. Generates multiple style variants via `--design-system`, user selects, solidifies as code reference. Lightweight and fast.
+2. **Fallback (ui-design.md):** Self-contained 4-layer pipeline (style → animation → layout → assembly) with 6D attribute space, OKLCH tokens, layout templates, and full prototype matrix. Used when ui-ux-pro-max is unavailable or `--full` is requested.
+
+Both paths produce the same output contract: MASTER.md + design-tokens.json + animation-tokens.json + selection.json for downstream plan/execute consumption.
+
+Position in pipeline: analyze -> **ui-design** -> plan -> execute -> verify
+</purpose>
+
+<deferred_reading>
+- [ui-style.md](~/.maestro/workflows/ui-style.md) — read when SKILL_PATH found (primary path)
+- [ui-design.md](~/.maestro/workflows/ui-design.md) — read when SKILL_PATH empty or --full (fallback path)
+- [index.json](~/.maestro/templates/index.json) — read when updating phase metadata
+- [scratch-index.json](~/.maestro/templates/scratch-index.json) — read when operating in scratch mode
+</deferred_reading>
+
+<context>
+$ARGUMENTS — phase number for phase mode, topic text for scratch mode, with optional flags.
+
+**Flags:**
+- `--styles N` — Number of style variants to generate (default: 3, range: 2-5)
+- `--layouts N` — Number of layout variants per target (default: 2, range: 1-3)
+- `--stack <stack>` — Tech stack for implementation guidelines (default: html-tailwind). Options: html-tailwind, react, nextjs, vue, svelte, shadcn
+- `--targets <pages>` — Comma-separated page/component targets to prototype (default: inferred from phase goal or "home")
+- `--refine` — Refinement mode: fine-tune an existing design-ref instead of generating from scratch (ui-design.md only)
+- `--persist` — Save design system with hierarchical page overrides (MASTER.md + pages/)
+- `--full` — Force full 4-layer pipeline (ui-design.md) even when ui-ux-pro-max is available
+- `-y` / `--yes` — Auto mode: skip interactive selection, pick top-scored variant
+
+**Workflow routing:**
+- Default: auto-detect ui-ux-pro-max skill → if found, use `ui-style.md` (lightweight); if not, use `ui-design.md` (self-contained)
+- `--full`: always use `ui-design.md` regardless of skill availability
+- Flags `--layouts N` and `--refine` are only effective with `ui-design.md` (full pipeline)
+
+**Phase mode** (number): resolves phase directory, reads context.md/brainstorm for requirements.
+**Scratch mode** (text): creates `.workflow/scratch/ui-design-{slug}-{date}/` for standalone exploration.
+
+**Output artifacts (in phase or scratch directory):**
+| Artifact | Description |
+|----------|-------------|
+| `design-ref/` | Root directory for all design outputs |
+| `design-ref/MASTER.md` | Selected design system (colors, typography, spacing, effects, anti-patterns) |
+| `design-ref/design-tokens.json` | Production-ready tokens (OKLCH colors, typography.combinations, component_styles, opacity) |
+| `design-ref/animation-tokens.json` | Animation system (duration, easing, transitions, keyframes, interactions) |
+| `design-ref/layout-templates/` | Structural layout templates per target (dom_structure + css_layout_rules) |
+| `design-ref/prototypes/` | Assembled HTML/CSS prototypes (styles x layouts x targets) |
+| `design-ref/prototypes/compare.html` | Interactive matrix comparison page |
+| `design-ref/.intermediates/` | Analysis options, user selections, exploration data |
+| `design-ref/selection.json` | User selection metadata + rationale |
+| `design-ref/pages/{page}.md` | Page-specific design overrides (if --persist) |
+</context>
+
+<execution>
+## Workflow Routing (skill detection)
+
+Detect ui-ux-pro-max skill availability:
+
+```bash
+SKILL_PATH=""
+for path in \
+  "skills/ui-ux-pro-max/scripts/search.py" \
+  "$HOME/.claude/plugins/cache/ui-ux-pro-max-skill/ui-ux-pro-max/*/scripts/search.py"; do
+  expanded=$(ls $path 2>/dev/null | tail -1)
+  if [ -n "$expanded" ]; then SKILL_PATH="$expanded"; break; fi
+done
+[ -z "$SKILL_PATH" ] && SKILL_PATH=$(find "$HOME/.claude/plugins" -path "*/ui-ux-pro-max/*/scripts/search.py" -print -quit 2>/dev/null)
+```
+
+**Route:**
+- **`--full` flag present** → Follow '~/.maestro/workflows/ui-design.md' completely (forced full pipeline)
+- **SKILL_PATH found** → Follow '~/.maestro/workflows/ui-style.md' completely (lightweight, delegates design to ui-ux-pro-max)
+- **SKILL_PATH empty** → Follow '~/.maestro/workflows/ui-design.md' completely (self-contained 4-layer pipeline fallback)
+
+Pass `SKILL_PATH` to the workflow when using ui-style.md.
+
+**Report format on completion:**
+
+```
+=== UI DESIGN READY ===
+Phase:   {phase_name}
+Styles:  {style_count} variants, #{selected} selected
+Layouts: {layout_count} per target
+Targets: {target_list}
+Stack:   {stack}
+Matrix:  {S x L x T} = {total} prototypes
+
+Design System:
+  MASTER.md:        {phase_dir}/design-ref/MASTER.md
+  Tokens:           {phase_dir}/design-ref/design-tokens.json
+  Animation:        {phase_dir}/design-ref/animation-tokens.json
+  Layout Templates: {phase_dir}/design-ref/layout-templates/
+  Prototypes:       {phase_dir}/design-ref/prototypes/
+  Compare:          {phase_dir}/design-ref/prototypes/compare.html
+
+Next steps:
+  Skill({ skill: "maestro-plan", args: "{phase}" })              -- Plan with design reference
+  Skill({ skill: "maestro-ui-design", args: "{phase} --refine" }) -- Refine selected design
+  Skill({ skill: "maestro-analyze", args: "{phase}" })           -- Analyze before planning
+```
+</execution>
+
+<error_codes>
+| Code | Severity | Description | Stage |
+|------|----------|-------------|-------|
+| E001 | error | Phase or topic argument required | parse_input |
+| E002 | error | Phase directory not found | parse_input |
+| E003 | error | Python not available (both paths need Python for ui-ux-pro-max or agent fallback) | setup |
+| E004 | error | --refine requires existing design-ref/ | parse_input |
+| W001 | warning | Design system generation returned partial results | generate |
+| W002 | warning | Prototype rendering failed for one variant | render |
+| W003 | warning | No context.md found, using phase goal only | context |
+| W004 | warning | ui-ux-pro-max not found, falling back to full pipeline | routing |
+</error_codes>
+
+<success_criteria>
+**Both paths (common):**
+- [ ] Requirements extracted from phase context (context.md, brainstorm, spec, or user input)
+- [ ] N style variants generated with contrasting design directions
+- [ ] User selected preferred variant (or auto-selected in -y mode)
+- [ ] MASTER.md written with complete design system specification
+- [ ] design-tokens.json written with production-ready tokens (OKLCH colors, component_styles)
+- [ ] animation-tokens.json written (duration, easing, transitions, keyframes)
+- [ ] selection.json recorded with choice metadata
+- [ ] index.json updated with design_ref status
+
+**ui-style.md path (primary):**
+- [ ] ui-ux-pro-max --design-system called with product/industry/style keywords
+- [ ] Tokens extracted from ui-ux-pro-max output into structured JSON
+
+**ui-design.md path (--full or fallback):**
+- [ ] 6D attribute space used for maximum contrast between variants
+- [ ] Layout templates generated per target (dom_structure + css_layout_rules)
+- [ ] HTML prototypes assembled: styles x layouts x targets
+- [ ] compare.html generated as interactive matrix viewer
+</success_criteria>
+</output>

package/.claude/commands/maestro-verify.md

@@ -1,84 +1,87 @@
----
-name: maestro-verify
-description: Goal-Backward verification with 3-layer must-have checks, anti-pattern scan, Nyquist test coverage validation, and gap-fix plan generation
-argument-hint: "<phase> [--skip-tests] [--skip-antipattern]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Verify phase execution results through three complementary methods:
-1. **Goal-Backward verification** — 3-layer check (Truths → Artifacts → Wiring) that validates goals are actually achieved, not just tasks completed
-2. **Anti-pattern scan** — detect stubs, placeholders, TODO/FIXME, empty returns in modified files
-3. **Nyquist test coverage validation** — requirement-to-test mapping with gap classification (COVERED/PARTIAL/MISSING)
-
-Core principle: **Task completion ≠ Goal achievement**. A task "create chat component" can be marked complete when the component is a placeholder. This verifier checks that the goal "working chat interface" is actually achieved.
-
-Produces verification.json with must-have checks, gaps, anti-patterns, and fix plans. Optionally produces validation.json with test coverage analysis.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/verify.md
-</required_reading>
-
-<deferred_reading>
-- [verification.json](~/.maestro/templates/verification.json) — read when generating verification output
-- [validation.json](~/.maestro/templates/validation.json) — read when generating validation output
-- [index.json](~/.maestro/templates/index.json) — read when updating phase index
-</deferred_reading>
-
-<context>
-Phase: $ARGUMENTS (required -- phase number or slug)
-
-**Flags:**
-- `--skip-tests` -- Skip Nyquist test coverage validation (V2), only run Goal-Backward verification
-- `--skip-antipattern` -- Skip anti-pattern scan
-
-Context files resolved from `.workflow/phases/{NN}-{slug}/`:
-- index.json (phase metadata, success_criteria, plan, execution results)
-- plan.json (task overview)
-- .task/TASK-{NNN}.json (task definitions with convergence.criteria)
-- .summaries/TASK-{NNN}-summary.md (execution results)
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/verify.md' completely.
-
-**Next-step routing on completion:**
-- All checks pass, no gaps → Skill({ skill: "quality-review", args: "{phase}" })
-- Gaps found (must-have failures or anti-pattern blockers) → Skill({ skill: "maestro-plan", args: "{phase} --gaps" })
-- Low test coverage (Nyquist gaps) → Skill({ skill: "quality-test-gen", args: "{phase}" })
-
-**Gap-fix closure loop:**
-Gaps found → maestro-plan --gaps → maestro-execute → maestro-verify (re-run)
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Phase argument required | Check arguments format, re-run with correct input |
-| E002 | error | Phase directory not found | Check arguments format, re-run with correct input |
-| E003 | error | No execution results found (missing summaries) | Check arguments format, re-run with correct input |
-| W001 | warning | Test coverage below configured threshold | Review coverage gaps, run quality-test-gen |
-| W002 | warning | Anti-pattern blockers found in modified files | Fix anti-pattern blockers before proceeding |
-</error_codes>
-
-<success_criteria>
-- [ ] Must-haves established (from success_criteria, convergence.criteria, or derived)
-- [ ] All truths verified with status and evidence (Layer 1)
-- [ ] All artifacts checked at L1 (exists), L2 (substantive), L3 (wired) (Layer 2)
-- [ ] All key links verified with evidence (Layer 3)
-- [ ] Anti-patterns scanned and categorized (unless skipped)
-- [ ] Nyquist test coverage assessed with gap classification (unless skipped)
-- [ ] Fix plans generated for identified gaps
-- [ ] Human verification items identified
-- [ ] verification.json written with complete results
-- [ ] validation.json written if test audit ran
-- [ ] index.json updated with verification status and timestamps
-</success_criteria>
+---
+name: maestro-verify
+description: Goal-Backward verification with 3-layer must-have checks, anti-pattern scan, Nyquist test coverage validation, and gap-fix plan generation
+argument-hint: "<phase> [--skip-tests] [--skip-antipattern]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Verify phase execution results through three complementary methods:
+1. **Goal-Backward verification** — 3-layer check (Truths → Artifacts → Wiring) that validates goals are actually achieved, not just tasks completed
+2. **Anti-pattern scan** — detect stubs, placeholders, TODO/FIXME, empty returns in modified files
+3. **Nyquist test coverage validation** — requirement-to-test mapping with gap classification (COVERED/PARTIAL/MISSING)
+
+Core principle: **Task completion ≠ Goal achievement**. A task "create chat component" can be marked complete when the component is a placeholder. This verifier checks that the goal "working chat interface" is actually achieved.
+
+Produces verification.json with must-have checks, gaps, anti-patterns, and fix plans. Optionally produces validation.json with test coverage analysis.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/verify.md
+</required_reading>
+
+<deferred_reading>
+- [verification.json](~/.maestro/templates/verification.json) — read when generating verification output
+- [validation.json](~/.maestro/templates/validation.json) — read when generating validation output
+- [index.json](~/.maestro/templates/index.json) — read when updating phase index
+</deferred_reading>
+
+<context>
+Phase: $ARGUMENTS (required -- phase number or slug)
+
+**Flags:**
+- `--skip-tests` -- Skip Nyquist test coverage validation (V2), only run Goal-Backward verification
+- `--skip-antipattern` -- Skip anti-pattern scan
+
+Context files resolved from `.workflow/phases/{NN}-{slug}/`:
+- index.json (phase metadata, success_criteria, plan, execution results)
+- plan.json (task overview)
+- .task/TASK-{NNN}.json (task definitions with convergence.criteria)
+- .summaries/TASK-{NNN}-summary.md (execution results)
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/verify.md' completely.
+
+**Next-step routing on completion:**
+- All checks pass, no gaps → Skill({ skill: "quality-review", args: "{phase}" })
+- Gaps found (must-have failures or anti-pattern blockers) → Skill({ skill: "maestro-plan", args: "{phase} --gaps" })
+- Low test coverage (Nyquist gaps) → Skill({ skill: "quality-test-gen", args: "{phase}" })
+
+**Gap-fix closure loop:**
+Gaps found → maestro-plan --gaps → maestro-execute → maestro-verify (re-run)
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Phase argument required | Check arguments format, re-run with correct input |
+| E002 | error | Phase directory not found | Check arguments format, re-run with correct input |
+| E003 | error | No execution results found (missing summaries) | Check arguments format, re-run with correct input |
+| W001 | warning | Test coverage below configured threshold | Review coverage gaps, run quality-test-gen |
+| W002 | warning | Anti-pattern blockers found in modified files | Fix anti-pattern blockers before proceeding |
+| W003 | warning | Wiki health below threshold (score < 80) | Review broken links and orphan specs |
+| W004 | warning | Wiki health check unavailable | Skipped — wiki may not be initialized |
+</error_codes>
+
+<success_criteria>
+- [ ] Must-haves established (from success_criteria, convergence.criteria, or derived)
+- [ ] All truths verified with status and evidence (Layer 1)
+- [ ] All artifacts checked at L1 (exists), L2 (substantive), L3 (wired) (Layer 2)
+- [ ] Wiki health score reported (Layer 2.5) — warnings emitted if score < 80 or orphan specs found
+- [ ] All key links verified with evidence (Layer 3)
+- [ ] Anti-patterns scanned and categorized (unless skipped)
+- [ ] Nyquist test coverage assessed with gap classification (unless skipped)
+- [ ] Fix plans generated for identified gaps
+- [ ] Human verification items identified
+- [ ] verification.json written with complete results
+- [ ] validation.json written if test audit ran
+- [ ] index.json updated with verification status and timestamps
+</success_criteria>

package/.claude/commands/maestro.md

@@ -64,7 +64,9 @@ When `-y` is active, maestro propagates auto flags to downstream commands. Only
 | quality-test | `--auto-fix` | Auto-trigger gap-fix loop on failures |
 | quality-test-gen | *(none)* | No auto flag — generates tests normally |
 | quality-debug | *(none)* | No auto flag — runs diagnosis normally |
+| quality-retrospective | `--auto-yes` | Accept all routing recommendations (spec/note/issue) without prompting |
 | maestro-phase-transition | *(none)* | No auto flag — validates and transitions |
+| manage-learn | *(none)* | No auto flag — pure file operation, no prompts |
 
 Commands not listed (manage-*, spec-*, milestone-*) have no auto flags and execute as-is.
 

package/.claude/commands/manage-issue-analyze.md

@@ -1,62 +1,62 @@
----
-name: manage-issue-analyze
-description: Root cause analysis for a specific issue using CLI exploration
-argument-hint: "<ISS-ID> [--tool gemini|qwen] [--depth standard|deep]"
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Root cause analysis for a specific issue. Uses CLI exploration to analyze codebase context, identify root cause, assess impact, and produce a structured analysis record attached to the issue in `.workflow/issues/issues.jsonl`.
-
-- **--tool**: CLI tool for analysis (default: gemini)
-- **--depth**: `standard` (keyword grep) or `deep` (semantic search via Agent)
-
-For issue CRUD, use `/manage-issue`. For solution planning, use `/manage-issue-plan`.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/issue-analyze.md
-</required_reading>
-
-<deferred_reading>
-- [issue.json template](~/.maestro/templates/issue.json) -- read when building the analysis record structure
-</deferred_reading>
-
-<context>
-$ARGUMENTS -- ISS-ID (required) + optional flags.
-
-**Options:**
-- `<ISS-ID>` -- issue ID in ISS-XXXXXXXX-NNN format (required)
-- `--tool gemini|qwen` -- CLI tool for analysis (default: gemini)
-- `--depth standard|deep` -- analysis depth (default: standard)
-
-**State files:**
-- `.workflow/issues/issues.jsonl` -- issue records (read + write)
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/issue-analyze.md' completely.
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E_NO_ISSUE_ID | error | No ISS-ID provided in $ARGUMENTS | Display usage hint with example |
-| E_ISSUE_NOT_FOUND | error | ISS-ID not found in issues.jsonl | Suggest `/manage-issue list` to find valid IDs |
-| E_INVALID_STATUS | warning | Issue status is not 'open' or 'registered' | Warn but allow analysis to proceed |
-| E_ANALYSIS_FAILED | error | CLI analysis returned no usable results | Retry with different --tool or report partial context |
-</error_codes>
-
-<success_criteria>
-- [ ] Issue loaded and validated from issues.jsonl
-- [ ] Codebase context gathered (grep or semantic search)
-- [ ] CLI analysis executed and JSON result parsed
-- [ ] Analysis record attached to issue in issues.jsonl
-- [ ] Summary displayed with next-step routing to manage-issue-plan
-</success_criteria>
+---
+name: manage-issue-analyze
+description: Root cause analysis for a specific issue using CLI exploration
+argument-hint: "<ISS-ID> [--tool gemini|qwen] [--depth standard|deep]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Root cause analysis for a specific issue. Uses CLI exploration to analyze codebase context, identify root cause, assess impact, and produce a structured analysis record attached to the issue in `.workflow/issues/issues.jsonl`.
+
+- **--tool**: CLI tool for analysis (default: gemini)
+- **--depth**: `standard` (keyword grep) or `deep` (semantic search via Agent)
+
+For issue CRUD, use `/manage-issue`. For solution planning, use `/manage-issue-plan`.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/issue-analyze.md
+</required_reading>
+
+<deferred_reading>
+- [issue.json template](~/.maestro/templates/issue.json) -- read when building the analysis record structure
+</deferred_reading>
+
+<context>
+$ARGUMENTS -- ISS-ID (required) + optional flags.
+
+**Options:**
+- `<ISS-ID>` -- issue ID in ISS-XXXXXXXX-NNN format (required)
+- `--tool gemini|qwen` -- CLI tool for analysis (default: gemini)
+- `--depth standard|deep` -- analysis depth (default: standard)
+
+**State files:**
+- `.workflow/issues/issues.jsonl` -- issue records (read + write)
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/issue-analyze.md' completely.
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E_NO_ISSUE_ID | error | No ISS-ID provided in $ARGUMENTS | Display usage hint with example |
+| E_ISSUE_NOT_FOUND | error | ISS-ID not found in issues.jsonl | Suggest `/manage-issue list` to find valid IDs |
+| E_INVALID_STATUS | warning | Issue status is not 'open' or 'registered' | Warn but allow analysis to proceed |
+| E_ANALYSIS_FAILED | error | CLI analysis returned no usable results | Retry with different --tool or report partial context |
+</error_codes>
+
+<success_criteria>
+- [ ] Issue loaded and validated from issues.jsonl
+- [ ] Codebase context gathered (grep or semantic search)
+- [ ] CLI analysis executed and JSON result parsed
+- [ ] Analysis record attached to issue in issues.jsonl
+- [ ] Summary displayed with next-step routing to manage-issue-plan
+</success_criteria>