maestro-flow 0.5.41 → 0.5.42

package/.agents/skills/team-swarm/roles/analyst/role.md

@@ -9,179 +9,175 @@ message_types:
 ---
 <!-- Open-standard mirror generated by scripts/build-agents-standard.mjs — do not edit; re-run after editing .claude/ source. -->
 
-
-# Analyst Role — Phase 2-4
-
-Tag: `[analyst]` | Prefix: `ANALYST-*`
-Responsibility: After swarm converges, synthesize the best solution + top trails + convergence curve into a human-readable `best-solution.md` report. Provides interpretation, not just data dump.
-
-## Boundaries
-
-### MUST
-- Read `<session>/best.json`, `<session>/artifacts/swarm-report.json`, all `<session>/trails/*.jsonl`
-- Produce `<session>/artifacts/best-solution.md` as the final deliverable
-- Explain WHY the best path won (which decisions mattered, evidence chain)
-- Compare best vs runner-ups to surface stability vs luck
-- Document convergence story (entropy curve, when stagnation hit)
-
-### MUST NOT
-- Re-score solutions (that is scorer's job — analyst takes verified_score as given)
-- Modify best.json, trails, or pheromone state
-- Generate solutions of its own — analyst synthesizes existing ant outputs
-- Exceed ~150 lines in best-solution.md (be sharp, not verbose)
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Original objective | `<session>/swarm-config.json#ant_prompt.objective` | Yes |
-| Best solution | `<session>/best.json` | Yes |
-| Full swarm report | `<session>/artifacts/swarm-report.json` | Yes |
-| All trails | `<session>/trails/*.jsonl` | Yes |
-| Convergence reason | swarm-report.json or `aco.py converged` output | Yes |
-| Best ant artifact | `<session>/artifacts/ant-<best.iteration>-<best.id>.json` (full evidence) | Yes |
-| Issues log | `<session>/wisdom/issues.md` | Optional |
-
-Workflow:
-1. Extract session path from task description
-2. Read swarm-config.json -> capture objective
-3. Read best.json -> identify best ant
-4. Read full swarm-report.json -> get top_k + convergence_curve
-5. Read the best ant's full artifact for evidence chain
-6. Read all trails/*.jsonl into a list (chronological)
-
-## Phase 3: Synthesis
-
-### 3.1 Structure the report
-
-Layout for `best-solution.md`:
-
-```markdown
-# Swarm Result — <objective_short_form>
-
-## Best Solution
-
-**Path**: node_a → node_c → node_f
-**Verified Score**: 0.82
-**Iteration**: 3 of 5
-**Ant**: ANT-3-2
-
-### Summary
-<one paragraph — what the best solution proposes and why it answers the objective>
-
-### Evidence Chain
-- `src/foo.ts:42` — <how this evidence supports the decision>
-- `tests/foo.spec.ts:18` — <...>
-
-### Candidate Artifact
-<extract from best.candidate_solution — quote or summarize, link to file if file_ref>
-
-## Why This Path Won
-
-| Decision | Pheromone-guided? | Why it mattered |
-|----------|-------------------|-----------------|
-| start = node_a | weighted | <reason> |
-| a → c | yes (0.45 hint) | <reason> |
-| c → f | NO (deviation) | <reason> — this was the key call |
-
-## Runner-Up Solutions
-
-| Rank | Ant | Path | Score | Diff from best |
-|------|-----|------|-------|----------------|
-| 2 | ANT-2-1 | a → b → e | 0.74 | -0.08; weaker evidence at e |
-| 3 | ANT-4-3 | a → c → g | 0.71 | -0.11; valid but less specific |
-
-## Convergence Story
-
-Iterations: 4 of 5 max
-Trigger: stagnation (best unchanged for 2 iterations)
-
-Entropy curve:
-- iter 1: 3.21 (broad exploration)
-- iter 2: 2.45 (narrowing on node_a region)
-- iter 3: 1.85 (best emerges at ANT-3-2)
-- iter 4: 1.72 (consensus around best, no improvement)
-
-Interpretation: <2-3 sentences on whether the swarm converged on a genuine optimum or got stuck>
-
-## Caveats
-
-- <e.g., 40% of ants in iter 2 flagged as hallucinations>
-- <e.g., evidence for node_f is single-source — recommend manual verification>
-- <e.g., search space had only N nodes — larger space may surface better solutions>
-
-## Reproducibility
-
-- Config: `swarm-config.json` (pinned)
-- Best path: `best.json`
-- Full trails: `trails/<iter>.jsonl`
-- Random seed: <if used>
-```
-
-### 3.2 Interpretation rules
-
-- **Why-it-won analysis** is the highest-value content. Don't just describe the path — explain which decisions were pivotal.
-- **Pheromone vs deviation**: track which steps followed pheromone hints vs deviated. Deviations that produced higher scores are the most interesting signal.
-- **Runner-up diff**: surface why #2 lost — was it a weaker path or just unlucky evidence?
-- **Caveats are mandatory**: every swarm result has limitations. List them honestly.
-
-### 3.3 Constraints
-
-- Target ≤ 150 lines
-- No prose padding — every section earns its place
-- Quote evidence verbatim where possible (file:line refs)
-- Don't editorialize beyond what evidence supports
-
-## Phase 4: Verify + Publish
-
-### Behavioral Traits
-
-#### Accuracy
-- Every cited path/score MUST match best.json or trails source
-- Every evidence reference MUST be verifiable (Read to confirm if file_ref)
-- Convergence curve numbers MUST match swarm-report.json#convergence_curve
-
-#### Feedback Contract
-| Field | Required | Content |
-|-------|----------|---------|
-| artifacts_written | Always | `<session>/artifacts/best-solution.md` |
-| line_count | Always | int (target ≤ 150) |
-| verification_method | Always | "cross_ref_with_best.json + evidence_verified" |
-
-#### Quality Gate
-- Final report file exists and parses as markdown
-- All sections present (Best Solution / Why Won / Runner-Ups / Convergence / Caveats / Reproducibility)
-- Line count ≤ 200 (hard cap — fail if exceeded, retry with sharper edit)
-
-### Verification Steps
-
-1. Read written best-solution.md back
-2. Cross-check best.score against best.json
-3. Confirm runner-up scores against trails
-4. If file_ref evidence in best.candidate_solution -> Read to confirm file exists
-5. Count lines — if > 200, condense and rewrite
-
-### State Update
-
-```json
-{
-  "task_id": "ANALYST-1",
-  "role": "analyst",
-  "status": "completed",
-  "artifact_path": "<session>/artifacts/best-solution.md",
-  "best_score": <float>,
-  "best_ant_id": "<id>",
-  "line_count": <int>,
-  "verification": "cross_ref_pass + evidence_verified"
-}
-```
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| best.json missing | Pipeline produced no valid ant — write minimal report with `status: no_solution` |
-| Trails empty | Same as above — no exploration data to analyze |
-| Best ant artifact missing | Use only best.json fields; note as caveat |
-| Cross-ref mismatch (score discrepancy) | Trust best.json; note discrepancy in caveats |
-| Line count > 200 after rewrite | Hard-fail report; coordinator decides retry vs accept |
+
+# Analyst Role — Phase 2-4
+
+Tag: `[analyst]` | Prefix: `ANALYST-*`
+Responsibility: After swarm converges, synthesize the best solution + top trails + convergence curve into a human-readable `best-solution.md` report. Provides interpretation, not just data dump.
+
+## Boundaries
+
+### MUST
+- Read `<session>/best.json`, `<session>/artifacts/swarm-report.json`, all `<session>/trails/*.jsonl`
+- Produce `<session>/artifacts/best-solution.md` as the final deliverable
+- Explain WHY the best path won (which decisions mattered, evidence chain)
+- Compare best vs runner-ups to surface stability vs luck
+- Document convergence story (entropy curve, when stagnation hit)
+
+### MUST NOT
+- Re-score solutions (that is scorer's job — analyst takes verified_score as given)
+- Modify best.json, trails, or pheromone state
+- Generate solutions of its own — analyst synthesizes existing ant outputs
+- Pad best-solution.md with prose — every section must earn its place
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Original objective | `<session>/swarm-config.json#ant_prompt.objective` | Yes |
+| Best solution | `<session>/best.json` | Yes |
+| Full swarm report | `<session>/artifacts/swarm-report.json` | Yes |
+| All trails | `<session>/trails/*.jsonl` | Yes |
+| Convergence reason | swarm-report.json or `aco.py converged` output | Yes |
+| Best ant artifact | `<session>/artifacts/ant-<best.iteration>-<best.id>.json` (full evidence) | Yes |
+| Issues log | `<session>/wisdom/issues.md` | Optional |
+
+Workflow:
+1. Extract session path from task description
+2. Read swarm-config.json -> capture objective
+3. Read best.json -> identify best ant
+4. Read full swarm-report.json -> get top_k + convergence_curve
+5. Read the best ant's full artifact for evidence chain
+6. Read all trails/*.jsonl into a list (chronological)
+
+## Phase 3: Synthesis
+
+### 3.1 Structure the report
+
+Layout for `best-solution.md`:
+
+```markdown
+# Swarm Result — <objective_short_form>
+
+## Best Solution
+
+**Path**: node_a → node_c → node_f
+**Verified Score**: 0.82
+**Iteration**: 3 of 5
+**Ant**: ANT-3-2
+
+### Summary
+<one paragraph — what the best solution proposes and why it answers the objective>
+
+### Evidence Chain
+- `src/foo.ts:42` — <how this evidence supports the decision>
+- `tests/foo.spec.ts:18` — <...>
+
+### Candidate Artifact
+<extract from best.candidate_solution — quote or summarize, link to file if file_ref>
+
+## Why This Path Won
+
+| Decision | Pheromone-guided? | Why it mattered |
+|----------|-------------------|-----------------|
+| start = node_a | weighted | <reason> |
+| a → c | yes (0.45 hint) | <reason> |
+| c → f | NO (deviation) | <reason> — this was the key call |
+
+## Runner-Up Solutions
+
+| Rank | Ant | Path | Score | Diff from best |
+|------|-----|------|-------|----------------|
+| 2 | ANT-2-1 | a → b → e | 0.74 | -0.08; weaker evidence at e |
+| 3 | ANT-4-3 | a → c → g | 0.71 | -0.11; valid but less specific |
+
+## Convergence Story
+
+Iterations: 4 of 5 max
+Trigger: stagnation (best unchanged for 2 iterations)
+
+Entropy curve:
+- iter 1: 3.21 (broad exploration)
+- iter 2: 2.45 (narrowing on node_a region)
+- iter 3: 1.85 (best emerges at ANT-3-2)
+- iter 4: 1.72 (consensus around best, no improvement)
+
+Interpretation: <2-3 sentences on whether the swarm converged on a genuine optimum or got stuck>
+
+## Caveats
+
+- <e.g., 40% of ants in iter 2 flagged as hallucinations>
+- <e.g., evidence for node_f is single-source — recommend manual verification>
+- <e.g., search space had only N nodes — larger space may surface better solutions>
+
+## Reproducibility
+
+- Config: `swarm-config.json` (pinned)
+- Best path: `best.json`
+- Full trails: `trails/<iter>.jsonl`
+- Random seed: <if used>
+```
+
+### 3.2 Interpretation rules
+
+- **Why-it-won analysis** is the highest-value content. Don't just describe the path — explain which decisions were pivotal.
+- **Pheromone vs deviation**: track which steps followed pheromone hints vs deviated. Deviations that produced higher scores are the most interesting signal.
+- **Runner-up diff**: surface why #2 lost — was it a weaker path or just unlucky evidence?
+- **Caveats are mandatory**: every swarm result has limitations. List them honestly.
+
+### 3.3 Constraints
+
+- No prose padding — every section earns its place
+- Quote evidence verbatim where possible (file:line refs)
+- Don't editorialize beyond what evidence supports
+
+## Phase 4: Verify + Publish
+
+### Behavioral Traits
+
+#### Accuracy
+- Every cited path/score MUST match best.json or trails source
+- Every evidence reference MUST be verifiable (Read to confirm if file_ref)
+- Convergence curve numbers MUST match swarm-report.json#convergence_curve
+
+#### Feedback Contract
+| Field | Required | Content |
+|-------|----------|---------|
+| artifacts_written | Always | `<session>/artifacts/best-solution.md` |
+| line_count | Always | int (informational) |
+| verification_method | Always | "cross_ref_with_best.json + evidence_verified" |
+
+#### Quality Gate
+- Final report file exists and parses as markdown
+- All sections present (Best Solution / Why Won / Runner-Ups / Convergence / Caveats / Reproducibility)
+
+### Verification Steps
+
+1. Read written best-solution.md back
+2. Cross-check best.score against best.json
+3. Confirm runner-up scores against trails
+4. If file_ref evidence in best.candidate_solution -> Read to confirm file exists
+
+### State Update
+
+```json
+{
+  "task_id": "ANALYST-1",
+  "role": "analyst",
+  "status": "completed",
+  "artifact_path": "<session>/artifacts/best-solution.md",
+  "best_score": <float>,
+  "best_ant_id": "<id>",
+  "line_count": <int>,
+  "verification": "cross_ref_pass + evidence_verified"
+}
+```
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| best.json missing | Pipeline produced no valid ant — write minimal report with `status: no_solution` |
+| Trails empty | Same as above — no exploration data to analyze |
+| Best ant artifact missing | Use only best.json fields; note as caveat |
+| Cross-ref mismatch (score discrepancy) | Trust best.json; note discrepancy in caveats |

package/.agy/skills/maestro-analyze/SKILL.md

@@ -88,51 +88,9 @@ Follows @~/.maestro/workflows/interview-mechanics.md standard.
 <execution>
 Follow '~/.maestro/workflows/analyze.md' completely.
 
-### Evidence-Backed Decisions
-
-Every decision MUST trace to independently gathered evidence. Manual Read/Grep is preparation — NOT evidence. Valid evidence sources:
-- cli-explore-agent output (code anchors, call chains, data flows)
-- maestro delegate CLI analysis output (multi-perspective findings)
-- User-provided input (domain knowledge, constraints, corrections)
-
-Decisions without CLI/agent-sourced evidence MUST be flagged as LOW CONFIDENCE.
-
-### Boundary Grill (Step 5 → Step 6)
-
-After discussion rounds, BEFORE synthesis: run boundary grill per `~/.maestro/workflows/boundary-grill.md`.
-Input: discussion.md decisions + exploration-codebase.json. Scope guard: "only analyze decisions; do not prejudge plan/execute concerns".
-IF conflicts → results to `analysis.md` § Boundary Grill Results + update `context.md` Locked/Free/Deferred.
-
-### Standard Mode Gates
-
-Gates 1-4 are defined in `analyze.md`. NEVER skip gates. NEVER substitute manual Read/Grep for agent/CLI exploration.
-
-### Artifact Verification
-
-Before writing the completion report (Step 9), verify ALL expected artifacts exist in OUTPUT_DIR:
-```
-FULL_MODE_REQUIRED = [
-  "discussion.md",             // Step 3+5
-  "exploration-codebase.json", // Step 4.1
-  "explorations.json" OR "perspectives.json", // Step 4.3
-  "analysis.md",               // Step 6
-  "conclusions.json",          // Step 7
-  "context.md",                // Step 8
-  "context-package.json"       // Step 8.6
-]
-```
-If any artifact is missing: DO NOT report completion. Produce the missing artifact first.
-
 ### --gaps Mode
 
 When `--gaps` is present, follow `~/.maestro/workflows/issue-gaps-analyze.md` instead of the standard pipeline.
-
-**Handoff:** context.md is consumed by maestro-plan. In --gaps mode, context.md contains issue root causes for `plan --gaps`.
-
-**scope_verdict** (added to context.md in Step 6 Synthesis for macro/adhoc/standalone scopes):
-- `large` (3+ independent subsystems or hard serial dependencies) → suggest `/maestro-roadmap --from analyze:ANL-xxx`
-- `medium` (1-2 subsystems, parallelizable) → suggest `/maestro-plan --from analyze:ANL-xxx`
-- `small` (single-file or few-file change) → suggest `/maestro-plan --from analyze:ANL-xxx`
 </execution>
 
 <completion>

package/.agy/skills/maestro-blueprint/SKILL.md

@@ -90,28 +90,6 @@ Each phase produces artifacts that are prerequisites for the next. Do NOT advanc
 **GATE P5 → P6**: `epics/` directory with `_index.md` + individual `EPIC-*.md` files. Cross-Epic dependency map present.
 **GATE P6**: Readiness score computed. Pass (≥80%) or Review (≥60%) required for handoff.
 
-### Artifact Verification (before completion)
-
-```
-REQUIRED_ARTIFACTS = [
-  "blueprint-config.json",        // P0
-  "product-brief.md",             // P2
-  "glossary.json",                // P2 (≥5 terms)
-  "requirements/_index.md",       // P3
-  "architecture/_index.md",       // P4
-  "epics/_index.md",              // P5
-  "readiness-report.md",          // P6
-  "blueprint-summary.md",         // P6
-  "context-package.json"          // P6
-]
-```
-If any artifact is missing: DO NOT report completion. Go back and produce it.
-
-### Evidence Requirement
-
-Architecture Decision Records (ADR-*.md) MUST cite evidence for each decision:
-- Valid: code analysis, requirement traceability (REQ-xxx), upstream context, CLI analysis output
-- INVALID: generic rationale without reference to project-specific constraints
 </execution>
 
 <completion>

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

@@ -92,35 +92,15 @@ These gates apply to Auto mode (full pipeline). Do NOT advance past a gate until
 - BLOCKED if missing: complete all role analyses before spawning cross-role-reviewer.
 
 **GATE 2.5: Cross-Role Review → Boundary Grill** (Step 4.5 → Step 4.6)
-Run boundary grill per `~/.maestro/workflows/boundary-grill.md` after cross-role-reviewer output.
-Input: reviewer findings + role Decision Digests. Scope guard: "only brainstorm decisions; do not pre-resolve roadmap/plan choices".
-IF conflicts → results to `guidance-specification.md` §12.5 + feed into GATE 3. NON-BLOCKING.
+- REQUIRED: Boundary grill executed per workflow boundary-grill.md after cross-role review.
+- NON-BLOCKING: conflicts logged as warnings.
 
 **GATE 3: Cross-Role Review → Completion** (Step 4.5/4.6 → Report)
 - REQUIRED: Cross-role-reviewer output received with `patch_targets[]`.
-- REQUIRED: Boundary grill completed (if conflicts detected, results logged).
-- REQUIRED: If findings > 0, resolutions applied via Edit AND logged in `guidance-specification.md` §12.
-- REQUIRED: If findings == 0, final report explicitly states "No cross-role issues detected".
+- REQUIRED: Boundary grill completed.
+- REQUIRED: Resolutions applied and logged (details in workflow).
 - BLOCKED if missing: complete review synthesis before reporting.
 
-### Artifact Verification (before completion report)
-
-```
-AUTO_MODE_REQUIRED = [
-  "guidance-specification.md",            // Step 1
-  "{role}/analysis.md" (per selected role), // Step 3
-  "{role}/analysis-F-*.md" (per feature),   // Step 3
-]
-```
-If any artifact is missing: DO NOT report completion. Go back and produce the missing artifact.
-
-### Evidence Requirement
-
-Role analysis findings in `{role}/analysis.md` §2 Decision Digest MUST cite concrete evidence:
-- Code references (file:line), API endpoints, data models from the codebase
-- User-provided constraints from interview
-- Cross-role references to other role analyses
-Decisions without evidence are flagged LOW CONFIDENCE.
 </execution>
 
 <completion>

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

@@ -39,7 +39,7 @@ $ARGUMENTS — phase number, or no args for milestone-wide execution, with optio
 | `--method agent\|cli\|auto` | Execution method: Agent tool, CLI delegate, or auto-select | `auto` |
 | `--executor <tool>` | Explicit executor tool for CLI delegate mode | First enabled in config |
 | `--dir <path>` | Execute a specific plan directory instead of auto-discovery | — |
-| `-y` / `--yes` | Auto mode — skip interactive questions | false |
+| `-y` / `--yes` | Auto mode — skip ALL interactive questions (executor selection, wave progression, blocked prompts) | false |
 
 ### Scope routing
 

package/.agy/skills/maestro-grill/SKILL.md

@@ -93,22 +93,6 @@ Follow '~/.maestro/workflows/grill.md' completely.
 - REQUIRED: `context-package.json` generated.
 - BLOCKED if any artifact missing: produce it before reporting completion.
 
-### Evidence Requirement
-
-Grill questions MUST reference specific code (`file:line`) when challenging the user's proposal. Generic questions without code grounding are INVALID.
-
-If codebase scan failed (W001): flag ALL subsequent locked decisions as LOW CONFIDENCE.
-
-### Artifact Verification (before completion)
-
-```
-REQUIRED_ARTIFACTS = [
-  "grill-report.md",        // Branch Log + Q&A + synthesis
-  "terminology.md",         // ≥5 terms with code refs
-  "context-package.json"    // Schema "context-package/1.0"
-]
-```
-If any missing: DO NOT report completion. Go back and produce the missing artifact.
 </execution>
 
 <completion>

package/.agy/skills/maestro-milestone-audit/SKILL.md

@@ -71,21 +71,6 @@ Audit checklist steps (phase coverage, ad-hoc completeness, execution completene
 - REQUIRED: Clear PASS/FAIL verdict determined with evidence for each check.
 - BLOCKED if missing: integration check not completed — do not write report without cross-artifact verification.
 
-### Artifact Verification (before completion)
-
-```
-REQUIRED_ARTIFACTS = [
-  ".workflow/milestones/{milestone}/audit-report.md"  // Clear PASS/FAIL verdict
-]
-```
-If missing: DO NOT report completion. Write the audit report first.
-
-### Evidence Requirement
-
-Every audit check result MUST cite what was examined and what was found:
-- PASS: "Phase 1 chain complete: ANL-001 → PLN-001 → EXC-001, all tasks completed"
-- FAIL: "Phase 2 missing EXC artifact — PLN-002 exists but no execution found"
-- Do NOT mark checks as PASS without verifying the actual artifact exists and contains expected content.
 </execution>
 
 <completion>

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

@@ -88,79 +88,22 @@ Follow '~/.maestro/workflows/plan.md' completely.
 - BLOCKED if missing: plan.json or TASK files not produced by planner agent — do not proceed to checking.
 
 **GATE P3.5 → P4: Boundary Grill → Plan Check**
-Run boundary grill per `~/.maestro/workflows/boundary-grill.md`.
-Input: plan.json tasks + convergence criteria + upstream context. Scope guard: "only plan scope; do not re-analyze or re-scope".
-IF conflicts → results to plan.json `boundary_grill` section + affected TASK files. DEC conflicts add `boundary_warning` to confidence.
-NON-BLOCKING: warnings, not hard stops.
+- REQUIRED: Boundary grill executed per workflow boundary-grill.md.
+- NON-BLOCKING: conflicts logged as warnings, not hard stops.
 
 **GATE P4 → P5: Plan Check → User Confirmation**
 - REQUIRED: Plan-checker passed (or minor issues acknowledged).
-- REQUIRED: Boundary grill completed (conflicts resolved or accepted as risks).
+- REQUIRED: Boundary grill completed.
 - REQUIRED: Confidence scored with 5-dimension factor model.
 - REQUIRED: Pressure pass completed on highest-complexity task.
-- REQUIRED: If plan touches UI (检出 `dashboard/` 或 UI 关键词 `landing|page|dashboard|frontend|UI|component|界面`), each delivery wave has ≥1 `[UI-observable]` convergence criterion (vertical-slice delivery, not backend-only).
-- BLOCKED if: plan-checker found critical issues, OR UI plan missing `[UI-observable]` coverage — fix plan before presenting to user.
+- REQUIRED: UI plans have `[UI-observable]` convergence criteria per wave (details in workflow).
+- BLOCKED if: plan-checker found critical issues, OR UI plan missing `[UI-observable]` coverage.
 
 **GATE P5 → Completion: User Confirmation → Done**
 - REQUIRED: User confirmation captured (execute/modify/cancel).
 - REQUIRED: PLN artifact registered in state.json.
 - BLOCKED if missing: no user confirmation — do not register artifact or report completion.
 
-### Artifact Verification (before completion)
-
-```
-REQUIRED_ARTIFACTS = [
-  "plan.json",                    // Task definitions, waves, summary
-  ".task/TASK-*.json" (per task)   // Individual task files with convergence criteria
-]
-```
-Every task MUST have `convergence.criteria[]` with grep-verifiable conditions. If any task lacks verifiable criteria: DO NOT report completion — fix the criteria first.
-
-### P3 Agent Constraint (MANDATORY)
-
-Main flow **MUST** spawn a planner agent (Agent tool) for P3 planning — inline planning by main flow is FORBIDDEN. The agent produces both `plan.json` and `.task/TASK-*.json` files. Main flow only passes context and validates output.
-
-### Codebase Docs Loading (P1 addition)
-
-During P1 Context Collection, after loading context files, load codebase documentation if available:
-
-```
-IF exists(.workflow/codebase/doc-index.json):
-  codebase_ctx = view_file(.workflow/codebase/ARCHITECTURE.md) + view_file(.workflow/codebase/FEATURES.md)
-  Pass codebase_ctx to planner agent as structural context
-ELSE:
-  display "W004: Codebase docs unavailable, continuing with code exploration only"
-```
-
-### Wiki Knowledge Search (P1 addition)
-
-During P1 Context Collection, after loading context files and before parallel exploration (step 5), search the wiki for prior knowledge related to the phase:
-
-```
-phase_keywords = extract key terms from goal/title (2-5 terms)
-wiki_result = run_command("maestro search ${phase_keywords} --json 2>/dev/null")
-
-IF wiki_result exit code != 0 OR empty:
-  display "W003: Wiki search unavailable, continuing without prior knowledge"
-ELSE:
-  entries = JSON.parse(wiki_result).entries (limit to first 10)
-  wiki_context = structured block for downstream stages
-```
-
-### Issue Linkback (--gaps mode)
-
-After plan generation and checking, if `--gaps` mode was used, link TASK files back to issues bidirectionally:
-
-```
-For each created TASK-{NNN}.json that has issue_id:
-  Update corresponding issue in .workflow/issues/issues.jsonl:
-    task_refs: append TASK-{NNN} to array
-    task_plan_dir: relative path to .task/ directory
-    status: "planned"
-    updated_at: now()
-  Append history entry: { action: "planned", at: <ISO>, by: "maestro-plan", summary: "Linked to TASK-{NNN}" }
-```
-
 ### Mode: Revise / Check
 
 Follow workflow plan.md § "Revise Mode" and § "Check Mode" respectively. These modes bypass the standard P1-P5 create pipeline.

package/.agy/skills/maestro-roadmap/SKILL.md

@@ -98,14 +98,6 @@ Sub-modes:
 - REQUIRED: Artifact registered in state.json with milestone entries.
 - BLOCKED if missing: do not report completion without written roadmap.
 
-### Artifact Verification (before completion)
-
-```
-REQUIRED_ARTIFACTS = [
-  ".workflow/roadmap.md"    // Milestone > Phase hierarchy with progress table
-]
-```
-If missing: DO NOT report completion.
 
 </execution>