maestro-flow 0.3.3 → 0.3.5

package/.codex/skills/manage-codebase-rebuild/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-codebase-rebuild
+name: manage-codebase-rebuild
 description: Full codebase documentation rebuild via CSV wave pipeline. Spawns 5 parallel doc generator agents to scan project and produce complete .workflow/codebase/ documentation set. Replaces manage-codebase-rebuild command.
 argument-hint: "[-y|--yes] [-c|--concurrency 5] [--continue] \"[--force] [--skip-commit]\""
 allowed-tools: spawn_agents_on_csv, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
@@ -14,10 +14,10 @@ When `--yes` or `-y`: Auto-confirm rebuild (implies --force), skip all prompts.
 ## Usage
 
 ```bash
-$maestro-codebase-rebuild ""
-$maestro-codebase-rebuild -y "--force"
-$maestro-codebase-rebuild -c 5 "--force --skip-commit"
-$maestro-codebase-rebuild --continue "rebuild-full-20260318"
+$manage-codebase-rebuild ""
+$manage-codebase-rebuild -y "--force"
+$manage-codebase-rebuild -c 5 "--force --skip-commit"
+$manage-codebase-rebuild --continue "rebuild-full-20260318"
 ```
 
 **Flags**:

package/.codex/skills/manage-codebase-refresh/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-codebase-refresh
+name: manage-codebase-refresh
 description: Incremental refresh of codebase docs based on recent git changes
 argument-hint: "[--since <date>] [--deep]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
@@ -10,10 +10,10 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ## Usage
 
 ```bash
-$maestro-codebase-refresh
-$maestro-codebase-refresh "--since 2026-03-15"
-$maestro-codebase-refresh "--deep"
-$maestro-codebase-refresh "--since 3d --deep"
+$manage-codebase-refresh
+$manage-codebase-refresh "--since 2026-03-15"
+$manage-codebase-refresh "--deep"
+$manage-codebase-refresh "--since 3d --deep"
 ```
 
 **Flags**:

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

@@ -1,5 +1,5 @@
 ---
-name: maestro-issue
+name: manage-issue
 description: Issue CRUD -- create, list, status, update, close, and link issues to tasks
 argument-hint: "<create|list|status|update|close|link> [options]"
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
@@ -10,12 +10,12 @@ allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
 ## Usage
 
 ```bash
-$maestro-issue "create --title 'Auth token expiry bug' --severity high --source manual"
-$maestro-issue "list --status open --severity high"
-$maestro-issue "status ISS-20260318-001"
-$maestro-issue "update ISS-20260318-001 --priority critical --tags auth,security"
-$maestro-issue "close ISS-20260318-001 --resolution fixed"
-$maestro-issue "link ISS-20260318-001 --task TASK-003"
+$manage-issue "create --title 'Auth token expiry bug' --severity high --source manual"
+$manage-issue "list --status open --severity high"
+$manage-issue "status ISS-20260318-001"
+$manage-issue "update ISS-20260318-001 --priority critical --tags auth,security"
+$manage-issue "close ISS-20260318-001 --resolution fixed"
+$manage-issue "link ISS-20260318-001 --task TASK-003"
 ```
 
 ---

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

@@ -1,5 +1,5 @@
 ---
-name: maestro-issue-analyze
+name: manage-issue-analyze
 description: Root cause analysis for a specific issue via CLI exploration. Gathers codebase context (grep or semantic deep search), runs maestro delegate gemini analysis, and attaches a structured analysis record to the issue in issues.jsonl.
 argument-hint: "<ISS-ID> [--tool gemini|qwen] [--depth standard|deep]"
 allowed-tools: Read, Write, Bash, Glob, Grep
@@ -10,9 +10,9 @@ allowed-tools: Read, Write, Bash, Glob, Grep
 ## Usage
 
 ```bash
-$maestro-issue-analyze "ISS-20260401-001"
-$maestro-issue-analyze "ISS-20260401-001 --depth deep"
-$maestro-issue-analyze "ISS-20260401-001 --tool qwen --depth standard"
+$manage-issue-analyze "ISS-20260401-001"
+$manage-issue-analyze "ISS-20260401-001 --depth deep"
+$manage-issue-analyze "ISS-20260401-001 --tool qwen --depth standard"
 ```
 
 **Flags**:
@@ -178,7 +178,7 @@ Impact:      <impact_scope>
 Confidence:  <confidence>
 Affected:    <N> files
 
-Next: $maestro-issue-plan "<ISS-ID>"
+Next: $manage-issue-plan "<ISS-ID>"
 ```
 
 ---
@@ -189,7 +189,7 @@ Next: $maestro-issue-plan "<ISS-ID>"
 |------|----------|-----------|----------|
 | E001 | error | No ISS-ID provided | Display usage hint with format example |
 | E002 | error | ISS-ID format invalid | Show correct format `ISS-XXXXXXXX-NNN` |
-| E003 | error | ISS-ID not found in issues.jsonl | Suggest `$maestro-issue "list"` |
+| E003 | error | ISS-ID not found in issues.jsonl | Suggest `$manage-issue "list"` |
 | E004 | error | CLI analysis returned no parseable result | Retry with different `--tool`; report partial |
 | W001 | warning | Issue status is not open/registered | Warn, allow analysis to continue |
 
@@ -204,4 +204,4 @@ Next: $maestro-issue-plan "<ISS-ID>"
 5. **Append-only history**: Append to `issue_history`, never overwrite existing entries
 - *Note*: `spawn_agent` / `wait_agent` / `close_agent` are Codex v4 built-in orchestration functions — they do not need to be listed in `allowed-tools`
 6. **Preserve existing fields**: Patch only `analysis` + `issue_history` — all other fields unchanged
-7. **Next-step routing**: Always display `$maestro-issue-plan "<ISS-ID>"` at the end
+7. **Next-step routing**: Always display `$manage-issue-plan "<ISS-ID>"` at the end