maestro-flow 0.3.28 → 0.3.30

package/.codex/skills/maestro-init/SKILL.md

@@ -1,26 +1,26 @@
 ---
 name: maestro-init
 description: Initialize project with auto state detection — creates .workflow/ directory, project.md, state.json, config.json, and specs/
-argument-hint: "[--auto] [--from-brainstorm SESSION-ID]"
+argument-hint: "[-y] [--from-brainstorm SESSION-ID]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
 
 <purpose>
 Sequential project setup skill. Detects project state (empty/code/existing), gathers project information through deep questioning or document extraction, then creates the `.workflow/` directory structure. No parallel agents — single sequential flow.
 
-When `--auto`: After config questions, run research without further interaction. Expects idea document via @ reference.
+When `-y`: After config questions, run research without further interaction. Expects idea document via @ reference.
 </purpose>
 
 <context>
 
 ```bash
 $maestro-init ""
-$maestro-init "--auto"
+$maestro-init "-y"
 $maestro-init "--from-brainstorm 20260318-brainstorm-auth"
 ```
 
 **Flags**:
-- `--auto`: Skip interactive questioning; extract from provided document
+- `-y`: Skip interactive questioning; extract from provided document
 - `--from-brainstorm SESSION-ID`: Import vision/goals/constraints from brainstorm guidance-specification.md
 
 **Output**: `.workflow/` directory with project.md, state.json, config.json, specs/
@@ -29,7 +29,7 @@ $maestro-init "--from-brainstorm 20260318-brainstorm-auth"
 
 <invariants>
 1. **Never create roadmap** — init only creates .workflow/ structure; roadmap is a separate step
-2. **Deep questioning over speed** — follow threads, ask clarifying questions (unless --auto)
+2. **Deep questioning over speed** — follow threads, ask clarifying questions (unless -y)
 3. **Detect, don't assume** — scan for existing files, package managers, frameworks before asking
 4. **Templates are source of truth** — always read templates before writing files
 5. **Idempotent check** — if .workflow/ exists, refuse to overwrite (E002)
@@ -40,7 +40,7 @@ $maestro-init "--from-brainstorm 20260318-brainstorm-auth"
 ### Step 1: Parse Arguments
 
 Extract flags from arguments:
-- `--auto` flag presence
+- `-y` flag presence
 - `--from-brainstorm SESSION-ID` value
 - Remaining text as project description
 
@@ -60,7 +60,7 @@ Classify as:
 - Extract: vision, goals, constraints, terminology, tech decisions
 - Skip interactive questioning
 
-**If `--auto`**:
+**If `-y`**:
 - Extract project info from provided document/@ reference
 - Minimal interactive questions (confirm core value only)
 
@@ -94,7 +94,7 @@ Initialize from template with `current_milestone: null`, `status: "initialized"`
 
 ### Step 8: Write config.json
 
-Configuration questions (or defaults for --auto): granularity (fine/medium/coarse), workflow agents (enable/disable), gate preferences. Write to `.workflow/config.json`.
+Configuration questions (or defaults for -y): granularity (fine/medium/coarse), workflow agents (enable/disable), gate preferences. Write to `.workflow/config.json`.
 
 ### Step 9: Initialize specs/
 
@@ -110,7 +110,7 @@ Display created files and next steps: `$maestro-roadmap --mode full` (full spec)
 
 | Code | Severity | Description | Recovery |
 |------|----------|-------------|----------|
-| E001 | error | No arguments when --auto requires document | Ask user for document reference |
+| E001 | error | No arguments when -y requires document | Ask user for document reference |
 | E002 | error | .workflow/ already exists | Show status, suggest manage-status |
 | E003 | error | Brainstorm session not found | List available sessions |
 | W001 | warning | Could not detect tech stack | Continue with manual input |

package/.codex/skills/maestro-link-coordinate/SKILL.md

@@ -150,10 +150,10 @@ Set `state.status` to completed/failed based on `node.status`. Record final hist
 
 | Skill | Flag |
 |-------|------|
-| `maestro-analyze`, `maestro-brainstorm`, `maestro-ui-design`, `maestro-roadmap` | `-y` |
-| `maestro-plan` | `--auto` |
-| `quality-test` | `--auto-fix` |
-| `quality-retrospective` | `--auto-yes` |
+| `maestro-init`, `maestro-analyze`, `maestro-brainstorm`, `maestro-ui-design`, `maestro-roadmap` | `-y` |
+| `maestro-plan`, `maestro-execute`, `maestro-milestone-complete` | `-y` |
+| `quality-business-test`, `quality-retrospective` | `-y` |
+| `quality-test` | `-y --auto-fix` |
 
 **buildSkillCall(node, ctx, autoMode)**: Substitute `{phase}`, `{description}`, `{issue_id}`, `{milestone_num}` from context into `node.args`. If autoMode, append auto flag from `node.auto_flag` or AUTO_FLAG_MAP. Return `$${node.cmd} ${resolvedArgs}`.
 

package/.codex/skills/maestro-milestone-complete/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: maestro-milestone-complete
 description: Archive completed milestone scratch artifacts to milestones/ dir, move artifact entries to milestone_history, extract learnings, advance state.
-argument-hint: "[milestone] [--force]"
+argument-hint: "[milestone] [--force] [-y]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ---
 
@@ -49,7 +49,8 @@ Read `.summaries/` and `reflection-log.md` from execute artifacts. Extract patte
 2. **Convention drift**: Compare summaries against `coding-conventions.md` and `architecture-constraints.md` -- ask if conventions need updating
 3. **Wiki island check**: Auto-trigger `wiki-connect --fix` to link new knowledge
 
-If user confirms promotion, append `<spec-entry>` to target category file preserving original date and source.
+If `-y`: auto-accept all promotions without asking.
+If not `-y`: ask user for confirmation. If user confirms, append `<spec-entry>` to target category file preserving original date and source.
 
 ### Step 4: Archive Artifact Entries
 

package/.codex/skills/maestro-plan/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: maestro-plan
 description: Exploration-driven planning via CSV wave pipeline. Wave 1 runs parallel codebase exploration agents, Wave 2 synthesizes explorations into plan.json + TASK-*.json. Replaces maestro-plan command.
-argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"<phase> [--auto] [--dir <path>] [--gaps] [--spec SPEC-xxx] [--collab]\""
+argument-hint: "[-y|--yes] [-c|--concurrency N] [--continue] \"<phase> [--dir <path>] [--gaps] [--spec SPEC-xxx] [--collab]\""
 allowed-tools: spawn_agents_on_csv, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
 
@@ -51,7 +51,7 @@ Wave-based planning using `spawn_agents_on_csv`. Wave 1 explores codebase contex
 <context>
 ```bash
 $maestro-plan "3"
-$maestro-plan -y "3 --auto"
+$maestro-plan -y "3"
 $maestro-plan -c 4 "3 --spec SPEC-001"
 $maestro-plan "3 --gaps"
 $maestro-plan "3 --dir .workflow/scratch/quick-nav-fix"