maestro-flow 0.3.37 → 0.3.39

package/workflows/issue-gaps-analyze.codex.md

@@ -0,0 +1,260 @@
+# Workflow: Issue Gaps Analysis (Codex — CSV Wave)
+
+Root cause analysis for issues via `spawn_agents_on_csv` wave execution.
+Supports single issue (ISS-ID) or batch with classification and parallel analysis.
+Produces analysis records in issues.jsonl and context.md for downstream `plan --gaps`.
+
+**Invoked by**: `maestro-analyze --gaps [ISS-ID]` (codex SKILL.md)
+
+## Pipeline
+
+```
+Load Issues → Classify & Group → Generate tasks.csv → Wave 1: Explore (parallel per issue) → Wave 2: Synthesize (per group) → Write issue.analysis → Output context.md
+```
+
+---
+
+### Step 1: Load Issues
+
+```
+If ISS-ID provided:
+  Load single issue from .workflow/issues/issues.jsonl
+  → fatal if file missing or ID not found (E_ISSUE_NOT_FOUND)
+  → skip Step 2 (single issue = single group)
+
+If no ISS-ID:
+  Load all issues where status == "open" || status == "registered"
+  → fatal if none found (E_NO_ISSUES)
+```
+
+---
+
+### Step 2: Classify & Group (batch mode only)
+
+```
+Group loaded issues by affected area overlap:
+
+Classification dimensions:
+  - location: file path prefix (first 2 segments, e.g. src/auth/)
+  - component: affected_components field overlap
+  - category: issue.category or severity
+
+Grouping rules:
+  1. Same location prefix → same group
+  2. Shared affected_components → same group
+  3. Remaining ungrouped → individual groups (1 issue each)
+
+Output: GROUPS[] = { group_id, label, issues[], shared_keywords[] }
+
+Display group breakdown (skip if AUTO_YES).
+```
+
+---
+
+### Step 3: Generate tasks.csv
+
+Generate CSV with two waves:
+- **Wave 1**: One exploration row per issue (parallel within wave)
+- **Wave 2**: One synthesis row per group (parallel across groups, depends on its issues in wave 1)
+
+```csv
+id,title,description,iss_id,group_id,group_label,deps,context_from,wave,status,findings,analysis_json,error
+```
+
+**Wave 1 rows** — one per issue:
+
+```csv
+"1","Explore: ISS-xxx {title}","Root cause exploration for ISS-xxx: {description}. Location: {location}. Severity: {severity}. Fix hint: {fix_direction}. Search keywords: {keywords from title+description+components}. TASK: grep keywords → read top matches → trace call chain → identify root cause (file:line) → assess impact → list related files → rate confidence → suggest fix. EXPECTED: JSON { root_cause, impact, related_files[], confidence, suggested_approach }. CONSTRAINTS: Evidence-only, use file reads to verify.","ISS-xxx","G1","src/auth","","","1","","","",""
+```
+
+**Wave 2 rows** — one per group:
+
+```csv
+"N","Synthesize: {group_label}","Compile exploration findings for group [{group_label}]. For each issue: validate root cause evidence, identify cross-issue relationships, build analysis record. Output: JSON array [{ iss_id, root_cause, affected_files, impact_scope, fix_direction, confidence, cross_refs }]. Note shared root causes and dependency chains across issues in this group.","","G1","src/auth","1;2;3","1;2;3","2","","","",""
+```
+
+**Column definitions**:
+
+| Column | Phase | Description |
+|--------|-------|-------------|
+| `id` | Input | Unique task identifier |
+| `title` | Input | Short task title |
+| `description` | Input | Full exploration/synthesis instructions |
+| `iss_id` | Input | Issue ID (wave 1 only, empty for wave 2) |
+| `group_id` | Input | Group identifier |
+| `group_label` | Input | Group label for display |
+| `deps` | Input | Semicolon-separated dependency task IDs |
+| `context_from` | Input | Task IDs whose findings this task needs |
+| `wave` | Input | 1 = explore, 2 = synthesize |
+| `status` | Output | `pending` → `completed` / `failed` |
+| `findings` | Output | Key findings summary (max 500 chars) |
+| `analysis_json` | Output | Structured analysis JSON (wave 2 only) |
+| `error` | Output | Error message if failed |
+
+Write `tasks.csv` to session folder.
+
+---
+
+### Step 4: Wave 1 — Explore (parallel per issue)
+
+Filter `wave == 1 && status == pending`. Write `wave-1.csv`.
+
+```javascript
+spawn_agents_on_csv({
+  csv_path: `${sessionFolder}/wave-1.csv`,
+  id_column: "id",
+  instruction: `You are analyzing a specific issue for root cause. Read the 'description' column for full instructions. Use file reads and grep to gather evidence. Write findings as a concise summary with file:line references. Write analysis_json as a JSON object: { root_cause, impact, related_files[], confidence, suggested_approach }.`,
+  max_concurrency: maxConcurrency,
+  max_runtime_seconds: 3600,
+  output_csv_path: `${sessionFolder}/wave-1-results.csv`,
+  output_schema: { id, status: ["completed"|"failed"], findings, analysis_json, error }
+})
+```
+
+Merge results into master `tasks.csv`, delete `wave-1.csv`.
+
+**Per-issue agent responsibilities**:
+1. **Keyword Search** — grep issue keywords in source, find top 20 relevant paths
+2. **Context Read** — read top 5 matches with 10 lines surrounding context
+3. **Call Chain Trace** — trace 2-3 levels from issue location
+4. **Root Cause Identification** — pinpoint file:line with evidence
+5. **Impact Assessment** — scope of affected functionality
+
+---
+
+### Step 5: Wave 2 — Synthesize (parallel per group)
+
+Filter `wave == 2 && status == pending`. Build `prev_context` from wave 1 findings of issues in same group. Write `wave-2.csv` with `prev_context` column.
+
+```javascript
+spawn_agents_on_csv({
+  csv_path: `${sessionFolder}/wave-2.csv`,
+  id_column: "id",
+  instruction: `You are synthesizing root cause analysis for a group of related issues. Read prev_context for per-issue exploration findings. Validate evidence, identify cross-issue relationships and shared root causes. Output analysis_json as a JSON array: [{ iss_id, root_cause, affected_files, impact_scope, fix_direction, confidence, cross_refs }].`,
+  max_concurrency: maxConcurrency,
+  max_runtime_seconds: 3600,
+  output_csv_path: `${sessionFolder}/wave-2-results.csv`,
+  output_schema: { id, status: ["completed"|"failed"], findings, analysis_json, error }
+})
+```
+
+Merge results into master `tasks.csv`, delete `wave-2.csv`.
+
+**Synthesis agent responsibilities**:
+1. Parse per-issue findings from prev_context
+2. Validate root cause evidence (file:line exists, logic holds)
+3. Identify cross-issue relationships within group
+4. Build consolidated analysis array with cross_refs
+5. Flag shared root causes that affect multiple issues
+
+---
+
+### Step 6: Write Analysis to issues.jsonl
+
+```
+Parse analysis_json from wave 2 results.
+
+For each issue in the analysis array:
+  Build IssueAnalysis record:
+    {
+      root_cause,
+      affected_files,
+      impact_scope,
+      fix_direction,
+      confidence,
+      cross_refs,
+      analyzed_at: NOW_ISO,
+      tool: "spawn_agents_on_csv",
+      depth: DEPTH
+    }
+
+  Read-modify-write issues.jsonl (single pass):
+    Set issue.analysis = ANALYSIS, updated_at = NOW_ISO
+    Append issue.history: { action: "analyzed", at: NOW_ISO, by: "maestro-analyze --gaps" }
+    Status unchanged (non-destructive enrichment).
+
+Verify: re-read, confirm analysis field present for all updated issues.
+```
+
+---
+
+### Step 7: Output context.md
+
+```
+Aggregate results organized by group:
+
+  # Context: Issue Gaps Analysis
+
+  **Date**: {date}
+  **Issues analyzed**: {count}
+  **Groups**: {group_count}
+  **Session**: {sessionFolder}
+
+  ## Group: {group.label}
+
+  ### ISS-{id}: {title}
+  - **Root cause**: {root_cause}
+  - **Affected files**: {affected_files}
+  - **Impact scope**: {impact_scope}
+  - **Fix direction**: {fix_direction}
+  - **Confidence**: {confidence}
+  - **Cross-refs**: {related ISS-IDs}
+
+  (repeat per issue, per group)
+
+  ## Cross-Group Dependencies
+  {issues sharing root causes across groups}
+
+  ## Constraints
+
+  ### Locked
+  {constraints from root cause evidence}
+
+  ### Free
+  {implementation choices left to planner}
+
+Write context.md to session folder + copy to scratchDir.
+Register artifact in state.json.
+```
+
+---
+
+### Step 8: Display Summary and Next Steps
+
+```
+Display: group breakdown, per-issue root cause, confidence, cross-refs.
+
+Next steps:
+  - maestro-plan --gaps (plan fix tasks linked to analyzed issues)
+  - maestro-analyze --gaps {ISS-ID} (re-analyze specific issue)
+  - manage-issue list (review all issues)
+```
+
+---
+
+## Session Structure
+
+```
+.workflow/.csv-wave/{YYYYMMDD}-analyze-{slug}/
+├── tasks.csv            # master state
+├── results.csv          # final export
+├── wave-1.csv           # temporary (deleted after merge)
+├── wave-2.csv           # temporary (deleted after merge)
+├── discoveries.ndjson   # shared board (append-only)
+├── context.md           # decisions for plan --gaps
+```
+
+## Output
+
+- **Updated**: `.workflow/issues/issues.jsonl` — enriched with `analysis` field per issue
+- **Created**: `context.md` — grouped root causes for downstream `plan --gaps`
+- **Created**: `results.csv` — full task execution results
+
+## Quality Criteria
+
+- Issues classified into groups before CSV generation
+- Wave 1 agents run parallel (one per issue, bounded by maxConcurrency)
+- Wave 2 agents run parallel (one per group, after wave 1 deps met)
+- Cross-issue relationships captured via cross_refs
+- Single-pass JSONL update preserves integrity
+- context.md organized by group with cross-group section

package/workflows/issue-gaps-analyze.md

@@ -0,0 +1,214 @@
+# Workflow: Issue Gaps Analysis
+
+Root cause analysis for issues using CLI exploration and codebase context gathering.
+Supports single issue (ISS-ID) or batch (all open/registered) with classification and parallel analysis.
+Produces analysis records in issues.jsonl and context.md for downstream `plan --gaps`.
+
+**Invoked by**: `maestro-analyze --gaps [ISS-ID]`
+
+## Input
+
+- `ISS-ID` (optional): Specific issue to analyze. If omitted, analyze all open/registered issues.
+- `TOOL`: CLI tool for exploration (default: gemini)
+- `DEPTH`: `standard` or `deep` (default: standard)
+
+## Pipeline
+
+```
+Load Issues → Classify & Group → Parallel Analysis (per group) → Write issue.analysis → Output context.md
+```
+
+---
+
+### Step 1: Load Issues
+
+```
+If ISS-ID provided:
+  Load single issue from .workflow/issues/issues.jsonl
+  → fatal if file missing or ID not found (E_ISSUE_NOT_FOUND)
+  → skip Step 2 (classification), go directly to Step 3
+
+If no ISS-ID:
+  Load all issues where status == "open" || status == "registered"
+  → fatal if none found (E_NO_ISSUES)
+
+Validate: at least 1 issue loaded.
+```
+
+---
+
+### Step 2: Classify & Group (batch mode only)
+
+```
+Group loaded issues by overlap in affected area:
+
+Classification dimensions:
+  - location: file path prefix (e.g. src/auth/, src/api/)
+  - component: affected_components field overlap
+  - category: issue.category or severity level
+
+Grouping rules:
+  1. Same location prefix (first 2 path segments) → same group
+  2. Shared affected_components → same group
+  3. Remaining ungrouped → individual groups (1 issue each)
+
+Output: GROUPS[] where each group = { group_id, label, issues[], shared_context_keywords[] }
+
+Display group breakdown to user (skip if AUTO_YES).
+```
+
+---
+
+### Step 3: Gather Codebase Context (per group)
+
+```
+For each group:
+  Merge keywords from all issues in group: title, description, location, affected_components.
+  Deduplicate keywords.
+
+  Standard depth: grep keywords in source files → top 20 paths, read 10 lines around
+    top 5 matches.
+  Deep depth: standard grep + semantic Agent search (error handling, data flow, deps),
+    merge results.
+
+  Build GROUP_CONTEXT: related files, key snippets (max 50 lines), dependency chain.
+  Shared context benefits co-located issues — avoids redundant exploration.
+```
+
+---
+
+### Step 4: Run Analysis (per group, parallel across groups)
+
+```
+Launch analysis for each group in parallel using Agent tool:
+
+  Agent({
+    subagent_type: "general-purpose",
+    prompt: "Root cause analysis for issues in group [{group.label}]:
+      {for each issue in group}
+        ISS-{id}: {title} — {description}, severity: {severity}, location: {location}
+      {end}
+      CODEBASE CONTEXT: {GROUP_CONTEXT}
+      TASK: For EACH issue — identify root cause (file:line) → assess impact → list related files → rate confidence → suggest fix direction. Note cross-issue relationships within this group.
+      EXPECTED: JSON array [{ iss_id, root_cause, impact, related_files[], confidence, suggested_approach, cross_refs[] }]
+      CONSTRAINTS: Evidence-only, no speculation. Use Read/Grep to verify before concluding."
+  })
+
+Alternatively, attempt CLI delegate first per group:
+
+  maestro delegate "<same prompt>" --role analyze --mode analysis
+
+  If delegate fails (timeout, unavailable, parse error):
+    Fall back to Agent tool with same prompt.
+    Record fallback in analysis metadata: { tool: "agent-fallback", reason: "<error>" }
+
+Validate response per issue: all required fields present.
+Parse failure → save raw output to issue feedback for review.
+```
+
+---
+
+### Step 5: Build Analysis Record (per issue)
+
+```
+For each issue from Step 4 results:
+
+Construct IssueAnalysis:
+  {
+    root_cause,
+    affected_files: related_files,
+    impact_scope: impact,
+    fix_direction: suggested_approach,
+    confidence,
+    cross_refs: [ISS-IDs of related issues in same group],
+    analyzed_at: NOW_ISO,
+    tool: TOOL or "agent-fallback",
+    depth: DEPTH
+  }
+```
+
+---
+
+### Step 6: Update Issues in JSONL
+
+```
+Read-modify-write issues.jsonl (single pass for all analyzed issues):
+  For each issue:
+    Set issue.analysis = ANALYSIS, updated_at = NOW_ISO
+    Append issue.history: { action: "analyzed", at: NOW_ISO, by: "maestro-analyze --gaps" }
+    Status unchanged (analysis is metadata enrichment).
+Verify: re-read file, confirm analysis field present for all updated issues.
+```
+
+---
+
+### Step 7: Output context.md
+
+```
+Aggregate all analyzed issues into context.md, organized by group:
+
+  # Context: Issue Gaps Analysis
+
+  **Date**: {date}
+  **Issues analyzed**: {count}
+  **Groups**: {group_count}
+
+  ## Group: {group.label}
+
+  ### ISS-{id}: {title}
+  - **Root cause**: {root_cause}
+  - **Affected files**: {affected_files}
+  - **Impact scope**: {impact_scope}
+  - **Fix direction**: {fix_direction}
+  - **Confidence**: {confidence}
+  - **Cross-refs**: {related ISS-IDs}
+
+  (repeat per issue, per group)
+
+  ## Cross-Group Dependencies
+  {issues that span multiple groups or share root causes}
+
+  ## Constraints
+
+  ### Locked
+  {constraints derived from root cause evidence}
+
+  ### Free
+  {implementation choices left to planner}
+
+Write context.md to session output directory.
+```
+
+---
+
+### Step 8: Display Summary and Next Steps
+
+```
+Display: group breakdown, per-issue root cause, confidence, cross-refs.
+
+Next steps:
+  - maestro-plan --gaps (plan fix tasks linked to analyzed issues)
+  - maestro-analyze --gaps {ISS-ID} (re-analyze specific issue with deeper context)
+  - manage-issue list (review all issues)
+```
+
+---
+
+## Output
+
+- **Updated**: `.workflow/issues/issues.jsonl` -- issue records enriched with `analysis` field
+- **Created**: `context.md` -- aggregated root causes grouped for downstream `plan --gaps`
+- **Analysis fields**: root_cause, affected_files, impact_scope, fix_direction, confidence, cross_refs, analyzed_at, tool, depth
+
+## Quality Criteria
+
+- Issues classified by location/component overlap before analysis
+- Groups analyzed in parallel (Agent or delegate per group)
+- CLI delegate attempted first; Agent fallback on failure
+- Analysis grounded in actual codebase evidence (file:line references)
+- Cross-issue relationships captured within groups (cross_refs)
+- JSON result validated before writing to JSONL
+- Issue status unchanged (analysis is non-destructive enrichment)
+- Single-pass read-modify-write preserves JSONL integrity
+- context.md organized by group with cross-group dependencies
+- Next-step routing guides to plan --gaps