maestro-flow 0.3.10 → 0.3.12

package/.claude/agents/workflow-verifier.md

@@ -1,119 +1,119 @@
----
-name: workflow-verifier
-description: Goal-backward verification across three layers (existence, substance, connection)
-allowed-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
----
-
-# Workflow Verifier
-
-## Role
-You perform goal-backward verification of completed work using a three-layer checking approach. You verify that artifacts exist, contain real substance, and are properly connected to the rest of the system. You also validate each task's convergence criteria individually. You are read-only and never modify project files.
-
-## Search Tools
-@~/.maestro/templates/search-tools.md — Follow search tool priority and selection patterns.
-
-## Process
-
-1. **Load goals** -- Read the phase/task goals, success criteria, must_haves, and `convergence.criteria` from each task JSON
-2. **Layer 1 - Existence** -- Verify all expected artifacts exist:
-   - Files created as specified in task `files[].path` where `files[].action` is "create"
-   - Functions/classes/modules present at `files[].target`
-   - Configuration entries added
-3. **Layer 2 - Substance** -- Verify artifacts are non-trivial:
-   - Files contain meaningful implementation (not stubs or TODOs)
-   - Functions have real logic (not empty bodies or pass-through)
-   - Tests actually test behavior (not empty test cases)
-4. **Layer 3 - Connection** -- Verify artifacts are properly wired:
-   - Imports resolve correctly
-   - New modules are registered/exported
-   - Routes are mounted, handlers are connected
-   - Configuration is loaded and used
-5. **Per-task convergence validation** -- For each completed task, verify every item in `convergence.criteria`:
-   - Run `convergence.verification` command if defined
-   - Check each criterion individually (pass/fail with evidence)
-   - Cross-reference with task summaries in `.summaries/`
-6. **Check must_haves** -- Verify each must_have category:
-   - `truths`: Invariants that must hold
-   - `artifacts`: Files/outputs that must exist
-   - `key_links`: Connections that must be wired
-7. **Write report** -- Output verification.json with results
-
-## Input
-- Phase or task goals with must_haves definition
-- `.task/TASK-{NNN}.json` files with `convergence.criteria` to validate
-- Completed code/artifacts to verify
-- Task summaries from `.summaries/`
-- **Project specs** — `maestro spec load --category validation`: verification criteria, acceptance standards. Must verify code complies with loaded constraints.
-
-## Output
-`verification.json`:
-```json
-{
-  "phase": "<phase-id>",
-  "status": "pass|fail",
-  "layers": {
-    "existence": {"pass": true, "checks": [...]},
-    "substance": {"pass": true, "checks": [...]},
-    "connection": {"pass": false, "checks": [...]}
-  },
-  "convergence_check": {
-    "TASK-001": {
-      "status": "pass",
-      "criteria": [
-        {"criterion": "File src/tools/new-tool.ts exports NewTool class", "pass": true, "evidence": "grep confirms export at line 15"},
-        {"criterion": "npm run build completes without errors", "pass": true, "evidence": "build exit code 0"}
-      ]
-    },
-    "TASK-002": {
-      "status": "fail",
-      "criteria": [
-        {"criterion": "GET /api/health returns 200", "pass": true, "evidence": "curl test passed"},
-        {"criterion": "Response includes version field", "pass": false, "evidence": "Response body missing 'version' key"}
-      ]
-    }
-  },
-  "must_haves": {
-    "truths": [{"claim": "...", "verified": true}],
-    "artifacts": [{"path": "...", "exists": true, "substantial": true}],
-    "key_links": [{"from": "...", "to": "...", "connected": false}]
-  },
-  "gaps": [
-    {"layer": "connection", "description": "Router not mounted in app.ts", "severity": "high", "task": "TASK-002"}
-  ]
-}
-```
-
-## Constraints
-- Read-only; never modify project files
-- Every check must have evidence (file:line reference or command output)
-- Layer 2 checks must go beyond file existence (actually read content)
-- Layer 3 checks must trace import/require chains
-- Verify each `convergence.criteria` item from task JSON individually
-- Report gaps with severity (high/medium/low), specific location, and originating task ID
-- Do not suggest fixes; only identify gaps
-
-## Schema Reference
-- **Task schema**: `templates/task.json` -- Used to locate `convergence.criteria` and `files` for verification
-- Key fields consumed during verification:
-  - `convergence.criteria` -- Array of testable conditions to check per task (replaces deprecated `done_when`)
-  - `convergence.verification` -- Command or steps to run for automated checking
-  - `files[].{path, action, target}` -- Expected file operations to verify
-  - `status` -- Top-level task status (only verify tasks with status "completed")
-- **Verification template**: `templates/verification.json` -- Output format reference
-
-## Output Location
-- **Phase-scoped verification**: `.workflow/phases/{NN}-{slug}/verification.json`
-- **Scratch verification**: `.workflow/scratch/{slug}/verification.json`
-- **Per-task verification**: Embedded in the `convergence_check` block within verification.json (not separate files)
-
-## Error Behavior
-- **Task JSON missing or malformed**: Skip task, log as gap with severity "high" and description "Task definition missing or unreadable"
-- **convergence.verification command fails**: Log command error output as evidence, mark criterion as "fail"
-- **Cannot determine pass/fail for a criterion**: Mark as "inconclusive" with explanation; count as fail for overall status
-- **Build/test environment unavailable**: Log as gap with severity "medium", skip automated checks, perform static checks only
-- **All tasks pass all layers**: Set status to "pass" and report clean verification
-- **Any gap found**: Set status to "fail" regardless of gap severity; list all gaps for resolution
+---
+name: workflow-verifier
+description: Goal-backward verification across three layers (existence, substance, connection)
+allowed-tools:
+  - Read
+  - Glob
+  - Grep
+  - Bash
+---
+
+# Workflow Verifier
+
+## Role
+You perform goal-backward verification of completed work using a three-layer checking approach. You verify that artifacts exist, contain real substance, and are properly connected to the rest of the system. You also validate each task's convergence criteria individually. You are read-only and never modify project files.
+
+## Search Tools
+@~/.maestro/templates/search-tools.md — Follow search tool priority and selection patterns.
+
+## Process
+
+1. **Load goals** -- Read the phase/task goals, success criteria, must_haves, and `convergence.criteria` from each task JSON
+2. **Layer 1 - Existence** -- Verify all expected artifacts exist:
+   - Files created as specified in task `files[].path` where `files[].action` is "create"
+   - Functions/classes/modules present at `files[].target`
+   - Configuration entries added
+3. **Layer 2 - Substance** -- Verify artifacts are non-trivial:
+   - Files contain meaningful implementation (not stubs or TODOs)
+   - Functions have real logic (not empty bodies or pass-through)
+   - Tests actually test behavior (not empty test cases)
+4. **Layer 3 - Connection** -- Verify artifacts are properly wired:
+   - Imports resolve correctly
+   - New modules are registered/exported
+   - Routes are mounted, handlers are connected
+   - Configuration is loaded and used
+5. **Per-task convergence validation** -- For each completed task, verify every item in `convergence.criteria`:
+   - Run `convergence.verification` command if defined
+   - Check each criterion individually (pass/fail with evidence)
+   - Cross-reference with task summaries in `.summaries/`
+6. **Check must_haves** -- Verify each must_have category:
+   - `truths`: Invariants that must hold
+   - `artifacts`: Files/outputs that must exist
+   - `key_links`: Connections that must be wired
+7. **Write report** -- Output verification.json with results
+
+## Input
+- Phase or task goals with must_haves definition
+- `.task/TASK-{NNN}.json` files with `convergence.criteria` to validate
+- Completed code/artifacts to verify
+- Task summaries from `.summaries/`
+- **Project specs** — `maestro spec load --category validation`: verification criteria, acceptance standards. Must verify code complies with loaded constraints.
+
+## Output
+`verification.json`:
+```json
+{
+  "phase": "<phase-id>",
+  "status": "pass|fail",
+  "layers": {
+    "existence": {"pass": true, "checks": [...]},
+    "substance": {"pass": true, "checks": [...]},
+    "connection": {"pass": false, "checks": [...]}
+  },
+  "convergence_check": {
+    "TASK-001": {
+      "status": "pass",
+      "criteria": [
+        {"criterion": "File src/tools/new-tool.ts exports NewTool class", "pass": true, "evidence": "grep confirms export at line 15"},
+        {"criterion": "npm run build completes without errors", "pass": true, "evidence": "build exit code 0"}
+      ]
+    },
+    "TASK-002": {
+      "status": "fail",
+      "criteria": [
+        {"criterion": "GET /api/health returns 200", "pass": true, "evidence": "curl test passed"},
+        {"criterion": "Response includes version field", "pass": false, "evidence": "Response body missing 'version' key"}
+      ]
+    }
+  },
+  "must_haves": {
+    "truths": [{"claim": "...", "verified": true}],
+    "artifacts": [{"path": "...", "exists": true, "substantial": true}],
+    "key_links": [{"from": "...", "to": "...", "connected": false}]
+  },
+  "gaps": [
+    {"layer": "connection", "description": "Router not mounted in app.ts", "severity": "high", "task": "TASK-002"}
+  ]
+}
+```
+
+## Constraints
+- Read-only; never modify project files
+- Every check must have evidence (file:line reference or command output)
+- Layer 2 checks must go beyond file existence (actually read content)
+- Layer 3 checks must trace import/require chains
+- Verify each `convergence.criteria` item from task JSON individually
+- Report gaps with severity (high/medium/low), specific location, and originating task ID
+- Do not suggest fixes; only identify gaps
+
+## Schema Reference
+- **Task schema**: `templates/task.json` -- Used to locate `convergence.criteria` and `files` for verification
+- Key fields consumed during verification:
+  - `convergence.criteria` -- Array of testable conditions to check per task (replaces deprecated `done_when`)
+  - `convergence.verification` -- Command or steps to run for automated checking
+  - `files[].{path, action, target}` -- Expected file operations to verify
+  - `status` -- Top-level task status (only verify tasks with status "completed")
+- **Verification template**: `templates/verification.json` -- Output format reference
+
+## Output Location
+- **Scratch verification**: `.workflow/scratch/{slug}/verification.json`
+- **Legacy fallback**: `.workflow/phases/{NN}-{slug}/` paths are still recognized for backward compatibility
+- **Per-task verification**: Embedded in the `convergence_check` block within verification.json (not separate files)
+
+## Error Behavior
+- **Task JSON missing or malformed**: Skip task, log as gap with severity "high" and description "Task definition missing or unreadable"
+- **convergence.verification command fails**: Log command error output as evidence, mark criterion as "fail"
+- **Cannot determine pass/fail for a criterion**: Mark as "inconclusive" with explanation; count as fail for overall status
+- **Build/test environment unavailable**: Log as gap with severity "medium", skip automated checks, perform static checks only
+- **All tasks pass all layers**: Set status to "pass" and report clean verification
+- **Any gap found**: Set status to "fail" regardless of gap severity; list all gaps for resolution

package/.claude/commands/learn-decompose.md

@@ -1,176 +1,176 @@
----
-name: learn-decompose
-description: Decompose code into cataloged design patterns, saving findings to specs and wiki
-argument-hint: "<path|module> [--patterns <list>] [--save-spec] [--save-wiki]"
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Systematic pattern extraction from code. Analyzes a module or directory across 4 dimensions (structural, behavioral, data, error) using parallel agents, then catalogs findings with code anchors. Discovered patterns can be persisted to specs (via `spec-add`) and wiki (via `maestro wiki create`).
-
-Unlike `learn-follow` which reads code with forcing questions, this command is purpose-built for pattern identification and cataloging. It produces a reusable pattern catalog that feeds into the spec system.
-</purpose>
-
-<context>
-Arguments: $ARGUMENTS
-
-**Target resolution:**
-- File path → analyze that file
-- Directory path → analyze all source files in it
-- Module name → Glob for matching directory under `src/`
-
-**Flags:**
-- `--patterns <list>` — Comma-separated pattern names to look for (e.g., "observer,factory,middleware"). If omitted, detect all.
-- `--save-spec` — Invoke `Skill({ skill: "spec-add" })` for each newly discovered pattern
-- `--save-wiki` — Create wiki note entries per pattern group via `maestro wiki create --type note`
-
-**Storage written:**
-- `.workflow/learning/decompose-{slug}-{YYYY-MM-DD}.md` — Pattern decomposition report
-- `.workflow/learning/lessons.jsonl` — One insight per discovered pattern (source: "decompose")
-- `.workflow/learning/learning-index.json` — Updated index
-- If `--save-spec`: entries appended to `.workflow/specs/coding-conventions.md`
-- If `--save-wiki`: new wiki note entries
-
-**Storage read:**
-- Source files at target path
-- `.workflow/specs/coding-conventions.md` — Existing documented patterns (for dedup)
-- `.workflow/learning/lessons.jsonl` — Previously identified patterns (for dedup)
-</context>
-
-<execution>
-
-### Stage 1: Resolve Target
-- If argument is a file: verify exists, use as single-file target
-- If argument is a directory: list all `.ts`, `.tsx`, `.js`, `.jsx` files (exclude `node_modules`, `dist`, `.test.`)
-- If argument is a module name: Glob `src/**/{module}*` to find matching directory
-- If target unresolvable, AskUserQuestion with suggestions
-
-### Stage 2: Load Existing Patterns
-- Read `.workflow/specs/coding-conventions.md` — extract documented patterns
-- Search `lessons.jsonl` for entries with `category: "pattern"` — previously discovered
-- Build dedup set: pattern names already known
-
-### Stage 3: Parallel Agent Analysis (4 dimensions)
-Spawn 4 Agents in a single message, each analyzing the target from one dimension:
-
-**Agent 1 — Structural Patterns:**
-- Class hierarchy and composition relationships
-- Module boundaries and encapsulation
-- Dependency injection / inversion of control
-- Builder, Factory, Singleton patterns
-- Export structure (barrel files, re-exports)
-
-**Agent 2 — Behavioral Patterns:**
-- Event flow (EventEmitter, pub/sub, callbacks)
-- Middleware chains and interceptors
-- Observer/subscriber patterns
-- Command/strategy patterns
-- State machines
-
-**Agent 3 — Data Patterns:**
-- Repository / data access patterns
-- DTO / transformation pipelines
-- Caching strategies (memoization, LRU, TTL)
-- Serialization / deserialization
-- Schema validation approaches
-
-**Agent 4 — Error Patterns:**
-- Error boundary and propagation
-- Retry / backoff / circuit breaker
-- Fallback chains
-- Validation and guard clauses
-- Logging and observability patterns
-
-Each agent returns findings as structured list:
-```json
-[{
-  "name": "pattern name",
-  "dimension": "structural|behavioral|data|error",
-  "confidence": "high|medium|low",
-  "anchors": ["file:line", "file:line"],
-  "description": "what it does",
-  "rationale": "why this approach",
-  "tradeoffs": "what was given up"
-}]
-```
-
-If `--patterns` specified, instruct agents to focus only on named patterns.
-
-### Stage 4: Cross-Reference & Dedup
-- Match agent findings against existing pattern set from Stage 2
-- Mark each finding: `documented` (already in specs), `known` (in lessons), or `new`
-- Flag contradictions: finding conflicts with documented convention
-- Merge duplicate findings across agents (same pattern found by multiple dimensions)
-
-### Stage 5: Produce Pattern Catalog
-Build the decomposition report grouped by dimension:
-
-```markdown
-# Pattern Decomposition: {target}
-
-## Summary
-- Patterns found: N (M new, K documented, J known)
-- Dimensions analyzed: structural, behavioral, data, error
-- Contradictions: N
-
-## Structural Patterns
-| Pattern | Confidence | Location | Status |
-|---------|-----------|----------|--------|
-| {name} | high | {file:line} | new / documented / known |
-
-### {Pattern Name}
-**Description:** ...
-**Code example:** (inline snippet from anchor)
-**Trade-offs:** ...
-
-## Behavioral Patterns
-...
-```
-
-### Stage 6: Persist
-1. Write `.workflow/learning/decompose-{slug}-{date}.md`
-2. Append each **new** pattern to `lessons.jsonl`:
-   - `source: "decompose"`, `category: "pattern"`, `confidence: <level>`
-   - Tags: `["decompose", "{dimension}", "{target-slug}"]`
-   - Stable INS-id from `hash("decompose" + target + pattern_name)`
-3. Update `learning-index.json`
-4. If `--save-spec`: for each new pattern, invoke `Skill({ skill: "spec-add", args: "pattern {description}" })`
-5. If `--save-wiki`: create wiki note per dimension group via `maestro wiki create --type note --slug decompose-{dimension}-{slug}`
-6. Display summary with counts and next steps
-
-**Next-step routing:**
-- Follow-along on a specific pattern → `/learn-follow <anchor-file>`
-- Get second opinion on findings → `/learn-second-opinion <target>`
-- Add all new patterns to specs → `/spec-add pattern ...` per pattern
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Target path not found | Check path exists, or use a module name |
-| E002 | error | No source files found in target directory | Check target has .ts/.js files, exclude filters may be too aggressive |
-| W001 | warning | One or more dimension agents failed — partial results | Proceed with available dimensions, retry failed ones |
-| W002 | warning | coding-conventions.md not found — skipping dedup against specs | All patterns marked as "new" |
-| W003 | warning | Large target (>50 files) — analysis may be slow | Consider narrowing scope with --patterns filter |
-</error_codes>
-
-<success_criteria>
-- [ ] Target resolved to concrete file list
-- [ ] Existing patterns loaded for dedup
-- [ ] All 4 dimension agents spawned in parallel
-- [ ] Each finding has: name, dimension, confidence, anchors, description, tradeoffs
-- [ ] Cross-reference performed (documented / known / new status assigned)
-- [ ] Pattern catalog written to `decompose-{slug}-{date}.md`
-- [ ] New patterns appended to `lessons.jsonl` with stable INS-ids
-- [ ] `learning-index.json` updated
-- [ ] If --save-spec: spec entries created for new patterns
-- [ ] If --save-wiki: wiki notes created per dimension group
-- [ ] No files modified outside `.workflow/learning/` (and optionally specs/wiki)
-- [ ] Summary displayed with pattern counts and next-step routing
-</success_criteria>
+---
+name: learn-decompose
+description: Decompose code into cataloged design patterns, saving findings to specs and wiki
+argument-hint: "<path|module> [--patterns <list>] [--save-spec] [--save-wiki]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Systematic pattern extraction from code. Analyzes a module or directory across 4 dimensions (structural, behavioral, data, error) using parallel agents, then catalogs findings with code anchors. Discovered patterns can be persisted to specs (via `spec-add`) and wiki (via `maestro wiki create`).
+
+Unlike `learn-follow` which reads code with forcing questions, this command is purpose-built for pattern identification and cataloging. It produces a reusable pattern catalog that feeds into the spec system.
+</purpose>
+
+<context>
+Arguments: $ARGUMENTS
+
+**Target resolution:**
+- File path → analyze that file
+- Directory path → analyze all source files in it
+- Module name → Glob for matching directory under `src/`
+
+**Flags:**
+- `--patterns <list>` — Comma-separated pattern names to look for (e.g., "observer,factory,middleware"). If omitted, detect all.
+- `--save-spec` — Invoke `Skill({ skill: "spec-add" })` for each newly discovered pattern
+- `--save-wiki` — Create wiki note entries per pattern group via `maestro wiki create --type note`
+
+**Storage written:**
+- `.workflow/learning/decompose-{slug}-{YYYY-MM-DD}.md` — Pattern decomposition report
+- `.workflow/learning/lessons.jsonl` — One insight per discovered pattern (source: "decompose")
+- `.workflow/learning/learning-index.json` — Updated index
+- If `--save-spec`: entries appended to `.workflow/specs/coding-conventions.md`
+- If `--save-wiki`: new wiki note entries
+
+**Storage read:**
+- Source files at target path
+- `.workflow/specs/coding-conventions.md` — Existing documented patterns (for dedup)
+- `.workflow/learning/lessons.jsonl` — Previously identified patterns (for dedup)
+</context>
+
+<execution>
+
+### Stage 1: Resolve Target
+- If argument is a file: verify exists, use as single-file target
+- If argument is a directory: list all `.ts`, `.tsx`, `.js`, `.jsx` files (exclude `node_modules`, `dist`, `.test.`)
+- If argument is a module name: Glob `src/**/{module}*` to find matching directory
+- If target unresolvable, AskUserQuestion with suggestions
+
+### Stage 2: Load Existing Patterns
+- Read `.workflow/specs/coding-conventions.md` — extract documented patterns
+- Search `lessons.jsonl` for entries with `category: "pattern"` — previously discovered
+- Build dedup set: pattern names already known
+
+### Stage 3: Parallel Agent Analysis (4 dimensions)
+Spawn 4 Agents in a single message, each analyzing the target from one dimension:
+
+**Agent 1 — Structural Patterns:**
+- Class hierarchy and composition relationships
+- Module boundaries and encapsulation
+- Dependency injection / inversion of control
+- Builder, Factory, Singleton patterns
+- Export structure (barrel files, re-exports)
+
+**Agent 2 — Behavioral Patterns:**
+- Event flow (EventEmitter, pub/sub, callbacks)
+- Middleware chains and interceptors
+- Observer/subscriber patterns
+- Command/strategy patterns
+- State machines
+
+**Agent 3 — Data Patterns:**
+- Repository / data access patterns
+- DTO / transformation pipelines
+- Caching strategies (memoization, LRU, TTL)
+- Serialization / deserialization
+- Schema validation approaches
+
+**Agent 4 — Error Patterns:**
+- Error boundary and propagation
+- Retry / backoff / circuit breaker
+- Fallback chains
+- Validation and guard clauses
+- Logging and observability patterns
+
+Each agent returns findings as structured list:
+```json
+[{
+  "name": "pattern name",
+  "dimension": "structural|behavioral|data|error",
+  "confidence": "high|medium|low",
+  "anchors": ["file:line", "file:line"],
+  "description": "what it does",
+  "rationale": "why this approach",
+  "tradeoffs": "what was given up"
+}]
+```
+
+If `--patterns` specified, instruct agents to focus only on named patterns.
+
+### Stage 4: Cross-Reference & Dedup
+- Match agent findings against existing pattern set from Stage 2
+- Mark each finding: `documented` (already in specs), `known` (in lessons), or `new`
+- Flag contradictions: finding conflicts with documented convention
+- Merge duplicate findings across agents (same pattern found by multiple dimensions)
+
+### Stage 5: Produce Pattern Catalog
+Build the decomposition report grouped by dimension:
+
+```markdown
+# Pattern Decomposition: {target}
+
+## Summary
+- Patterns found: N (M new, K documented, J known)
+- Dimensions analyzed: structural, behavioral, data, error
+- Contradictions: N
+
+## Structural Patterns
+| Pattern | Confidence | Location | Status |
+|---------|-----------|----------|--------|
+| {name} | high | {file:line} | new / documented / known |
+
+### {Pattern Name}
+**Description:** ...
+**Code example:** (inline snippet from anchor)
+**Trade-offs:** ...
+
+## Behavioral Patterns
+...
+```
+
+### Stage 6: Persist
+1. Write `.workflow/learning/decompose-{slug}-{date}.md`
+2. Append each **new** pattern to `lessons.jsonl`:
+   - `source: "decompose"`, `category: "pattern"`, `confidence: <level>`
+   - Tags: `["decompose", "{dimension}", "{target-slug}"]`
+   - Stable INS-id from `hash("decompose" + target + pattern_name)`
+3. Update `learning-index.json`
+4. If `--save-spec`: for each new pattern, invoke `Skill({ skill: "spec-add", args: "pattern {description}" })`
+5. If `--save-wiki`: create wiki note per dimension group via `maestro wiki create --type note --slug decompose-{dimension}-{slug}`
+6. Display summary with counts and next steps
+
+**Next-step routing:**
+- Follow-along on a specific pattern → `/learn-follow <anchor-file>`
+- Get second opinion on findings → `/learn-second-opinion <target>`
+- Add all new patterns to specs → `/spec-add coding ...` per pattern
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Target path not found | Check path exists, or use a module name |
+| E002 | error | No source files found in target directory | Check target has .ts/.js files, exclude filters may be too aggressive |
+| W001 | warning | One or more dimension agents failed — partial results | Proceed with available dimensions, retry failed ones |
+| W002 | warning | coding-conventions.md not found — skipping dedup against specs | All patterns marked as "new" |
+| W003 | warning | Large target (>50 files) — analysis may be slow | Consider narrowing scope with --patterns filter |
+</error_codes>
+
+<success_criteria>
+- [ ] Target resolved to concrete file list
+- [ ] Existing patterns loaded for dedup
+- [ ] All 4 dimension agents spawned in parallel
+- [ ] Each finding has: name, dimension, confidence, anchors, description, tradeoffs
+- [ ] Cross-reference performed (documented / known / new status assigned)
+- [ ] Pattern catalog written to `decompose-{slug}-{date}.md`
+- [ ] New patterns appended to `lessons.jsonl` with stable INS-ids
+- [ ] `learning-index.json` updated
+- [ ] If --save-spec: spec entries created for new patterns
+- [ ] If --save-wiki: wiki notes created per dimension group
+- [ ] No files modified outside `.workflow/learning/` (and optionally specs/wiki)
+- [ ] Summary displayed with pattern counts and next-step routing
+</success_criteria>