maestro-flow 0.3.15 → 0.3.17

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

@@ -163,31 +163,22 @@ Each wave generates `wave-{N}.csv` with extra `prev_context` column.
 
 ### Session Initialization
 
-```javascript
-const getUtc8ISOString = () => new Date(Date.now() + 8 * 60 * 60 * 1000).toISOString()
-
-// Parse flags
-const AUTO_YES = $ARGUMENTS.includes('--yes') || $ARGUMENTS.includes('-y')
-const continueMode = $ARGUMENTS.includes('--continue')
-const concurrencyMatch = $ARGUMENTS.match(/(?:--concurrency|-c)\s+(\d+)/)
-const maxConcurrency = concurrencyMatch ? parseInt(concurrencyMatch[1]) : 6
-
-// Parse brainstorm-specific flags
-const countMatch = $ARGUMENTS.match(/--count\s+(\d+)/)
-const roleCount = countMatch ? Math.min(parseInt(countMatch[1]), 9) : 3
-const skipQuestions = $ARGUMENTS.includes('--skip-questions')
-
-// Clean topic text
-const topicArg = $ARGUMENTS
-  .replace(/--yes|-y|--continue|--concurrency\s+\d+|-c\s+\d+|--count\s+\d+|--skip-questions/g, '')
-  .trim()
-
-const slug = topicArg.toLowerCase().replace(/[^a-z0-9]+/g, '-').substring(0, 40)
-const dateStr = getUtc8ISOString().substring(0, 10).replace(/-/g, '')
-const sessionId = `${dateStr}-brainstorm-${slug}`
-const sessionFolder = `.workflow/.csv-wave/${sessionId}`
-
-Bash(`mkdir -p ${sessionFolder}/.brainstorming`)
+```
+Parse from $ARGUMENTS:
+  AUTO_YES       ← --yes | -y
+  continueMode   ← --continue
+  maxConcurrency ← --concurrency | -c N  (default: 6)
+  roleCount      ← --count N  (default: 3, max: 9)
+  skipQuestions   ← --skip-questions
+  topicArg       ← remaining text after flag removal
+
+Derive:
+  slug           ← topicArg kebab-cased, max 40 chars
+  dateStr        ← UTC+8 YYYYMMDD
+  sessionId      ← "{dateStr}-brainstorm-{slug}"
+  sessionFolder  ← ".workflow/.csv-wave/{sessionId}"
+
+mkdir -p {sessionFolder}/.brainstorming
 ```
 
 ### Phase 1: Topic Resolution -> CSV
@@ -231,37 +222,22 @@ Bash(`mkdir -p ${sessionFolder}/.brainstorming`)
 
 #### Wave 1: Guidance Specification (Single Agent)
 
-1. Read master `tasks.csv`
-2. Filter rows where `wave == 1` AND `status == pending`
-3. No prev_context needed (wave 1 has no predecessors)
-4. Write `wave-1.csv`
-5. Execute:
+1. Extract wave 1 pending rows from master `tasks.csv` into `wave-1.csv` (no prev_context needed)
+2. Execute:
 
 ```javascript
 spawn_agents_on_csv({
   csv_path: `${sessionFolder}/wave-1.csv`,
   id_column: "id",
   instruction: buildGuidanceInstruction(sessionFolder, topicArg),
-  max_concurrency: 1,
-  max_runtime_seconds: 600,
+  max_concurrency: 1, max_runtime_seconds: 600,
   output_csv_path: `${sessionFolder}/wave-1-results.csv`,
-  output_schema: {
-    type: "object",
-    properties: {
-      id: { type: "string" },
-      status: { type: "string", enum: ["completed", "failed"] },
-      findings: { type: "string" },
-      analysis_file: { type: "string" },
-      error: { type: "string" }
-    },
-    required: ["id", "status", "findings"]
-  }
+  output_schema: { id, status: [completed|failed], findings, analysis_file, error }
 })
 ```
 
-6. Read `wave-1-results.csv`, merge into master `tasks.csv`
-7. Delete `wave-1.csv`
-8. Read generated `guidance-specification.md` for wave 2 context propagation
+3. Merge results into master `tasks.csv`, delete `wave-1.csv`
+4. Read generated `guidance-specification.md` for wave 2 context propagation
 
 **Guidance agent responsibilities**:
 - Analyze topic, extract 5-10 core domain terms
@@ -272,40 +248,23 @@ spawn_agents_on_csv({
 
 #### Wave 2: Role Analysis (Parallel, 3-9 Agents)
 
-1. Read master `tasks.csv`
-2. Filter rows where `wave == 2` AND `status == pending`
-3. Build `prev_context` from wave 1 findings:
-   ```
-   [Task 1: Guidance Specification] Generated guidance-specification.md with N features, M terms defined...
-   ```
-4. Include `guidance-specification.md` content in prev_context for each role agent
-5. Write `wave-2.csv` with `prev_context` column
-6. Execute:
+1. Extract wave 2 pending rows from master `tasks.csv`
+2. Build `prev_context` from wave 1 findings + `guidance-specification.md` content
+3. Write `wave-2.csv` with `prev_context` column
+4. Execute:
 
 ```javascript
 spawn_agents_on_csv({
   csv_path: `${sessionFolder}/wave-2.csv`,
   id_column: "id",
   instruction: buildRoleAnalysisInstruction(sessionFolder),
-  max_concurrency: maxConcurrency,
-  max_runtime_seconds: 900,
+  max_concurrency: maxConcurrency, max_runtime_seconds: 900,
   output_csv_path: `${sessionFolder}/wave-2-results.csv`,
-  output_schema: {
-    type: "object",
-    properties: {
-      id: { type: "string" },
-      status: { type: "string", enum: ["completed", "failed"] },
-      findings: { type: "string" },
-      analysis_file: { type: "string" },
-      error: { type: "string" }
-    },
-    required: ["id", "status", "findings"]
-  }
+  output_schema: { id, status: [completed|failed], findings, analysis_file, error }
 })
 ```
 
-7. Read `wave-2-results.csv`, merge into master `tasks.csv`
-8. Delete `wave-2.csv`
+5. Merge results into master `tasks.csv`, delete `wave-2.csv`
 
 **Role agent responsibilities**:
 - Read guidance-specification.md for framework context
@@ -321,19 +280,10 @@ spawn_agents_on_csv({
 
 #### Wave 3: Synthesis + Feature Index (Single Agent)
 
-1. Read master `tasks.csv`
-2. Filter rows where `wave == 3` AND `status == pending`
-3. Check deps -- if all wave 2 tasks failed, skip synthesis
-4. Build `prev_context` from wave 2 findings:
-   ```
-   [Task 2: System Architect Analysis] Key findings: microservice architecture with event sourcing...
-   [Task 3: UI Designer Analysis] Key findings: component-based design system with real-time cursors...
-   [Task 4: Product Manager Analysis] Key findings: MVP focuses on document editing + presence...
-   ```
-5. Write `wave-3.csv` with `prev_context` column
-6. Execute `spawn_agents_on_csv` for synthesis agent
-7. Merge results into master `tasks.csv`
-8. Delete `wave-3.csv`
+1. If all wave 2 tasks failed, skip synthesis entirely
+2. Extract wave 3 pending rows, build `prev_context` from wave 2 findings
+3. Write `wave-3.csv`, execute `spawn_agents_on_csv` for synthesis agent (same output_schema pattern)
+4. Merge results into master `tasks.csv`, delete `wave-3.csv`
 
 **Synthesis agent responsibilities**:
 - Cross-role analysis: consensus, conflicts, unique contributions
@@ -347,9 +297,8 @@ spawn_agents_on_csv({
 
 **Objective**: Generate final results and human-readable report.
 
-1. Read final master `tasks.csv`
-2. Export as `results.csv`
-3. Generate `context.md`:
+1. Export final `tasks.csv` as `results.csv`
+2. Generate `context.md`:
 
 ```markdown
 # Brainstorm Report -- {topic}
@@ -411,11 +360,7 @@ spawn_agents_on_csv({
 
 #### Protocol
 
-1. **Read** `{session_folder}/discoveries.ndjson` before own analysis
-2. **Skip covered**: If discovery of same type + dedup key exists, skip
-3. **Write immediately**: Append findings as found
-4. **Append-only**: Never modify or delete
-5. **Deduplicate**: Check before writing
+Read `discoveries.ndjson` before analysis. Append-only: dedup by type+key before writing, never modify/delete.
 
 ```bash
 echo '{"ts":"<ISO>","worker":"{id}","type":"terminology","data":{"term":"CRDT","definition":"Conflict-free Replicated Data Type","aliases":["conflict-free"],"category":"technical"}}' >> {session_folder}/discoveries.ndjson

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

@@ -99,26 +99,7 @@ Example: 'analyze the code, then plan, implement, and test the feature'"
 
 **Step 1.6** — Write `intent.json` to `.workflow/templates/design-drafts/WFD-<slug>-<date>/`.
 
-**Step 1.7 — Interactive confirmation**:
-```
-============================================================
-  COMPOSER — Intent Parsed
-============================================================
-  Description: "<original input>"
-  Task type:   <type>
-  Complexity:  <level>
-
-  Detected steps:
-    1. <description>  →  <type_hint>
-    2. <description>  →  <type_hint>
-    3. <description>  →  <type_hint>
-
-  Variables:
-    - goal (required): <inferred description>
-============================================================
-```
-
-AskUserQuestion: `Looks good, continue to resolution` / `Edit steps` / `Add a step` / `Cancel`
+**Step 1.7 — Interactive confirmation**: Display description, task type, complexity, detected steps (numbered with type_hint), and variables. AskUserQuestion: `Continue to resolution` / `Edit steps` / `Add a step` / `Cancel`
 
 ---
 
@@ -153,20 +134,7 @@ If spec not found, use built-in fallback:
 
 **Step 2.4** — Write `nodes.json`.
 
-**Step 2.5 — Interactive confirmation**:
-```
-============================================================
-  COMPOSER — Nodes Resolved
-============================================================
-  N-001  [skill]    maestro-plan          "{goal}"
-  N-002  [skill]    maestro-execute       {phase}
-  N-003  [skill]    quality-test          {phase}
-
-  Parallel groups: none
-============================================================
-```
-
-AskUserQuestion: `Continue to checkpoint injection` / `Change executor` / `Change node type` / `Back to intent` / `Cancel`
+**Step 2.5 — Interactive confirmation**: Display resolved nodes table (ID, type, executor, args) and parallel groups. AskUserQuestion: `Continue to checkpoint injection` / `Change executor` / `Change node type` / `Back to intent` / `Cancel`
 
 ---
 
@@ -195,28 +163,7 @@ Set `auto_continue: false` for checkpoints before user-facing deliverables.
 
 ### Phase 4: Confirm — Visualize + User Approval
 
-**Step 4.1** — Render ASCII pipeline:
-```
-============================================================
-  COMPOSER — Pipeline Review
-============================================================
-Pipeline: <template-name>
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- N-001  [skill]       maestro-plan              "{goal}"
-   |
- CP-01  [checkpoint]  After Plan                auto-continue
-   |
- N-002  [skill]       maestro-execute           {phase}
-   |
- CP-02  [checkpoint]  Before Tests              pause-for-user
-   |
- N-003  [skill]       quality-test              {phase}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Variables (required):  goal
-Checkpoints:           2  (1 auto, 1 pause)
-Nodes:                 3 work + 2 checkpoints
-============================================================
-```
+**Step 4.1** — Render ASCII pipeline: vertical node chain with `|` connectors showing each node (ID, type, executor, args) and checkpoint nodes (auto-continue vs pause-for-user). Footer: required variables, checkpoint counts, node counts.
 
 **Step 4.2** — AskUserQuestion: `Confirm & Save` / `Edit a node` / `Add a node` / `Remove a node` / `Rename template` / `Re-run checkpoint injection` / `Cancel`
 
@@ -236,26 +183,7 @@ Nodes:                 3 work + 2 checkpoints
 
 **Step 5.4** — Update `~/.maestro/templates/workflows/index.json`.
 
-**Step 5.5** — Output summary:
-```
-============================================================
-  COMPOSER — Template Saved
-============================================================
-  Path:      ~/.maestro/templates/workflows/<slug>.json
-  ID:        wft-<slug>-<date>
-  Nodes:     <n> work + <n> checkpoints
-  Variables: <required vars>
-
-  To execute:
-    $maestro-player <slug> --context goal="<your goal>"
-
-  To edit later:
-    $maestro-composer --edit ~/.maestro/templates/workflows/<slug>.json
-
-  To list all templates:
-    $maestro-player --list
-============================================================
-```
+**Step 5.5** — Output summary: path, template ID, node/checkpoint counts, required variables. Include usage commands: `$maestro-player <slug> --context goal="..."`, `$maestro-composer --edit <path>`, `$maestro-player --list`.
 
 **Step 5.6** — Clean up design draft directory.
 </execution>

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

@@ -158,34 +158,22 @@ Each wave generates `wave-{N}.csv` with extra `prev_context` column populated fr
 
 ### Session Initialization
 
-```javascript
-const getUtc8ISOString = () => new Date(Date.now() + 8 * 60 * 60 * 1000).toISOString()
-
-// Parse flags
-const AUTO_YES = $ARGUMENTS.includes('--yes') || $ARGUMENTS.includes('-y')
-const continueMode = $ARGUMENTS.includes('--continue')
-const concurrencyMatch = $ARGUMENTS.match(/(?:--concurrency|-c)\s+(\d+)/)
-const maxConcurrency = concurrencyMatch ? parseInt(concurrencyMatch[1]) : 5
-
-// Parse execute-specific flags
-const autoCommit = $ARGUMENTS.includes('--auto-commit')
-const methodMatch = $ARGUMENTS.match(/--method\s+(agent|cli)/)
-const executionMethod = methodMatch ? methodMatch[1] : null
-const dirMatch = $ARGUMENTS.match(/--dir\s+(\S+)/)
-const scratchDir = dirMatch ? dirMatch[1] : null
-
-// Clean phase text
-const phaseArg = $ARGUMENTS
-  .replace(/--yes|-y|--continue|--concurrency\s+\d+|-c\s+\d+|--auto-commit|--method\s+\w+|--dir\s+\S+/g, '')
-  .trim()
-
-const dateStr = getUtc8ISOString().substring(0, 10).replace(/-/g, '')
-const sessionId = scratchDir
-  ? `${dateStr}-execute-scratch`
-  : `${dateStr}-execute-P${phaseArg}-${phaseSlug}`
-const sessionFolder = `.workflow/.csv-wave/${sessionId}`
-
-Bash(`mkdir -p ${sessionFolder}`)
+```
+Parse from $ARGUMENTS:
+  AUTO_YES        ← --yes | -y
+  continueMode    ← --continue
+  maxConcurrency  ← --concurrency | -c N  (default: 5)
+  autoCommit      ← --auto-commit
+  executionMethod ← --method agent|cli  (default: from config.json)
+  scratchDir      ← --dir <path>  (default: null)
+  phaseArg        ← remaining text after flag removal
+
+Derive:
+  dateStr        ← UTC+8 YYYYMMDD
+  sessionId      ← scratchDir ? "{dateStr}-execute-scratch" : "{dateStr}-execute-P{phaseArg}-{phaseSlug}"
+  sessionFolder  ← ".workflow/.csv-wave/{sessionId}"
+
+mkdir -p {sessionFolder}
 ```
 
 ### Phase 1: Plan Resolution -> CSV
@@ -204,27 +192,13 @@ Bash(`mkdir -p ${sessionFolder}`)
 
    For multi-plan: execute sequentially. Each plan is a full CSV session.
 
-2. **Load plan** (per PLAN_DIR):
-   - Read `{PLAN_DIR}/plan.json` for wave structure
-   - Extract `plan.waves` array with task assignments
+2. **Load plan**: Read `{PLAN_DIR}/plan.json` for wave structure and task assignments
 
-3. **Detect completed tasks (breakpoint resume)**:
-   - For each task in plan, read `.task/TASK-{NNN}.json`
-   - If `status == "completed"`: exclude from CSV
-   - Log: "Resuming: {completed}/{total} tasks already completed"
+3. **Detect completed tasks (breakpoint resume)**: Read `.task/TASK-{NNN}.json` for each task; exclude completed ones from CSV. Log resume count.
 
-4. **Build tasks.csv from task definitions**:
-   - For each pending task in each wave:
-     - Read `.task/TASK-{NNN}.json`
-     - Extract: title, description, files (build scope), convergence.criteria, hints, execution_directives
-     - Set `deps` from task dependency field
-     - Set `context_from` = same as deps (findings propagate along dependency edges)
-     - Set `wave` from plan.json wave assignment
-   - Write `tasks.csv`
+4. **Build tasks.csv**: For each pending task per wave, read `.task/TASK-{NNN}.json` and extract: title, description, scope (from files), convergence.criteria, hints, execution_directives. Set `deps` from task dependency, `context_from` = deps, `wave` from plan.json.
 
-5. **Load project specs**:
-   - Read `.workflow/specs/` for coding conventions and architecture constraints
-   - Pass as context to all executor agents
+5. **Load project specs**: Read `.workflow/specs/` for coding conventions and architecture constraints (passed to all agents)
 
 6. **User validation**: Display task/wave breakdown. Skip if AUTO_YES.
 
@@ -234,160 +208,59 @@ Bash(`mkdir -p ${sessionFolder}`)
 
 #### Per-Wave Execution Loop
 
-For each wave in ascending order:
+For each wave N in ascending order:
 
-1. Read master `tasks.csv`
-2. Filter rows where `wave == N` AND `status == pending`
-3. If no pending tasks in this wave: skip to next wave
-4. Build `prev_context` for each task from completed predecessor findings:
-   ```
-   [TASK-001: Setup auth module] Created src/auth/auth.ts with verifyToken and generateToken...
-   [TASK-002: Create user model] Created src/models/user.ts with User interface...
-   ```
-5. Write `wave-{N}.csv` with `prev_context` column added
-6. Execute:
+1. Extract wave N pending rows from master `tasks.csv` (skip wave if none)
+2. Build `prev_context` per task from completed predecessor findings
+3. Write `wave-{N}.csv` with `prev_context` column, then execute:
 
 ```javascript
 spawn_agents_on_csv({
   csv_path: `${sessionFolder}/wave-${N}.csv`,
   id_column: "id",
   instruction: buildExecutorInstruction(sessionFolder, phaseDir, autoCommit, specsContent),
-  max_concurrency: maxConcurrency,
-  max_runtime_seconds: 900,
+  max_concurrency: maxConcurrency, max_runtime_seconds: 900,
   output_csv_path: `${sessionFolder}/wave-${N}-results.csv`,
-  output_schema: {
-    type: "object",
-    properties: {
-      id: { type: "string" },
-      status: { type: "string", enum: ["completed", "failed", "blocked"] },
-      findings: { type: "string" },
-      files_modified: { type: "string" },
-      tests_passed: { type: "string" },
-      error: { type: "string" }
-    },
-    required: ["id", "status", "findings"]
-  }
+  output_schema: { id, status: [completed|failed|blocked], findings, files_modified, tests_passed, error }
 })
 ```
 
-7. Read `wave-{N}-results.csv`, merge into master `tasks.csv`
-8. Delete `wave-{N}.csv`
+4. Merge results into master `tasks.csv`, delete `wave-{N}.csv`
 
 #### Blocked Task Handling
 
-After each wave:
-- Count blocked/failed tasks
-- If any blocked and NOT AUTO_YES:
-  ```
-  AskUserQuestion: "Tasks blocked: {blocked_list}. Continue to next wave or stop?"
-  Options: [Continue (skip blocked deps), Stop and review]
-  ```
-- If AUTO_YES: auto-continue, skip tasks whose deps are blocked
+After each wave: if blocked tasks exist, prompt user to continue or stop (AUTO_YES: auto-continue). Skip tasks whose deps are blocked/failed.
 
 #### Cascading Skip
 
-If a task is blocked/failed and other tasks in later waves depend on it:
-- Mark dependent tasks as `skipped` with error: "Dependency {dep_id} blocked/failed"
-- Do not attempt execution of skipped tasks
+Blocked/failed tasks cascade: mark all downstream dependents as `skipped` with error "Dependency {dep_id} blocked/failed".
 
 ### Phase 3: Results Aggregation
 
 **Objective**: Update all state files and generate execution report.
 
-1. Read final master `tasks.csv`
-2. Export as `results.csv`
+1. Export final `tasks.csv` as `results.csv`
 
-3. **Update task files**: For each row in results:
-   - Read `.task/{id}.json`
-   - Update `status` to match CSV status
-   - Write back to disk
+2. **Update task files**: Write each task's status from CSV back to `.task/{id}.json`
 
-3b. **Issue status sync**: For each completed/failed task that has `issue_id`:
-   - Read issue from `.workflow/issues/issues.jsonl` by `issue_id`
-   - Collect all `task_refs[]` statuses for that issue:
-     - All task_refs completed -> `issue.status = "resolved"`
-     - Any task_ref failed -> `issue.status = "in_progress"`
+3. **Issue status sync**: For tasks with `issue_id`, update `.workflow/issues/issues.jsonl`:
+   - All task_refs completed -> `issue.status = "resolved"`; any failed -> `"in_progress"`
    - Append history entry: `{ action: "executed", at: <ISO>, by: "maestro-execute", summary: "TASK-{NNN} {status}" }`
-   - Write updated issue back to `issues.jsonl`
-
-4. **Register EXC artifact in state.json**:
-   ```
-   Read .workflow/state.json
-   plan_artifact = state.json.artifacts.find(a => a.type == "plan" && a.path == PLAN_DIR_relative)
-   next_id = max EXC-NNN + 1
-   Push artifact: { id: "EXC-{next_id}", type: "execute", milestone: plan_artifact.milestone,
-     phase: plan_artifact.phase, scope: plan_artifact.scope, path: plan_artifact.path,
-     status: "completed", depends_on: plan_artifact.id, harvested: false,
-     created_at: execution_start, completed_at: now() }
-   Write state.json (atomic)
-   ```
-
-5. **Extract incremental learnings**:
-   - Read all `.summaries/` from PLAN_DIR
-   - Extract strategy adjustments, patterns, pitfalls
-   - Check existing entries via `maestro spec load --category learning` (dedup)
-   - Append to `.workflow/specs/learnings.md` using `<spec-entry>` closed-tag format (category=`learning`, auto-extract keywords, date=today, source=`execute`)
-   - Mark artifact `harvested: true` in state.json
-
-5b. **Post-task Knowledge Inquiry** (after each task completes):
-   - **Execution deviation**: If task summary mentions approach change, dependency swap, or plan deviation:
-     → Ask: "TASK-{NNN} deviated from the plan. Should this decision be recorded as an architecture constraint? (`/spec-add arch`)"
-   - **Retry success**: If task required ≥2 retries before completion:
-     → Ask: "TASK-{NNN} succeeded after {N} retries. Should this fix pattern be documented? (`/spec-add debug`)"
-   - **Implicit knowledge**: If task summary contains design rationale ("chose X because", "rejected Y due to"):
-     → Ask: "Design decision detected. Should it be recorded as a learning? (`/spec-add learning`)"
-   - If user confirms, append `<spec-entry>` to matching category file via `spec-add` mechanism
-
-6. **Generate context.md**:
-
-```markdown
-# Execution Report -- Phase {phase}
-
-## Summary
-- Tasks: {completed}/{total} completed
-- Blocked: {blocked_count}
-- Waves executed: {waves_run}/{waves_total}
-- Auto-commit: {yes/no}
-
-## Wave Results
-
-### Wave {N}
-| Task | Status | Files Modified | Tests |
-|------|--------|---------------|-------|
-| {id}: {title} | {status} | {files} | {tests} |
-
-## Blocked Tasks
-{if any: task ID, error, checkpoint info}
-
-## Discovery Board Summary
-{aggregated discovery findings}
-
-## Next Steps
-- Run verify to validate results
-- Run debug for any blocked tasks
-```
 
-7. **Auto-sync** (if config.json.codebase.auto_sync_after_execute == true):
-   - Detect changed files from execution
-   - Trigger codebase doc update
+4. **Register EXC artifact in state.json**: Find matching plan artifact, create `{ id: "EXC-{next_id}", type: "execute", milestone, phase, scope, path, status: "completed", depends_on: plan_artifact.id, harvested: false, created_at, completed_at }`
 
-8. **Display completion report**:
+5. **Extract incremental learnings**: Read `.summaries/`, dedup against existing specs, append to `.workflow/specs/learnings.md` as `<spec-entry>` (category=learning), mark artifact `harvested: true`
 
-```
-=== EXECUTION COMPLETE ===
-Phase:     {phase_name}
-Completed: {completed_count}/{total_count} tasks
-Blocked:   {blocked_count} tasks
-Waves:     {waves_executed}/{total_waves}
-
-Summaries: {PLAN_DIR}/.summaries/
-Tasks:     {PLAN_DIR}/.task/
-
-Next steps:
-  Skill({ skill: "maestro-verify" })
-  Skill({ skill: "maestro-verify", args: "--dir {PLAN_DIR}" })
-  Skill({ skill: "manage-status" })
-```
+6. **Post-task Knowledge Inquiry**: Prompt user to capture knowledge when:
+   - Execution deviation detected (plan change) -> `/spec-add arch`
+   - Retry success (>=2 retries) -> `/spec-add debug`
+   - Implicit design rationale found -> `/spec-add learning`
+
+7. **Generate context.md**: Execution report with summary (tasks/blocked/waves/auto-commit), per-wave result table (task, status, files, tests), blocked tasks, discovery board summary, next steps.
+
+8. **Auto-sync** (if config.json.codebase.auto_sync_after_execute == true): detect changed files, trigger codebase doc update.
+
+9. **Display completion report**: Phase, completed/blocked counts, wave progress, paths to `.summaries/` and `.task/`, next step suggestions (`maestro-verify`, `manage-status`).
 
 ### Shared Discovery Board Protocol
 
@@ -404,11 +277,7 @@ Next steps:
 
 #### Protocol
 
-1. **Read** `{session_folder}/discoveries.ndjson` before starting task implementation
-2. **Skip covered**: If discovery of same type + dedup key exists, skip
-3. **Write immediately**: Append findings as discovered
-4. **Append-only**: Never modify or delete existing entries
-5. **Deduplicate**: Check before writing
+Read `discoveries.ndjson` before implementation. Append-only: dedup by type+key before writing, never modify/delete.
 
 ```bash
 echo '{"ts":"<ISO>","worker":"TASK-001","type":"code_pattern","data":{"name":"Result type","file":"src/types/result.ts","description":"All functions return Result<T,E> for error handling"}}' >> {session_folder}/discoveries.ndjson

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

@@ -46,11 +46,7 @@ Extract flags from arguments:
 
 ### Step 2: Detect Project State
 
-```bash
-# Check existing state
-ls .workflow/state.json 2>/dev/null
-ls package.json pyproject.toml Cargo.toml go.mod 2>/dev/null
-```
+Check for `.workflow/state.json` and common manifests (`package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`).
 
 Classify as:
 - **existing**: `.workflow/state.json` found — warn and exit (E002)
@@ -86,67 +82,27 @@ Read the following templates:
 
 ### Step 5: Create .workflow/ Structure
 
-```bash
-mkdir -p .workflow/specs .workflow/scratch .workflow/codebase
-```
+Create directories: `.workflow/specs`, `.workflow/scratch`, `.workflow/codebase`.
 
 ### Step 6: Write project.md
 
-Populate template with gathered information:
-- Project name, core value proposition
-- Requirements: Validated / Active / Out of Scope
-- Key decisions and constraints
-- Tech stack (detected or specified)
-
-Write to `.workflow/project.md`.
+Populate template with: project name, core value proposition, requirements (Validated/Active/Out of Scope), key decisions, constraints, tech stack. Write to `.workflow/project.md`.
 
 ### Step 7: Write state.json
 
-Initialize state from template:
-- `current_milestone`: null
-- `current_task_id`: null
-- `status`: "initialized"
-- `artifacts`: []
-
-Write to `.workflow/state.json`.
+Initialize from template with `current_milestone: null`, `status: "initialized"`, empty `artifacts[]`. Write to `.workflow/state.json`.
 
 ### Step 8: Write config.json
 
-Configuration questions (or defaults for --auto):
-- Granularity: fine / medium / coarse
-- Workflow agents: enable/disable optional agents
-- Gate preferences: verification strictness
-
-Write to `.workflow/config.json`.
+Configuration questions (or defaults for --auto): granularity (fine/medium/coarse), workflow agents (enable/disable), gate preferences. Write to `.workflow/config.json`.
 
 ### Step 9: Initialize specs/
 
-Create convention files in `.workflow/specs/`:
-- `conventions.md` — detected or specified coding conventions
-- `learnings.md` — empty, populated during execute summaries extraction
+Create in `.workflow/specs/`: `conventions.md` (detected coding conventions), `learnings.md` (empty placeholder).
 
 ### Step 10: Completion Report
 
-```
-=== WORKFLOW INITIALIZED ===
-Project: {project_name}
-State:   .workflow/state.json (active)
-
-Created:
-  .workflow/project.md
-  .workflow/state.json
-  .workflow/config.json
-  .workflow/specs/
-
-Next steps (choose one path to create roadmap):
-  $maestro-spec-generate "<idea>"   -- Full spec package + roadmap (heavy)
-  $maestro-roadmap "<requirement>"  -- Direct interactive roadmap (light)
-
-Other commands:
-  $manage-status                   -- View project dashboard
-  $maestro-brainstorm "<topic>"     -- Explore ideas first
-  $maestro-quick "<task>"           -- Quick ad-hoc task
-```
+Display created files and next steps: `$maestro-spec-generate` (full spec), `$maestro-roadmap` (light), `$manage-status`, `$maestro-brainstorm`, `$maestro-quick`.
 
 </execution>