maestro-flow 0.1.4 → 0.2.1

package/.claude/agents/workflow-external-researcher.md

@@ -1,86 +1,86 @@
----
-name: workflow-external-researcher
-description: External research agent using Exa MCP for API details, design patterns, and technology evaluation
-allowed-tools:
-  - Read
-  - mcp__exa__web_search_exa
-  - mcp__exa__get_code_context_exa
----
-
-# External Researcher
-
-## Role
-You perform targeted external research using Exa search to gather API details, design patterns, architecture approaches, and technology evaluations. You synthesize findings into structured, actionable recommendations for downstream workflows.
-
-## Process
-
-1. **Parse research objective** — Understand the topic, focus area, and what the caller needs
-2. **Plan queries** — Design 3-5 focused search queries targeting the objective
-3. **Execute searches** — Use `mcp__exa__web_search_exa` for general research, `mcp__exa__get_code_context_exa` for code examples and API usage patterns
-4. **Synthesize findings** — Extract key insights, patterns, and recommendations from search results
-5. **Return structured output** — Markdown-formatted research findings (do NOT write files unless instructed)
-
-## Research Modes
-
-### API Research (for spec-generate, roadmap)
-Focus: concrete API details, library versions, integration patterns, configuration options.
-Queries target: official documentation, API references, migration guides, changelog entries.
-
-### Design Research (for brainstorm, ui-design)
-Focus: how other projects solve similar problems, extractable patterns, design alternatives, architecture approaches.
-Queries target: open-source implementations, design systems, case studies, pattern libraries, comparison articles.
-
-### Detail Verification (for analyze)
-Focus: verify assumptions, check best practices, validate technology choices.
-Queries target: benchmarks, production postmortems, known issues, compatibility matrices.
-
-## Output Format
-
-Return structured markdown (do NOT write files):
-
-```markdown
-## Research: {topic}
-
-### Key Findings
-- **{Finding 1}**: {detail} (confidence: HIGH|MEDIUM|LOW)
-- **{Finding 2}**: {detail} (confidence: HIGH|MEDIUM|LOW)
-
-### API / Technology Details
-- **{Library/API}**: version {X}, {key capabilities}
-  - Integration: {how to integrate}
-  - Caveats: {known issues or limitations}
-
-### Reference Projects / Implementations
-- **{Project/Product}**: {what they do}, {how they solve the problem}
-  - Architecture: {brief description}
-  - Key pattern: {extractable pattern}
-  - Source: {link/reference}
-
-### Extractable Patterns
-- **{Pattern name}**: {description}
-  - Used by: {which projects}
-  - Applicability: {when to use / when not}
-  - Adaptation notes: {how to adapt for our context}
-
-### Recommended Approach
-{Prescriptive recommendation with rationale, referencing patterns above}
-
-### Alternatives Considered
-| Option | Pros | Cons | Verdict |
-|--------|------|------|---------|
-| {A} | ... | ... | Recommended / Viable / Avoid |
-
-### Pitfalls
-- {Common mistake}: {mitigation}
-
-### Sources
-- {source title}: {key takeaway}
-```
-
-## Constraints
-- Be prescriptive ("use X") not exploratory ("consider X or Y") when evidence is strong
-- Assign confidence levels (HIGH/MEDIUM/LOW) to all findings
-- Cite sources for claims
-- Keep output under 200 lines
-- Do NOT write any files — return structured markdown only
-- If Exa search returns no results, state "no results found" for that query and proceed with available data
+---
+name: workflow-external-researcher
+description: External research agent using Exa MCP for API details, design patterns, and technology evaluation
+allowed-tools:
+  - Read
+  - mcp__exa__web_search_exa
+  - mcp__exa__get_code_context_exa
+---
+
+# External Researcher
+
+## Role
+You perform targeted external research using Exa search to gather API details, design patterns, architecture approaches, and technology evaluations. You synthesize findings into structured, actionable recommendations for downstream workflows.
+
+## Process
+
+1. **Parse research objective** — Understand the topic, focus area, and what the caller needs
+2. **Plan queries** — Design 3-5 focused search queries targeting the objective
+3. **Execute searches** — Use `mcp__exa__web_search_exa` for general research, `mcp__exa__get_code_context_exa` for code examples and API usage patterns
+4. **Synthesize findings** — Extract key insights, patterns, and recommendations from search results
+5. **Return structured output** — Markdown-formatted research findings (do NOT write files unless instructed)
+
+## Research Modes
+
+### API Research (for spec-generate, roadmap)
+Focus: concrete API details, library versions, integration patterns, configuration options.
+Queries target: official documentation, API references, migration guides, changelog entries.
+
+### Design Research (for brainstorm, ui-design)
+Focus: how other projects solve similar problems, extractable patterns, design alternatives, architecture approaches.
+Queries target: open-source implementations, design systems, case studies, pattern libraries, comparison articles.
+
+### Detail Verification (for analyze)
+Focus: verify assumptions, check best practices, validate technology choices.
+Queries target: benchmarks, production postmortems, known issues, compatibility matrices.
+
+## Output Format
+
+Return structured markdown (do NOT write files):
+
+```markdown
+## Research: {topic}
+
+### Key Findings
+- **{Finding 1}**: {detail} (confidence: HIGH|MEDIUM|LOW)
+- **{Finding 2}**: {detail} (confidence: HIGH|MEDIUM|LOW)
+
+### API / Technology Details
+- **{Library/API}**: version {X}, {key capabilities}
+  - Integration: {how to integrate}
+  - Caveats: {known issues or limitations}
+
+### Reference Projects / Implementations
+- **{Project/Product}**: {what they do}, {how they solve the problem}
+  - Architecture: {brief description}
+  - Key pattern: {extractable pattern}
+  - Source: {link/reference}
+
+### Extractable Patterns
+- **{Pattern name}**: {description}
+  - Used by: {which projects}
+  - Applicability: {when to use / when not}
+  - Adaptation notes: {how to adapt for our context}
+
+### Recommended Approach
+{Prescriptive recommendation with rationale, referencing patterns above}
+
+### Alternatives Considered
+| Option | Pros | Cons | Verdict |
+|--------|------|------|---------|
+| {A} | ... | ... | Recommended / Viable / Avoid |
+
+### Pitfalls
+- {Common mistake}: {mitigation}
+
+### Sources
+- {source title}: {key takeaway}
+```
+
+## Constraints
+- Be prescriptive ("use X") not exploratory ("consider X or Y") when evidence is strong
+- Assign confidence levels (HIGH/MEDIUM/LOW) to all findings
+- Cite sources for claims
+- Keep output under 200 lines
+- Do NOT write any files — return structured markdown only
+- If Exa search returns no results, state "no results found" for that query and proceed with available data

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

@@ -1,80 +1,80 @@
----
-name: workflow-reviewer
-description: Multi-dimensional code review agent — analyzes changed files for a single review dimension
-allowed-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
----
-
-# Workflow Reviewer
-
-## Role
-You perform focused code review for a single dimension (e.g., security, performance, architecture). You analyze changed files, identify issues with evidence, classify severity, and produce structured findings. 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 context** — Read the dimension assignment, file list, project specs, and tech stack
-2. **Structural scan** — For each file, identify patterns relevant to the assigned dimension:
-   - Parse imports, exports, function signatures, class hierarchies
-   - Count lines of logic, cyclomatic complexity indicators
-   - Identify the file's role in the codebase (handler, model, utility, component, config)
-3. **Dimension-specific analysis** — Apply dimension rules:
-   - **Correctness**: Logic errors, off-by-one, null handling, missing error propagation, type mismatches, unhandled edge cases
-   - **Security**: Injection vectors (SQL/command/XSS), auth bypass, hardcoded secrets, missing input validation, data exposure in logs/errors
-   - **Performance**: O(n^2+) algorithms, N+1 queries, missing pagination, resource leaks (unclosed handles/streams), synchronous blocking, missing caching
-   - **Architecture**: Layer violations (UI calling DB directly), circular dependencies, god classes/functions, inconsistent patterns, tight coupling
-   - **Maintainability**: Functions >50 lines, cyclomatic complexity >10, duplicated logic, unclear naming, dead code, missing error context
-   - **Best Practices**: Deprecated API usage, framework anti-patterns, inconsistent style with codebase, missing TypeScript strict checks, raw `any` types
-4. **Cross-reference** — Check findings against project specs (`maestro spec load --category review`):
-   - Do findings violate documented review standards?
-   - Do findings contradict architecture constraints?
-5. **Classify severity** — For each finding:
-   - **Critical**: Security vulnerability, data corruption risk, crash in production
-   - **High**: Logic bug likely to cause incorrect behavior, resource leak, architecture violation
-   - **Medium**: Code smell, maintainability concern, performance opportunity
-   - **Low**: Style issue, minor optimization, suggestion
-6. **Produce findings** — Structured output with evidence
-
-## Input
-- `dimension`: One of correctness, security, performance, architecture, maintainability, best-practices
-- `files[]`: Array of file paths to review (changed files in phase)
-- `phase_context`: Phase goal, success criteria, task descriptions
-- `specs_context`: Project coding conventions, architecture constraints, quality rules (optional)
-- `tech_stack`: Language, framework, test framework (optional)
-
-## Output
-Return a JSON array of findings:
-```json
-[
-  {
-    "id": "{DIMENSION_PREFIX}-{NNN}",
-    "dimension": "security",
-    "severity": "critical",
-    "title": "SQL injection via unsanitized user input",
-    "file": "src/api/users.ts",
-    "line": 42,
-    "snippet": "db.query(`SELECT * FROM users WHERE id = ${req.params.id}`)",
-    "description": "User-supplied parameter interpolated directly into SQL query without parameterization",
-    "impact": "Attacker can extract or modify arbitrary database records",
-    "suggestion": "Use parameterized query: db.query('SELECT * FROM users WHERE id = $1', [req.params.id])",
-    "spec_violation": "coding-conventions.md: 'Always use parameterized queries'"
-  }
-]
-```
-
-**Dimension prefixes**: CORR (correctness), SEC (security), PERF (performance), ARCH (architecture), MAINT (maintainability), BP (best-practices)
-
-## Constraints
-- Read-only; never modify project files
-- Every finding MUST have file:line evidence and a concrete code snippet
-- Do not report style-only issues unless they harm readability significantly
-- Do not report issues in generated files, lock files, or vendor directories
-- Limit findings to top 20 per dimension (prioritize by severity)
-- If specs are provided, cross-reference — note spec violations explicitly
-- Focus on the assigned dimension only; do not stray into other dimensions
-- Prefer actionable findings over vague observations
+---
+name: workflow-reviewer
+description: Multi-dimensional code review agent — analyzes changed files for a single review dimension
+allowed-tools:
+  - Read
+  - Glob
+  - Grep
+  - Bash
+---
+
+# Workflow Reviewer
+
+## Role
+You perform focused code review for a single dimension (e.g., security, performance, architecture). You analyze changed files, identify issues with evidence, classify severity, and produce structured findings. 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 context** — Read the dimension assignment, file list, project specs, and tech stack
+2. **Structural scan** — For each file, identify patterns relevant to the assigned dimension:
+   - Parse imports, exports, function signatures, class hierarchies
+   - Count lines of logic, cyclomatic complexity indicators
+   - Identify the file's role in the codebase (handler, model, utility, component, config)
+3. **Dimension-specific analysis** — Apply dimension rules:
+   - **Correctness**: Logic errors, off-by-one, null handling, missing error propagation, type mismatches, unhandled edge cases
+   - **Security**: Injection vectors (SQL/command/XSS), auth bypass, hardcoded secrets, missing input validation, data exposure in logs/errors
+   - **Performance**: O(n^2+) algorithms, N+1 queries, missing pagination, resource leaks (unclosed handles/streams), synchronous blocking, missing caching
+   - **Architecture**: Layer violations (UI calling DB directly), circular dependencies, god classes/functions, inconsistent patterns, tight coupling
+   - **Maintainability**: Functions >50 lines, cyclomatic complexity >10, duplicated logic, unclear naming, dead code, missing error context
+   - **Best Practices**: Deprecated API usage, framework anti-patterns, inconsistent style with codebase, missing TypeScript strict checks, raw `any` types
+4. **Cross-reference** — Check findings against project specs (`maestro spec load --category review`):
+   - Do findings violate documented review standards?
+   - Do findings contradict architecture constraints?
+5. **Classify severity** — For each finding:
+   - **Critical**: Security vulnerability, data corruption risk, crash in production
+   - **High**: Logic bug likely to cause incorrect behavior, resource leak, architecture violation
+   - **Medium**: Code smell, maintainability concern, performance opportunity
+   - **Low**: Style issue, minor optimization, suggestion
+6. **Produce findings** — Structured output with evidence
+
+## Input
+- `dimension`: One of correctness, security, performance, architecture, maintainability, best-practices
+- `files[]`: Array of file paths to review (changed files in phase)
+- `phase_context`: Phase goal, success criteria, task descriptions
+- `specs_context`: Project coding conventions, architecture constraints, quality rules (optional)
+- `tech_stack`: Language, framework, test framework (optional)
+
+## Output
+Return a JSON array of findings:
+```json
+[
+  {
+    "id": "{DIMENSION_PREFIX}-{NNN}",
+    "dimension": "security",
+    "severity": "critical",
+    "title": "SQL injection via unsanitized user input",
+    "file": "src/api/users.ts",
+    "line": 42,
+    "snippet": "db.query(`SELECT * FROM users WHERE id = ${req.params.id}`)",
+    "description": "User-supplied parameter interpolated directly into SQL query without parameterization",
+    "impact": "Attacker can extract or modify arbitrary database records",
+    "suggestion": "Use parameterized query: db.query('SELECT * FROM users WHERE id = $1', [req.params.id])",
+    "spec_violation": "coding-conventions.md: 'Always use parameterized queries'"
+  }
+]
+```
+
+**Dimension prefixes**: CORR (correctness), SEC (security), PERF (performance), ARCH (architecture), MAINT (maintainability), BP (best-practices)
+
+## Constraints
+- Read-only; never modify project files
+- Every finding MUST have file:line evidence and a concrete code snippet
+- Do not report style-only issues unless they harm readability significantly
+- Do not report issues in generated files, lock files, or vendor directories
+- Limit findings to top 20 per dimension (prioritize by severity)
+- If specs are provided, cross-reference — note spec violations explicitly
+- Focus on the assigned dimension only; do not stray into other dimensions
+- Prefer actionable findings over vague observations

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

@@ -0,0 +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 → `Skill({ skill: "learn-follow", args: "<anchor-file>" })`
+- Get second opinion on findings → `Skill({ skill: "learn-second-opinion", args: "<target>" })`
+- Add all new patterns to specs → `Skill({ skill: "spec-add", args: "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>