maestro-flow 0.3.4 → 0.3.6

package/.codex/skills/manage-issue-execute/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-issue-execute
+name: manage-issue-execute
 description: Execute a planned solution for an issue via dual-mode dispatch. Auto-detects server UP (POST to /api/execution/dispatch) or DOWN (direct maestro delegate). Updates issue status on completion with next-step routing to close, debug, or verify.
 argument-hint: "<ISS-ID> [--executor claude-code|codex|gemini] [--dry-run]"
 allowed-tools: Read, Write, Bash, Glob, Grep
@@ -10,10 +10,10 @@ allowed-tools: Read, Write, Bash, Glob, Grep
 ## Usage
 
 ```bash
-$maestro-issue-execute "ISS-20260401-001"
-$maestro-issue-execute "ISS-20260401-001 --dry-run"
-$maestro-issue-execute "ISS-20260401-001 --executor codex"
-$maestro-issue-execute "ISS-20260401-001 --executor gemini"
+$manage-issue-execute "ISS-20260401-001"
+$manage-issue-execute "ISS-20260401-001 --dry-run"
+$manage-issue-execute "ISS-20260401-001 --executor codex"
+$manage-issue-execute "ISS-20260401-001 --executor gemini"
 ```
 
 **Flags**:
@@ -172,9 +172,9 @@ Mode:      <server|cli>
 Status:    resolved
 
 Next steps:
-  Close:   $maestro-issue "close <ISS-ID> --resolution fixed"
+  Close:   $manage-issue "close <ISS-ID> --resolution fixed"
   Verify:  $maestro-verify "<phase>"
-  Debug:   $maestro-debug "<failure description>" (if issues found)
+  Debug:   $quality-debug "<failure description>" (if issues found)
 ```
 
 ---
@@ -184,8 +184,8 @@ Next steps:
 | Code | Severity | Condition | Recovery |
 |------|----------|-----------|----------|
 | E001 | error | No ISS-ID provided | Display usage hint |
-| E002 | error | No solution record on issue | Run `$maestro-issue-plan "<ISS-ID>"` first |
-| E003 | error | ISS-ID not found in issues.jsonl | Suggest `$maestro-issue "list"` |
+| E002 | error | No solution record on issue | Run `$manage-issue-plan "<ISS-ID>"` first |
+| E003 | error | ISS-ID not found in issues.jsonl | Suggest `$manage-issue "list"` |
 | E004 | error | Server dispatch or CLI execution failed | Log error, revert status to `open`, display failure details |
 
 ---

package/.codex/skills/manage-issue-plan/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-issue-plan
+name: manage-issue-plan
 description: Solution planning for a specific issue. Auto-detects analysis context, runs maestro delegate planning, and attaches a structured solution record with ordered steps and verification criteria to the issue in issues.jsonl.
 argument-hint: "<ISS-ID> [--tool gemini|qwen] [--from-analysis]"
 allowed-tools: Read, Write, Bash, Glob, Grep
@@ -10,9 +10,9 @@ allowed-tools: Read, Write, Bash, Glob, Grep
 ## Usage
 
 ```bash
-$maestro-issue-plan "ISS-20260401-001"
-$maestro-issue-plan "ISS-20260401-001 --from-analysis"
-$maestro-issue-plan "ISS-20260401-001 --tool qwen"
+$manage-issue-plan "ISS-20260401-001"
+$manage-issue-plan "ISS-20260401-001 --from-analysis"
+$manage-issue-plan "ISS-20260401-001 --tool qwen"
 ```
 
 **Flags**:
@@ -160,7 +160,7 @@ Steps:
 Verification:
   - <verification 1>
 
-Next: $maestro-issue-execute "<ISS-ID>"
+Next: $manage-issue-execute "<ISS-ID>"
 ```
 
 ---
@@ -170,9 +170,9 @@ Next: $maestro-issue-execute "<ISS-ID>"
 | Code | Severity | Condition | Recovery |
 |------|----------|-----------|----------|
 | E001 | error | No ISS-ID provided | Display usage hint |
-| E002 | error | ISS-ID not found in issues.jsonl | Suggest `$maestro-issue "list"` |
+| E002 | error | ISS-ID not found in issues.jsonl | Suggest `$manage-issue "list"` |
 | E003 | error | CLI planning returned no parseable result | Retry with different `--tool` |
-| W001 | warning | `--from-analysis` but no analysis record exists | Proceed without context; suggest `$maestro-issue-analyze` |
+| W001 | warning | `--from-analysis` but no analysis record exists | Proceed without context; suggest `$manage-issue-analyze` |
 
 ---
 
@@ -183,4 +183,4 @@ Next: $maestro-issue-execute "<ISS-ID>"
 3. **Concrete steps only**: Each step must have a file reference — no "investigate further" placeholders
 4. **Preserve existing fields**: Patch only `solution` + `issue_history` — all other issue fields unchanged
 5. **Append-only history**: Append to `issue_history`, never overwrite existing entries
-6. **Next-step routing**: Always display `$maestro-issue-execute "<ISS-ID>"` at the end
+6. **Next-step routing**: Always display `$manage-issue-execute "<ISS-ID>"` at the end

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

@@ -1,5 +1,5 @@
 ---
-name: maestro-learn
+name: manage-learn
 description: Capture atomic learning insights into .workflow/learning/lessons.jsonl. Lightweight CRUD over the shared learning store — supports capture, list, search, and show modes. No LLM or CLI calls; all operations are pure file reads and writes.
 argument-hint: "[\"<insight text>\"|list|search <query>|show <INS-id>] [--category pattern|antipattern|decision|tool|gotcha|technique] [--tag t1,t2] [--phase N] [--confidence high|medium|low]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
@@ -10,11 +10,11 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ## Usage
 
 ```bash
-$maestro-learn "Always read state.json before planning to detect current phase"
-$maestro-learn "list --limit 10 --category antipattern"
-$maestro-learn "search context propagation"
-$maestro-learn "show INS-a3f7b2c1"
-$maestro-learn "\"Zod v4 breaks z.object().strict() API\" --category gotcha --tag zod,typescript"
+$manage-learn "Always read state.json before planning to detect current phase"
+$manage-learn "list --limit 10 --category antipattern"
+$manage-learn "search context propagation"
+$manage-learn "show INS-a3f7b2c1"
+$manage-learn "\"Zod v4 breaks z.object().strict() API\" --category gotcha --tag zod,typescript"
 ```
 
 **Flags** (capture mode):
@@ -157,7 +157,7 @@ Phase:      3 (phase-03-api-layer)
 Confidence: medium
 Tags:       manual, zod, typescript
 
-Next: $maestro-learn "list"  or  $maestro-learn "search zod"
+Next: $manage-learn "list"  or  $manage-learn "search zod"
 ```
 
 ---

package/.codex/skills/manage-memory/SKILL.md

@@ -1,72 +1,72 @@
----
-name: maestro-memory
-description: Manage memory entries across workflow and system stores (list, search, view, edit, delete, prune)
-argument-hint: "[list|search|view|edit|delete|prune] [query|id|file] [--store workflow|system|all] [--tag tag] [--type compact|tip]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-# Memory Management
-
-## Usage
-
-```bash
-$maestro-memory
-$maestro-memory "list --store workflow"
-$maestro-memory "search authentication"
-$maestro-memory "view MEM-20260318-001"
-$maestro-memory "edit MEMORY.md"
-$maestro-memory "delete TIP-20260318-001 --confirm"
-$maestro-memory "prune --before 2026-01-01 --type tip --dry-run"
-```
-
----
-
-## Implementation
-
-### Step 1: Resolve Store Paths
-
-- **Workflow store**: `.workflow/memory/` (entries: `MEM-*.md`, `TIP-*.md`, index: `memory-index.json`)
-- **System store**: `~/.claude/projects/{project}/memory/` (files: `MEMORY.md` + topic `.md` files)
-
-Derive system path from project root (replace path separators with `--`, prefix drive letter).
-
-### Step 2: Parse Subcommand
-
-Default to `list` if no arguments. Parse first token as subcommand.
-
-### Step 3: Execute Subcommand
-
-**list**: Show entries from both stores (or filtered by `--store`, `--tag`, `--type`).
-- Workflow: read `memory-index.json`, display ID, type, date, tags, title
-- System: list `.md` files in system memory directory
-
-**search `<query>`**: Full-text grep across both stores. Rank by match count.
-
-**view `<id|file>`**: Auto-detect store from format (`MEM-*/TIP-*` = workflow, else system). Display full content.
-
-**edit `<file>`**: Edit a system memory file. Read current content, apply changes. Warn if MEMORY.md exceeds 200 lines (W003).
-
-**delete `<id|file>`**: Require confirmation (or `--confirm` flag). MEMORY.md cannot be deleted (E004). Remove entry file and update `memory-index.json`.
-
-**prune**: Requires at least one filter (`--tag`, `--type`, `--before`, `--after`). Workflow store only. `--dry-run` previews without deleting.
-
-### Step 4: Integrity Check
-
-After write operations, verify:
-- No orphaned files without index entries (W001)
-- No dangling index references to missing files (W001)
-- System MEMORY.md references valid topic files (W002)
-
----
-
-## Error Handling
-
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | error | No memory stores found -- run `Skill({ skill: "memory-capture" })` or create MEMORY.md |
-| E002 | error | Entry ID or filename not found |
-| E003 | error | Prune requires at least one filter flag |
-| E004 | error | Cannot delete MEMORY.md -- use `edit` subcommand instead |
-| W001 | warning | Index has orphaned files or dangling references |
-| W002 | warning | MEMORY.md references non-existent topic file |
-| W003 | warning | MEMORY.md exceeds 200 lines -- content truncated at load |
+---
+name: manage-memory
+description: Manage memory entries across workflow and system stores (list, search, view, edit, delete, prune)
+argument-hint: "[list|search|view|edit|delete|prune] [query|id|file] [--store workflow|system|all] [--tag tag] [--type compact|tip]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+---
+
+# Memory Management
+
+## Usage
+
+```bash
+$manage-memory
+$manage-memory "list --store workflow"
+$manage-memory "search authentication"
+$manage-memory "view MEM-20260318-001"
+$manage-memory "edit MEMORY.md"
+$manage-memory "delete TIP-20260318-001 --confirm"
+$manage-memory "prune --before 2026-01-01 --type tip --dry-run"
+```
+
+---
+
+## Implementation
+
+### Step 1: Resolve Store Paths
+
+- **Workflow store**: `.workflow/memory/` (entries: `MEM-*.md`, `TIP-*.md`, index: `memory-index.json`)
+- **System store**: `~/.claude/projects/{project}/memory/` (files: `MEMORY.md` + topic `.md` files)
+
+Derive system path from project root (replace path separators with `--`, prefix drive letter).
+
+### Step 2: Parse Subcommand
+
+Default to `list` if no arguments. Parse first token as subcommand.
+
+### Step 3: Execute Subcommand
+
+**list**: Show entries from both stores (or filtered by `--store`, `--tag`, `--type`).
+- Workflow: read `memory-index.json`, display ID, type, date, tags, title
+- System: list `.md` files in system memory directory
+
+**search `<query>`**: Full-text grep across both stores. Rank by match count.
+
+**view `<id|file>`**: Auto-detect store from format (`MEM-*/TIP-*` = workflow, else system). Display full content.
+
+**edit `<file>`**: Edit a system memory file. Read current content, apply changes. Warn if MEMORY.md exceeds 200 lines (W003).
+
+**delete `<id|file>`**: Require confirmation (or `--confirm` flag). MEMORY.md cannot be deleted (E004). Remove entry file and update `memory-index.json`.
+
+**prune**: Requires at least one filter (`--tag`, `--type`, `--before`, `--after`). Workflow store only. `--dry-run` previews without deleting.
+
+### Step 4: Integrity Check
+
+After write operations, verify:
+- No orphaned files without index entries (W001)
+- No dangling index references to missing files (W001)
+- System MEMORY.md references valid topic files (W002)
+
+---
+
+## Error Handling
+
+| Code | Severity | Description |
+|------|----------|-------------|
+| E001 | error | No memory stores found -- run `Skill({ skill: "memory-capture" })` or create MEMORY.md |
+| E002 | error | Entry ID or filename not found |
+| E003 | error | Prune requires at least one filter flag |
+| E004 | error | Cannot delete MEMORY.md -- use `edit` subcommand instead |
+| W001 | warning | Index has orphaned files or dangling references |
+| W002 | warning | MEMORY.md references non-existent topic file |
+| W003 | warning | MEMORY.md exceeds 200 lines -- content truncated at load |

package/.codex/skills/manage-memory-capture/SKILL.md

@@ -1,86 +1,86 @@
----
-name: maestro-memory-capture
-description: Capture session memory (compact or tip) into .workflow/memory/ with JSON index
-argument-hint: "[compact|tip] [description] [--tag tag1,tag2]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-# Memory Capture
-
-## Usage
-
-```bash
-$maestro-memory-capture
-$maestro-memory-capture "compact"
-$maestro-memory-capture "tip Always check state.json before phase operations --tag workflow,state"
-$maestro-memory-capture "compact Full auth implementation session"
-```
-
-**Modes**: `compact` (full session compression) or `tip` (quick note with tags).
-No arguments: auto-detect or ask user.
-
----
-
-## Implementation
-
-### Step 1: Validate
-
-```bash
-test -d .workflow || exit 1  # E001: not initialized
-```
-
-Create `.workflow/memory/` if it does not exist.
-
-### Step 2: Detect Mode
-
-Parse first token as mode (`compact` or `tip`).
-If absent or ambiguous, ask user via AskUserQuestion.
-
-### Step 3: Capture Content
-
-**Compact mode**:
-1. Analyze current conversation for: objective, key decisions, modified files, current plan state, pending work
-2. Generate entry ID: `MEM-{YYYYMMDD}-{NNN}`
-3. Write `.workflow/memory/MEM-{id}.md` with sections:
-   - Objective, Key Decisions, Files Modified (absolute paths), Execution Plan (verbatim), Pending Work, Context Notes
-
-**Tip mode**:
-1. Extract content (everything after `tip`) and parse `--tag` flag
-2. Generate entry ID: `TIP-{YYYYMMDD}-{NNN}`
-3. Write `.workflow/memory/TIP-{id}.md` with: content, tags, timestamp, context
-
-### Step 4: Update Index
-
-Read or create `.workflow/memory/memory-index.json`.
-Append new entry metadata:
-
-```json
-{
-  "id": "{entry_id}",
-  "type": "compact|tip",
-  "date": "{ISO}",
-  "title": "{short title}",
-  "tags": ["tag1", "tag2"],
-  "file": "{filename}"
-}
-```
-
-### Step 5: Confirm
-
-```
-=== MEMORY CAPTURED ===
-ID: {entry_id}
-Type: {compact|tip}
-File: .workflow/memory/{filename}
-```
-
----
-
-## Error Handling
-
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | error | `.workflow/` not initialized -- run `Skill({ skill: "maestro-init" })` first |
-| E002 | error | Empty note content in tip mode |
-| W001 | warning | No active workflow session -- compact captures conversation only |
-| W002 | warning | No explicit plan found -- using inferred plan |
+---
+name: manage-memory-capture
+description: Capture session memory (compact or tip) into .workflow/memory/ with JSON index
+argument-hint: "[compact|tip] [description] [--tag tag1,tag2]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+---
+
+# Memory Capture
+
+## Usage
+
+```bash
+$manage-memory-capture
+$manage-memory-capture "compact"
+$manage-memory-capture "tip Always check state.json before phase operations --tag workflow,state"
+$manage-memory-capture "compact Full auth implementation session"
+```
+
+**Modes**: `compact` (full session compression) or `tip` (quick note with tags).
+No arguments: auto-detect or ask user.
+
+---
+
+## Implementation
+
+### Step 1: Validate
+
+```bash
+test -d .workflow || exit 1  # E001: not initialized
+```
+
+Create `.workflow/memory/` if it does not exist.
+
+### Step 2: Detect Mode
+
+Parse first token as mode (`compact` or `tip`).
+If absent or ambiguous, ask user via AskUserQuestion.
+
+### Step 3: Capture Content
+
+**Compact mode**:
+1. Analyze current conversation for: objective, key decisions, modified files, current plan state, pending work
+2. Generate entry ID: `MEM-{YYYYMMDD}-{NNN}`
+3. Write `.workflow/memory/MEM-{id}.md` with sections:
+   - Objective, Key Decisions, Files Modified (absolute paths), Execution Plan (verbatim), Pending Work, Context Notes
+
+**Tip mode**:
+1. Extract content (everything after `tip`) and parse `--tag` flag
+2. Generate entry ID: `TIP-{YYYYMMDD}-{NNN}`
+3. Write `.workflow/memory/TIP-{id}.md` with: content, tags, timestamp, context
+
+### Step 4: Update Index
+
+Read or create `.workflow/memory/memory-index.json`.
+Append new entry metadata:
+
+```json
+{
+  "id": "{entry_id}",
+  "type": "compact|tip",
+  "date": "{ISO}",
+  "title": "{short title}",
+  "tags": ["tag1", "tag2"],
+  "file": "{filename}"
+}
+```
+
+### Step 5: Confirm
+
+```
+=== MEMORY CAPTURED ===
+ID: {entry_id}
+Type: {compact|tip}
+File: .workflow/memory/{filename}
+```
+
+---
+
+## Error Handling
+
+| Code | Severity | Description |
+|------|----------|-------------|
+| E001 | error | `.workflow/` not initialized -- run `Skill({ skill: "maestro-init" })` first |
+| E002 | error | Empty note content in tip mode |
+| W001 | warning | No active workflow session -- compact captures conversation only |
+| W002 | warning | No explicit plan found -- using inferred plan |

package/.codex/skills/manage-status/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-status
+name: manage-status
 description: Display project dashboard with phase progress, active tasks, and next steps
 argument-hint: ""
 allowed-tools: Read, Bash, Glob, Grep
@@ -10,7 +10,7 @@ allowed-tools: Read, Bash, Glob, Grep
 ## Usage
 
 ```bash
-$maestro-status
+$manage-status
 ```
 
 No arguments required. Reads `.workflow/` state files and renders a formatted project overview.

package/.codex/skills/quality-business-test/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-business-test
+name: quality-business-test
 description: PRD-forward business testing with requirement traceability, multi-layer execution (L1 Interface → L2 Business Rule → L3 Scenario), fixture generation, and feedback loop.
 argument-hint: "<phase> [--spec SPEC-xxx] [--layer L1|L2|L3] [--gen-code] [--dry-run] [--re-run] [--auto]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion
@@ -14,13 +14,13 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion
 ## Usage
 
 ```bash
-$maestro-business-test "3"                          # test phase 3 against PRD
-$maestro-business-test "3 --layer L1"               # L1 interface tests only
-$maestro-business-test "3 --gen-code"               # generate framework-specific test classes
-$maestro-business-test "3 --dry-run"                # extract scenarios only, don't execute
-$maestro-business-test "3 --re-run"                 # re-run only previously failed scenarios
-$maestro-business-test "3 --spec SPEC-auth-2026-04" # explicit spec reference
-$maestro-business-test "3 --auto"                   # skip plan confirmation
+$quality-business-test "3"                          # test phase 3 against PRD
+$quality-business-test "3 --layer L1"               # L1 interface tests only
+$quality-business-test "3 --gen-code"               # generate framework-specific test classes
+$quality-business-test "3 --dry-run"                # extract scenarios only, don't execute
+$quality-business-test "3 --re-run"                 # re-run only previously failed scenarios
+$quality-business-test "3 --spec SPEC-auth-2026-04" # explicit spec reference
+$quality-business-test "3 --auto"                   # skip plan confirmation
 ```
 
 **Flags**:

package/.codex/skills/quality-debug/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-debug
+name: quality-debug
 description: Hypothesis-driven debugging via CSV wave pipeline. Wave 1 generates parallel hypotheses, Wave 2 attempts parallel fixes on confirmed hypotheses. Replaces quality-debug command.
 argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"[bug description] [--from-uat <phase>] [--parallel]\""
 allowed-tools: spawn_agents_on_csv, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
@@ -14,10 +14,10 @@ When `--yes` or `-y`: Auto-confirm hypothesis selection, skip interactive sympto
 ## Usage
 
 ```bash
-$maestro-debug "Login button throws 500 error on click"
-$maestro-debug -y "JWT token not refreshed --from-uat 3"
-$maestro-debug -c 4 "Navigation crash --from-uat 3 --parallel"
-$maestro-debug --continue "debug-jwt-expiry-20260318"
+$quality-debug "Login button throws 500 error on click"
+$quality-debug -y "JWT token not refreshed --from-uat 3"
+$quality-debug -c 4 "Navigation crash --from-uat 3 --parallel"
+$quality-debug --continue "debug-jwt-expiry-20260318"
 ```
 
 **Flags**: