maestro-flow 0.3.15 → 0.3.17

package/.claude/commands/quality-review.md

@@ -13,28 +13,7 @@ allowed-tools:
   - AskUserQuestion
 ---
 <purpose>
-Run multi-dimensional code review on a completed phase's changed files. Answers the question "is this code good?" — complementing maestro-verify ("is the goal met?") and quality-test ("does it work for users?").
-
-Supports three review levels that scale with task depth:
-
-**Quick** — Single-pass inline scan, no agents. For small changes (≤3 files) or scratch tasks.
-  - Dimensions: correctness + security only
-  - No deep-dive, issues created for critical only
-
-**Standard** — Parallel agent review across all dimensions. Default for most phases.
-  - Dimensions: all 6 (correctness, security, performance, architecture, maintainability, best-practices)
-  - Auto deep-dive if critical findings > 0
-  - Issues created for critical + high
-
-**Deep** — Full agent review with forced multi-iteration deep-dive and cross-file impact analysis. For complex/critical phases.
-  - Dimensions: all 6
-  - Forced deep-dive (max 3 iterations) with impact radius analysis
-  - Issues created for critical + high + medium
-
-Level auto-detection when not specified:
-  - ≤3 changed files → quick
-  - 4-19 changed files → standard
-  - ≥20 changed files OR phase marked critical in index.json → deep
+Run multi-dimensional code review on a completed phase's changed files. Answers the question "is this code good?" -- complementing maestro-verify ("is the goal met?") and quality-test ("does it work for users?"). Three review levels (quick/standard/deep) scale with task depth, auto-detected from file count. Level definitions, dimension lists, deep-dive rules, and issue creation thresholds defined in workflow review.md.
 </purpose>
 
 <required_reading>
@@ -96,38 +75,10 @@ Append to state.json.artifacts[]:
 }
 ```
 
-**Report format on completion:**
-
-```
-=== CODE REVIEW RESULTS ===
-Phase:     {phase_name}
-Level:     {quick | standard | deep}
-Files:     {files_reviewed} files across {dimensions_count} dimensions
-Duration:  {duration}
-
-Severity Distribution:
-  Critical: {critical_count}
-  High:     {high_count}
-  Medium:   {medium_count}
-  Low:      {low_count}
-
-Top Issues:
-  1. [{severity}] {finding_id}: {title} ({file}:{line})
-  2. ...
-
-Verdict: {PASS | WARN | BLOCK}
-Issues Created: {issue_count}
-
-Files:
-  {REVIEW_DIR}/review.json
-
-Next steps:
-  {verdict_based_routing}
-```
+Report format and next-step routing by verdict defined in workflow review.md Report Format and Next Step Routing sections.
 
-**Next-step routing by verdict:**
+**Next-step routing summary:**
 - PASS → `/quality-test {phase}`
-- PASS + low test coverage → `/quality-test-gen {phase}`
 - WARN → `/quality-test {phase}` (proceed with caveats)
 - BLOCK → `/maestro-plan {phase} --gaps` (fix critical findings first)
 </execution>

package/.claude/commands/quality-test-gen.md

@@ -13,16 +13,7 @@ allowed-tools:
   - AskUserQuestion
 ---
 <purpose>
-Generate missing automated tests for a phase based on gap analysis from maestro-verify (Nyquist audit) and quality-test (UAT coverage gaps). Classifies changed files into unit test vs E2E vs skip categories, discovers existing test infrastructure, generates a test plan for user approval, then writes tests using RED-GREEN methodology.
-
-Key mechanisms from GSD add-tests:
-- **TDD/E2E/Skip classification**: Categorize changed files by appropriate test type
-- **Test structure discovery**: Find existing test patterns, frameworks, conventions
-- **Test plan with user approval**: Present plan before writing any tests
-- **RED-GREEN generation**: Write failing test first, verify it targets the right behavior
-- **Bug discovery, not fix**: Tests expose bugs; fixing is for quality-debug or maestro-execute
-
-This command is the "test gap filler" -- it bridges the gap between verification (maestro-verify finds MISSING coverage) and testing (quality-test runs UAT). It produces the automated tests that make Nyquist coverage pass.
+Generate missing automated tests for a phase based on gap analysis from maestro-verify (Nyquist audit) and quality-test (UAT coverage gaps). Bridges verification (finds MISSING coverage) and testing (runs UAT) by producing the automated tests that make Nyquist coverage pass. TDD/E2E classification, test discovery, plan approval, and RED-GREEN methodology defined in workflow test-gen.md.
 </purpose>
 
 <required_reading>

package/.claude/commands/quality-test.md

@@ -32,35 +32,13 @@ Key mechanisms from GSD verify-work:
 <context>
 Phase or task: $ARGUMENTS (optional)
 
-**Flags:**
-- `--smoke` -- Run cold-start smoke tests before UAT (basic sanity: app starts, routes respond, no crash)
-- `--auto-fix` -- After diagnosis, auto-trigger gap-fix loop instead of asking user
-
-**All context via state.json.artifacts[]:**
-
-```
-related = artifacts.filter(a =>
-  a.phase === target_phase && a.milestone === current_milestone
-).sort_by(completed_at asc)
-```
-
-Each artifact's type determines its outputs at `.workflow/{a.path}/`:
-- **execute** → .summaries/, .task/, verification.json, plan.json (test target source)
-- **verify** → verification.json (must_haves, gaps)
-- **review** → review.json (findings become additional test scenarios)
-- **debug** → understanding.md (confirmed root causes become regression tests)
-- **test** → uat.md (existing session, resumable)
-
-Extract conclusions from related artifacts that may affect this test session — review findings generate additional scenarios, debug root causes generate regression tests.
-
-**Output**: `TEST_DIR = .workflow/scratch/{YYYYMMDD}-test-P{N}-{slug}/` (P{N} = phase number, enables directory-level identification as state.json fallback)
+Flags, artifact context resolution, and output directory format defined in workflow test.md.
 </context>
 
 <execution>
 Follow '~/.maestro/workflows/test.md' completely.
 
-**Output writes to TEST_DIR** (`scratch/{YYYYMMDD}-test-P{N}-{slug}/`):
-- uat.md, test-plan.json, .tests/test-results.json, .tests/coverage-report.json
+**Command-specific extensions (not in workflow):**
 
 **Review findings integration** (from related review artifacts):
 - Extract critical/high findings as additional test scenarios, marked `source: "review_finding"`
@@ -88,7 +66,7 @@ Append to state.json.artifacts[]:
 ```
 
 **Next-step routing on completion:**
-- All tests pass → `/maestro-phase-transition {phase}`
+- All tests pass → `/maestro-milestone-audit`
 - Issues found, --auto-fix ran and succeeded → `/maestro-verify {phase}`
 - Issues found, --auto-fix ran but gaps remain → `/quality-debug --from-uat {phase}`
 - Issues found, manual fix needed → `/quality-debug --from-uat {phase}`

package/.claude/commands/spec-add.md

@@ -21,27 +21,7 @@ Each category maps 1:1 to a single target file — no dual-write.
 <context>
 $ARGUMENTS -- expects `<category> <content>`
 
-**Category-to-file mapping (1:1, same as spec-load):**
-| Category | Target file |
-|----------|------------|
-| `coding` | `coding-conventions.md` |
-| `arch` | `architecture-constraints.md` |
-| `quality` | `quality-rules.md` |
-| `debug` | `debug-notes.md` |
-| `test` | `test-conventions.md` |
-| `review` | `review-standards.md` |
-| `learning` | `learnings.md` |
-
-**Entry format (closed-tag):**
-```markdown
-<spec-entry category="{category}" keywords="{auto-extracted}" date="{YYYY-MM-DD}">
-
-### {title}
-
-{content}
-
-</spec-entry>
-```
+Category-to-file mapping (1:1) and entry format defined in workflow specs-add.md.
 </context>
 
 <execution>

package/.claude/commands/spec-load.md

@@ -20,22 +20,7 @@ Supports filtering by category (file-level) and keyword (entry-level via `<spec-
 <context>
 $ARGUMENTS -- optional flags and keyword
 
-**Category-to-file mapping (1:1, same as spec-add):**
-| Category | File loaded |
-|----------|------------|
-| `coding` | `coding-conventions.md` |
-| `arch` | `architecture-constraints.md` |
-| `quality` | `quality-rules.md` |
-| `debug` | `debug-notes.md` |
-| `test` | `test-conventions.md` |
-| `review` | `review-standards.md` |
-| `learning` | `learnings.md` |
-| `all` (default) | All spec files |
-
-**Flags:**
-- `--category <type>` — Filter by file category (loads one file)
-- `--keyword <word>` — Filter entries by keyword attribute in `<spec-entry>` tags. Searches across all files (or within category if combined)
-- `--with-lessons` — Also search `.workflow/learning/lessons.jsonl`
+Category-to-file mapping (1:1) and flag details defined in workflow specs-load.md.
 
 **Examples:**
 ```

package/.claude/commands/wiki-connect.md

@@ -24,121 +24,11 @@ Leverages maestro's unique wiki graph infrastructure (BM25 search, backlinks, he
 <context>
 Arguments: $ARGUMENTS
 
-**Flags:**
-- `--scope <type>` — Limit analysis to a wiki type (spec, memory, note, lesson, issue). Default: all types.
-- `--min-similarity N` — Minimum similarity score threshold 0.0-1.0 (default: 0.3)
-- `--fix` — Auto-apply the top suggestions by updating wiki entries with new `related` links
-- `--max N` — Maximum number of suggestions to generate (default: 20)
-
-**Storage written:**
-- `.workflow/learning/wiki-connections-{YYYY-MM-DD}.md` — Connection analysis report
-- If `--fix`: wiki entries updated via `maestro wiki update` with new `related` links
-- `.workflow/learning/lessons.jsonl` — Graph structure insights (source: "wiki-connect")
-
-**Storage read (via maestro wiki CLI, offline mode):**
-- `maestro wiki list --json` — All wiki entries
-- `maestro wiki graph` — Full graph structure (forward + backlinks)
-- `maestro wiki health` — Current health score
-- `maestro wiki orphans` — Orphaned entries
-- `maestro wiki hubs` — Hub entries (most referenced)
+Flags, storage paths, and CLI commands defined in workflow wiki-connect.md.
 </context>
 
 <execution>
-
-### Stage 1: Load Wiki State
-Run these `maestro wiki` commands in parallel:
-
-```bash
-maestro wiki list --json
-maestro wiki health
-maestro wiki orphans
-maestro wiki hubs --top 10
-```
-
-Parse results:
-- Entry count, type distribution
-- Baseline health score (from `wiki health`)
-- Orphan list (entries with 0 in-degree and 0 out-degree)
-- Hub list (most-referenced entries)
-
-Apply `--scope` filter if provided.
-
-### Stage 2: Identify Connection Candidates
-For each entry, compute potential connections:
-
-**2a. Orphan Rescue:**
-For each orphan entry, search for related entries using:
-- `maestro wiki search "<orphan title>"` — BM25 match by title
-- Tag overlap: entries sharing 2+ tags with the orphan
-- Same category: entries with matching `category`
-
-**2b. Missing Bidirectional Links:**
-For entries that have forward links but no corresponding backlink (A links to B, but B doesn't link to A), suggest adding the reverse link.
-
-**2c. Transitive Closure:**
-If A → B and B → C, but A has no link to C, and A and C share tags or category, suggest A → C.
-
-**2d. Type Bridge:**
-Entries of different types that reference the same concept (e.g., a `spec-auth` and a `lesson-auth-gotcha`) but aren't linked.
-
-### Stage 3: Score Candidates
-For each candidate connection (source → target), compute similarity:
-
-```
-score = 0.4 × tag_overlap_ratio
-      + 0.3 × title_bm25_similarity
-      + 0.2 × same_category_bonus
-      + 0.1 × type_bridge_bonus
-```
-
-- `tag_overlap_ratio`: shared_tags / max(source_tags, target_tags)
-- `title_bm25_similarity`: normalized BM25 score from wiki search
-- `same_category_bonus`: 1.0 if same category, else 0.0
-- `type_bridge_bonus`: 1.0 if different types, else 0.0
-
-Filter by `--min-similarity`, rank descending, limit to `--max`.
-
-### Stage 4: Present Suggestions
-Display ranked connection suggestions:
-
-```
-== Wiki Connection Suggestions ==
-Baseline health: 72/100 | Orphans: 8 | Broken links: 3
-
-#  Score  Source              → Target              Reason
-1  0.85   memory-auth-flow    → spec-auth           tag overlap (auth, security) + same phase
-2  0.71   note-cache-pattern  → spec-performance    title BM25 match + type bridge
-3  0.65   lesson-retry-fix    → spec-error-handling  tag overlap (error, retry)
-...
-
-Projected health after fix: 81/100 (+9)
-```
-
-If NOT `--fix`: display and exit.
-If `--fix`: proceed to Stage 5.
-
-### Stage 5: Apply Connections (--fix only)
-For each accepted suggestion:
-1. Get current entry: `maestro wiki get <source-id> --json`
-2. Extract existing `related` list from frontmatter
-3. Append target-id to `related` if not already present
-4. Update: `maestro wiki update <source-id> --frontmatter "related: [existing..., new-target]"`
-5. Log success/failure
-
-After all updates:
-- Re-run `maestro wiki health` to get new health score
-- Report delta
-
-### Stage 6: Persist & Report
-1. Write `.workflow/learning/wiki-connections-{date}.md` with:
-   - Baseline and final health scores
-   - All suggestions (applied and unapplied)
-   - Orphan rescue results
-   - Graph structure observations (hub concentration, type distribution)
-2. Append graph insights to `lessons.jsonl`:
-   - `source: "wiki-connect"`, `category: "technique"`
-   - e.g., "Auth-related entries are poorly connected", "Phase 3 has 5 orphaned notes"
-3. Display summary
+Follow '~/.maestro/workflows/wiki-connect.md' completely (Stages 1-6).
 
 **Next-step routing:**
 - Generate knowledge digest → `/wiki-digest <topic>`

package/.claude/commands/wiki-digest.md

@@ -28,150 +28,11 @@ Unlike `maestro wiki list` which shows raw entries, this command synthesizes and
 <context>
 Arguments: $ARGUMENTS
 
-**Scope resolution (auto-detected):**
-- `<topic>` — Search wiki for entries matching the topic via `maestro wiki search`
-- `--recent N` — Entries updated in the last N days
-- `--type <type>` — Filter by wiki type (spec, memory, note, lesson, issue)
-- No arguments — digest of the entire wiki
-
-**Flags:**
-- `--format brief` — Compact summary, one paragraph per theme (default)
-- `--format full` — Detailed digest with per-entry summaries and full gap analysis
-- `--create-issues` — Auto-create `type: "knowledge-gap"` entries in `.workflow/issues/issues.jsonl` for each identified gap (closes the discovery→action loop)
-
-**Storage written:**
-- `.workflow/learning/digest-{slug}-{YYYY-MM-DD}.md` — Digest document
-- `.workflow/learning/lessons.jsonl` — Meta-insights about knowledge structure (source: "wiki-digest")
-- `.workflow/issues/issues.jsonl` — Knowledge-gap issues (only when `--create-issues`)
-
-**Storage read (via maestro wiki CLI, offline mode):**
-- `maestro wiki list --json` — All entries (or filtered)
-- `maestro wiki search <topic>` — Topic-scoped entries
-- `maestro wiki get <id>` — Entry bodies for summarization
-- `maestro wiki backlinks <id>` / `maestro wiki forward <id>` — Relationship context
-- `maestro wiki health` — Overall graph health
-- `.workflow/learning/lessons.jsonl` — Cross-reference for unlinked insights
+Flags, scope resolution, storage paths, and CLI commands defined in workflow wiki-digest.md.
 </context>
 
 <execution>
-
-### Stage 1: Scope & Load
-- Parse arguments to determine scope:
-  - Topic: `maestro wiki search "<topic>" --json` → matching entries
-  - Recent N: `maestro wiki list --json` → filter by `updated` within N days
-  - Type: `maestro wiki list --type <type> --json`
-  - All: `maestro wiki list --json`
-- Load entry metadata (id, title, tags, status, type, related, summary)
-- For `--format full`: also load entry bodies via `maestro wiki get <id>` for top entries
-- Run `maestro wiki health` for baseline metrics
-
-### Stage 2: Theme Clustering
-Group entries into 3-5 semantic themes using:
-
-1. **Tag co-occurrence**: entries sharing 2+ tags belong to the same theme
-2. **Title similarity**: BM25-based grouping (entries whose titles match each other's keywords)
-3. **Relationship proximity**: entries connected by `related` links cluster together
-4. **Type grouping**: if entries are all same type, sub-cluster by content
-
-For each theme:
-- Name: most common tag or dominant keyword
-- Entry count
-- Type distribution within theme
-- Status distribution (draft/active/completed/archived)
-
-### Stage 3: Per-Theme Analysis
-For each theme, produce:
-
-**Summary paragraph**: synthesize the key knowledge in this theme area (what do these entries collectively say?)
-
-**Key entries**: top 3-5 most important entries (by hub score / backlink count)
-
-**Gap detection**:
-- Broken links: `[[references]]` that don't resolve within the theme
-- Orphans: entries in this theme with no connections
-- Questions: entries with `?` in title or "TODO" / "TBD" markers in body
-- Missing perspectives: if theme has specs but no lessons, or issues but no decisions
-
-**Health**: per-theme health score (adapted from wiki health formula)
-
-### Stage 4: Cross-Reference with Lessons
-- Search `lessons.jsonl` for insights related to each theme
-- Identify unlinked insights: lessons that match a theme but are not referenced by any wiki entry in that theme
-- Flag these as "knowledge not yet connected to the graph"
-
-### Stage 5: Coverage Heatmap
-Build a matrix showing knowledge density by type × theme:
-
-```
-              Theme 1    Theme 2    Theme 3    Theme 4    Theme 5
-spec          ███░░      ░░░░░      █████      ██░░░      ░░░░░
-memory        ░░░░░      ████░      ██░░░      ░░░░░      ███░░
-lesson        █░░░░      ██░░░      ████░      █░░░░      ░░░░░
-issue         ██░░░      ░░░░░      █░░░░      ███░░      ░░░░░
-
-Legend: █ = entries exist, ░ = sparse/missing
-```
-
-Identify: which theme × type cells are empty? These are knowledge gaps.
-
-### Stage 6: Write Digest
-Produce `.workflow/learning/digest-{slug}-{date}.md`:
-
-```markdown
-# Knowledge Digest: {scope description}
-**Generated:** {date} | **Entries:** {count} | **Health:** {score}/100
-
-## Themes
-
-### 1. {Theme Name} ({N} entries)
-{summary paragraph}
-
-**Key entries:** {linked entry IDs}
-**Gaps:** {list of missing knowledge}
-**Health:** {score}/100
-
-### 2. {Theme Name} ...
-
-## Coverage Heatmap
-{matrix}
-
-## Knowledge Gaps
-| Gap | Theme | Type Missing | Suggested Action |
-|-----|-------|-------------|-----------------|
-| No lessons for auth patterns | Security | lesson | Run /learn-decompose on src/auth/ |
-
-## Unlinked Insights
-{lessons.jsonl entries not connected to wiki graph}
-
-## Recommended Actions
-1. {action}: {reason}
-2. ...
-```
-
-### Stage 7: Gap → Issue Routing (if --create-issues)
-For each knowledge gap identified in Stage 5:
-1. Check `.workflow/issues/issues.jsonl` for existing gap with same theme + type
-2. If not duplicate, append to `issues.jsonl` using the canonical schema from `~/.maestro/workflows/issue.md` Step 4:
-   - `id`: `ISS-XXXXXXXX-NNN` format (8 hex hash + sequence)
-   - `title`: "Knowledge gap: {gap description}"
-   - `type`: "knowledge-gap"
-   - `status`: "open"
-   - `severity`: "low"
-   - `priority`: "low"
-   - `source`: "wiki-digest"
-   - `description`: "Theme: {theme}, Missing type: {type}. Suggested action: {action}"
-   - `tags`: ["knowledge-gap", "{theme-slug}"]
-   - `created`: ISO date
-   - `issue_history`: initial entry with `action: "created"`, `by: "wiki-digest"`, `timestamp`
-3. Report created issue count
-
-### Stage 8: Persist
-1. Write digest file
-2. Append meta-insights to `lessons.jsonl`:
-   - `source: "wiki-digest"`, `category: "technique"`
-   - e.g., "Auth knowledge is concentrated in specs but lacks lessons", "Security category has no decision entries"
-3. Update `learning-index.json`
-4. Display summary with key findings
+Follow '~/.maestro/workflows/wiki-digest.md' completely (Stages 1-8).
 
 **Next-step routing:**
 - Deep dive on a theme → `/learn-follow <wiki-id>`

package/.codex/skills/learn-decompose/SKILL.md

@@ -47,14 +47,8 @@ $ARGUMENTS — target path/module and optional flags.
 
 ### Phase 1: Session Init + Target Resolution
 
-```javascript
-const AUTO_YES = $ARGUMENTS.includes('-y') || $ARGUMENTS.includes('--yes')
-const patternsMatch = $ARGUMENTS.match(/--patterns\s+(\S+)/)
-const patternFilter = patternsMatch ? patternsMatch[1].split(',') : null
-const SAVE_SPEC = $ARGUMENTS.includes('--save-spec')
-const SAVE_WIKI = $ARGUMENTS.includes('--save-wiki')
-const target = $ARGUMENTS.replace(/--yes|-y|--continue|--concurrency\s+\d+|-c\s+\d+|--patterns\s+\S+|--save-spec|--save-wiki/g, '').trim()
-```
+Parse flags from `$ARGUMENTS`: `-y`/`--yes`, `--patterns <list>`, `--save-spec`, `--save-wiki`, `--continue`, `-c N`.
+Extract remaining text as target path/module.
 
 Resolve target to file list. Load existing patterns from `coding-conventions.md` + `lessons.jsonl` for dedup set.