maestro-flow 0.3.9 → 0.3.11

package/workflows/issue-execute.md

@@ -1,5 +1,8 @@
 # Workflow: Issue Execution
 
+> **DEPRECATED**: This workflow was used by the deleted `manage-issue-execute` command.
+> Use `maestro-execute` instead, which handles wave-based execution with automatic issue status sync.
+
 Execute a planned solution for an issue via dual-mode agent dispatch (server or direct CLI).
 
 ## Input
@@ -182,8 +185,8 @@ If SERVER_UP == false (or server dispatch failed):
        }
    - Rewrite file
 
-3. Execute via CLI:
-   maestro cli -p "{EXEC_PROMPT}" --tool {CLI_TOOL} --mode write
+3. Execute via delegate:
+   maestro delegate "{EXEC_PROMPT}" --to {CLI_TOOL} --mode write
 
 4. Evaluate result:
    - If CLI exits successfully → EXEC_SUCCESS = true
@@ -274,7 +277,7 @@ If execution failed:
 ## Output
 
 - **Updated**: `.workflow/issues/issues.jsonl` -- issue status transitions (open -> in_progress -> resolved/open)
-- **Execution modes**: Server dispatch (POST /api/execution/dispatch) or Direct CLI (maestro cli --mode write)
+- **Execution modes**: Server dispatch (POST /api/execution/dispatch) or Direct delegate (maestro delegate --mode write)
 
 ## Quality Criteria
 

package/workflows/issue-plan.md

@@ -1,5 +1,8 @@
 # Workflow: Issue Planning
 
+> **DEPRECATED**: This workflow was used by the deleted `manage-issue-plan` command.
+> Use `maestro-plan --gaps` instead, which generates TASK files linked to issues via `task_refs`.
+
 Solution planning for a specific issue with codebase-aware step generation and prompt template construction.
 
 ## Input
@@ -91,7 +94,7 @@ Solution planning for a specific issue with codebase-aware step generation and p
 ```
 1. Build planning prompt:
 
-   maestro cli -p "PURPOSE: Generate a step-by-step solution plan for issue {ISS-ID}: {ISSUE.title}
+   maestro delegate "PURPOSE: Generate a step-by-step solution plan for issue {ISS-ID}: {ISSUE.title}
    Produce an actionable, ordered list of implementation steps.
 
    ISSUE DETAILS:
@@ -116,7 +119,7 @@ Solution planning for a specific issue with codebase-aware step generation and p
      context: string (approach summary),
      promptTemplate: string (execution prompt for the agent)
    CONSTRAINTS: Steps must be concrete and file-specific, not vague
-   " --tool {TOOL} --mode analysis
+   " --to {TOOL} --mode analysis
 
 2. Parse CLI output:
    - Extract JSON object from response