maestro-flow 0.3.32 → 0.3.34

package/.claude/commands/learn-retro.md

@@ -259,7 +259,7 @@ Write `.workflow/learning/retro-{date}.json` with structured data.
 **Next-step routing:**
 - Browse insights → `/manage-learn list --tag retro`
 - Deep dive on high-churn file → `/learn-follow <path>`
-- Fix test gaps → `/quality-test-gen <area>`
+- Fix test gaps → `/quality-auto-test <area>`
 - Create issue for questionable decision → `/manage-issue create ...`
 - Investigate stale decision → `/learn-investigate <question>`
 - Full phase retrospective → `/quality-retrospective`

package/.claude/commands/maestro-composer.md

@@ -97,7 +97,7 @@ Example: 'analyze the code, then plan, implement, and test the feature'"
 
 **Step 1.3** — Extract variables (inputs that vary per run). Detect from: direct mentions, `{var}` patterns, implicit from task type.
 
-**Step 1.4** — Classify task type: `bugfix | feature | tdd | review | brainstorm | spec-driven | roadmap | refactor | integration-test | quick-task | custom`
+**Step 1.4** — Classify task type: `bugfix | feature | tdd | review | brainstorm | spec-driven | roadmap | refactor | auto-test | quick-task | custom`
 
 **Step 1.5** — Assess complexity: `simple` (1-3 nodes), `medium` (4-7), `complex` (8+)
 
@@ -212,7 +212,7 @@ options:
 | Agent spawn | Target type is `agent` |
 | Long-running | Target is maestro-plan, maestro-roadmap --mode full |
 | User-defined | Step had `type_hint: checkpoint` |
-| Post-testing | Source executor contains `test` or `integration-test` |
+| Post-testing | Source executor contains `test` or `auto-test` |
 
 Set `auto_continue: false` for checkpoints before user-facing deliverables.
 

package/.claude/commands/maestro-ralph-execute.md

@@ -191,7 +191,7 @@ auto_flag_map = {
   "maestro-ui-design": "-y",
   "maestro-plan": "-y",
   "maestro-execute": "-y",
-  "quality-business-test": "-y",
+  "quality-auto-test": "-y",
   "quality-test": "-y --auto-fix",
   "quality-retrospective": "-y",
   "maestro-milestone-complete": "-y"

package/.claude/commands/maestro-ralph.md

@@ -211,9 +211,9 @@ analyze            maestro-analyze {phase}       cli     —
 plan               maestro-plan {phase}          skill   —
 execute            maestro-execute {phase}       cli     —
 verify             maestro-verify {phase}        skill   decision:post-verify
-business-test      quality-business-test {phase}  skill   decision:post-business-test
+business-test      quality-auto-test {phase}      skill   decision:post-business-test
 review             quality-review {phase}        skill   decision:post-review
-test-gen           quality-test-gen {phase}      skill   —
+test-gen           quality-auto-test {phase}     skill   —
 test               quality-test {phase}          skill   decision:post-test
 milestone-audit    maestro-milestone-audit       skill   —
 milestone-complete maestro-milestone-complete    skill   decision:post-milestone
@@ -247,11 +247,11 @@ milestone-complete maestro-milestone-complete    skill   decision:post-milestone
   { "index": 1, "type": "cli",  "skill": "maestro-execute", "args": "{phase}" },
   { "index": 2, "type": "skill", "skill": "maestro-verify", "args": "{phase}" },
   { "index": 3, "type": "decision", "skill": "maestro-ralph", "args": "{\"decision\":\"post-verify\",\"retry_count\":0,\"max_retries\":2}" },
-  { "index": 4, "type": "skill", "skill": "quality-business-test", "args": "{phase}" },
+  { "index": 4, "type": "skill", "skill": "quality-auto-test", "args": "{phase}" },
   { "index": 5, "type": "decision", "skill": "maestro-ralph", "args": "{\"decision\":\"post-business-test\",\"retry_count\":0,\"max_retries\":2}" },
   { "index": 6, "type": "skill", "skill": "quality-review", "args": "{phase}" },
   { "index": 7, "type": "decision", "skill": "maestro-ralph", "args": "{\"decision\":\"post-review\",\"retry_count\":0,\"max_retries\":2}" },
-  { "index": 8, "type": "skill", "skill": "quality-test-gen", "args": "{phase}" },
+  { "index": 8, "type": "skill", "skill": "quality-auto-test", "args": "{phase}" },
   { "index": 9, "type": "skill", "skill": "quality-test", "args": "{phase}" },
   { "index": 10, "type": "decision", "skill": "maestro-ralph", "args": "{\"decision\":\"post-test\",\"retry_count\":0,\"max_retries\":2}" },
   { "index": 11, "type": "skill", "skill": "maestro-milestone-audit", "args": "" },
@@ -313,11 +313,11 @@ Write status.json:
   [ ] 1. maestro-execute 1               [cli]
   [ ] 2. maestro-verify 1                [skill]
   [ ] 3. ◆ post-verify                   [decision]
-  [ ] 4. quality-business-test 1         [skill]
+  [ ] 4. quality-auto-test 1              [skill]
   [ ] 5. ◆ post-business-test            [decision]
   [ ] 6. quality-review 1                [skill]
   [ ] 7. ◆ post-review                   [decision]
-  [ ] 8. quality-test-gen 1              [skill]
+  [ ] 8. quality-auto-test 1              [skill]
   [ ] 9. quality-test 1                  [skill]
   [ ] 10. ◆ post-test                    [decision]
   [ ] 11. maestro-milestone-audit        [skill]
@@ -400,7 +400,7 @@ If failures found:
     → Insert: [quality-debug --from-business-test {phase},
                maestro-plan --gaps {phase}, maestro-execute {phase} [cli],
                maestro-verify {phase}, decision:post-verify {retry:0},
-               quality-business-test {phase}, decision:post-business-test {retry+1}]
+               quality-auto-test {phase}, decision:post-business-test {retry+1}]
 
 If all pass:
   → No insertion, proceed
@@ -435,9 +435,9 @@ If failures found (any test result != pass, or gaps with severity >= high):
     → Insert: [quality-debug --from-uat {phase},
                maestro-plan --gaps {phase}, maestro-execute {phase} [cli],
                maestro-verify {phase}, decision:post-verify {retry:0},
-               quality-business-test {phase}, decision:post-business-test {retry:0},
+               quality-auto-test {phase}, decision:post-business-test {retry:0},
                quality-review {phase}, decision:post-review {retry:0},
-               quality-test-gen {phase}, quality-test {phase},
+               quality-auto-test {phase}, quality-test {phase},
                decision:post-test {retry+1}]
 
 If all pass:
@@ -462,11 +462,11 @@ If next milestone found:
      maestro-execute {first_phase} [cli],
      maestro-verify {first_phase} [skill],
      decision:post-verify {retry:0},
-     quality-business-test {first_phase} [skill],
+     quality-auto-test {first_phase} [skill],
      decision:post-business-test {retry:0},
      quality-review {first_phase} [skill],
      decision:post-review {retry:0},
-     quality-test-gen {first_phase} [skill],
+     quality-auto-test {first_phase} [skill],
      quality-test {first_phase} [skill],
      decision:post-test {retry:0},
      maestro-milestone-audit [skill],

package/.claude/commands/maestro-verify.md

@@ -61,7 +61,7 @@ If user confirms, invoke `Skill({ skill: "spec-add", args: "<category> <content>
 **Next-step routing on completion:**
 - All checks pass, no gaps → /quality-review
 - Gaps found (must-have failures or anti-pattern blockers) → /maestro-plan --gaps
-- Low test coverage (Nyquist gaps) → /quality-test-gen
+- Low test coverage (Nyquist gaps) → /quality-auto-test
 
 **Gap-fix closure loop:**
 Gaps found → maestro-plan --gaps → maestro-execute → maestro-verify (re-run)

package/.claude/commands/maestro.md

@@ -72,10 +72,9 @@ When `-y` is active, maestro propagates auto flags to downstream commands. Only
 | maestro-plan | `-y` | Skip confirmations and clarification |
 | maestro-execute | `-y` | Skip confirmations, blocked auto-continue |
 | maestro-verify | *(none)* | No interactive prompts |
-| quality-business-test | `-y` | Skip plan confirmation |
+| quality-auto-test | `-y` | Skip plan confirmation |
 | quality-review | *(none)* | No interactive prompts, auto-detects level |
 | quality-test | `-y --auto-fix` | Auto-trigger gap-fix loop on failures |
-| quality-test-gen | *(none)* | No interactive prompts |
 | quality-debug | *(none)* | No interactive prompts |
 | quality-retrospective | `-y` | Accept all routing recommendations without prompting |
 | maestro-milestone-audit | *(none)* | No interactive prompts |

package/.claude/commands/quality-auto-test.md

@@ -0,0 +1,124 @@
+---
+name: quality-auto-test
+description: Unified automated testing via CSV layer pipeline — generates, executes, and iterates tests from PRD specs, coverage gaps, or code exploration
+argument-hint: "<phase> [-y] [-c N] [--max-iter <N>] [--layer <L0-L3>] [--strategy <name>] [--dry-run] [--re-run]"
+allowed-tools:
+  - spawn_agents_on_csv
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+---
+<purpose>
+Run unified automated testing via CSV layer pipeline. Reads project state to auto-select the optimal scenario source — PRD specs (when spec package exists), coverage gaps (when Nyquist audit found gaps), or code exploration (default). All sources converge into a CSV pipeline: discover infrastructure → plan → build scenarios.csv → write tests per layer (spawn_agents_on_csv parallel) → execute → diagnose failures (spawn_agents_on_csv parallel) → iterate → report.
+
+Key mechanisms:
+- **Intelligent routing**: Reads `.tests/`, `.workflow/.spec/`, `verification.json` to auto-select source — no mode flag needed
+- **CSV parallel test writing**: Per-layer `spawn_agents_on_csv` — each agent writes one test file independently
+- **CSV parallel failure diagnosis**: Failed scenarios dispatched via `spawn_agents_on_csv` for classification + fix
+- **Unified iteration engine**: Nested inner loop (fix test_defects via diagnosis CSV, max 3/layer) + outer loop (adaptive strategy, max N iterations)
+- **Layers as waves**: L0→L1→L2→L3 sequential (fail-fast on critical), scenarios within layer parallel
+- **Discovery board**: `discoveries.ndjson` shared across all agents/iterations (append-only)
+- **Degenerate modes**: `--max-iter 1` = single-pass generation; default = full iterative cycle
+- **Session persistence**: CSV state + state.json survive context resets, resume from any point
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/auto-test.md
+</required_reading>
+
+<context>
+Phase or task: $ARGUMENTS (required — phase number)
+
+**Flags:**
+- `--max-iter N` — Maximum outer iterations (default: 5). Set to 1 for single-pass generation only.
+- `--layer L` — Start from or restrict to specific layer (L0|L1|L2|L3)
+- `--dry-run` — Generate test plan only, do not execute
+- `--re-run` — Re-run only previously failed/blocked scenarios
+
+**Intelligent routing** (auto-detected from project state):
+
+| Priority | Condition | Route | Equivalent to |
+|----------|-----------|-------|---------------|
+| 1 | Active session exists (state.json status=running) | Resume | — |
+| 2 | --re-run flag + previous failures | Re-run | — |
+| 3 | Spec package exists (REQ-*.md) | spec | quality-business-test |
+| 4 | Nyquist gaps exist (verification.json) | gap | quality-test-gen |
+| 5 | Default | code | quality-integration-test |
+
+Flags, artifact context resolution, and output formats defined in workflow auto-test.md.
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/auto-test.md' completely.
+
+**Command-specific extensions (not in workflow):**
+
+**Review findings integration** (from related review artifacts):
+- Extract critical/high findings as additional test scenarios, marked `source: "review_finding"`
+- When review verdict is "BLOCK" and review-finding tests fail, suggest quality-debug
+
+**Debug root cause integration** (from related debug artifacts):
+- Generate regression test scenarios from confirmed root causes, marked `source: "debug_root_cause"`
+
+**Register artifact on completion:**
+```
+Append to state.json.artifacts[]:
+{
+  id: nextArtifactId(artifacts, "test"),  // TST-001
+  type: "test",
+  milestone: current_milestone,
+  phase: target_phase,
+  scope: "phase",
+  path: "scratch/{YYYYMMDD}-auto-test-P{N}-{slug}",
+  status: issues == 0 ? "completed" : "failed",
+  depends_on: exec_art.id,
+  harvested: false,
+  created_at: start_time,
+  completed_at: now()
+}
+```
+
+**Next-step routing on completion:**
+- Converged (>=95%) → `/maestro-verify {phase}`
+- All requirements verified (spec source) → `/maestro-milestone-audit`
+- Bugs discovered → `/quality-debug --from-auto-test {phase}`
+- Max iter, >80% → `/quality-test {phase}` for manual UAT
+- Max iter, <80% → `/quality-debug {phase}`
+- Coverage still low → `/quality-auto-test {phase} --layer {missing}`
+- Re-run all pass → `/maestro-verify {phase}`
+- Single pass, all pass → `/quality-test {phase}`
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Phase argument required (no active sessions) | Prompt user for phase number |
+| E002 | error | Phase not found in artifact registry | Check state.json artifacts |
+| E003 | error | No test framework detected | Install test framework or configure test runner |
+| W001 | warning | One or more test scenarios failed | Auto-iterate or suggest fix options |
+| W002 | warning | Max iterations reached without convergence | Review reflection-log.md, suggest debug |
+| W003 | warning | Degraded spec mode (no full spec package) | Consider running maestro-roadmap --mode full |
+</error_codes>
+
+<success_criteria>
+- [ ] Phase resolved from artifact registry
+- [ ] Route auto-selected from project state (spec/gap/code)
+- [ ] Active sessions checked, resume offered if applicable
+- [ ] Scenarios extracted and normalized to unified format
+- [ ] Test infrastructure discovered (framework, patterns, conventions)
+- [ ] test-plan.json generated with layer distribution
+- [ ] User confirmed plan (or --dry-run stopped here)
+- [ ] Tests written following RED-GREEN methodology and existing patterns
+- [ ] Tests executed progressively (L0→L3) with fail-fast on critical
+- [ ] Iteration engine ran (inner: test_defect fix, outer: strategy adjust)
+- [ ] state.json, report.json, reflection-log.md written
+- [ ] index.json updated with auto_test section
+- [ ] If spec source: traceability matrix built, traceability.md written
+- [ ] If failures: issues auto-created in issues.jsonl
+- [ ] If gap source: validation.json gaps updated (MISSING→COVERED)
+- [ ] Next step routed based on convergence status
+</success_criteria>

package/.claude/commands/quality-refactor.md

@@ -35,7 +35,7 @@ Follow '~/.maestro/workflows/refactor.md' completely.
 **Next-step routing on completion:**
 - All tests pass → `/quality-sync` (update codebase docs)
 - Test failures after refactor → `/quality-debug {scope}`
-- No test suite available → `/quality-test-gen {phase}`
+- No test suite available → `/quality-auto-test {phase}`
 </execution>
 
 <error_codes>

package/.claude/commands/quality-test.md

@@ -70,8 +70,8 @@ Append to state.json.artifacts[]:
 - Issues found, --auto-fix ran and succeeded → `/maestro-verify {phase}`
 - Issues found, --auto-fix ran but gaps remain → `/quality-debug --from-uat {phase}`
 - Issues found, manual fix needed → `/quality-debug --from-uat {phase}`
-- Coverage below threshold → `/quality-test-gen {phase}`
-- Need integration tests → `/quality-integration-test {phase}`
+- Coverage below threshold → `/quality-auto-test {phase}`
+- Need integration tests → `/quality-auto-test {phase}`
 </execution>
 
 <error_codes>
@@ -81,7 +81,7 @@ Append to state.json.artifacts[]:
 | E002 | error | Phase not verified yet (no verification.json) | Suggest `/maestro-verify` first |
 | E003 | error | Smoke test failed (app won't start) | Suggest `/quality-debug` |
 | W001 | warning | One or more test scenarios failed | Auto-diagnose, suggest fix options |
-| W002 | warning | Coverage below threshold | Suggest `/quality-test-gen` |
+| W002 | warning | Coverage below threshold | Suggest `/quality-auto-test` |
 </error_codes>
 
 <success_criteria>

package/.codex/skills/learn-retro/SKILL.md

@@ -60,7 +60,7 @@ Write `retro-{date}.md` + `retro-{date}.json` with metrics, sessions, hotspots,
 ### Phase 5: Persist
 Append insights to `lessons.jsonl` (source: "retro-git" or "retro-decision"). Display summary.
 
-**Next steps:** `/learn-follow <path>`, `/quality-test-gen <area>`, `/learn-investigate <question>`
+**Next steps:** `/learn-follow <path>`, `/quality-auto-test <area>`, `/learn-investigate <question>`
 </execution>
 
 <error_codes>

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

@@ -201,7 +201,7 @@ functions.update_plan({
 |-------|------|
 | `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-auto-test`, `quality-retrospective` | `-y` |
 | `quality-test` | `-y --auto-fix` |
 
 **`buildSkillCall(step, ctx)`**: Replace placeholders `{phase}`, `{description}`, `{issue_id}`, `{plan_dir}`, `{analysis_dir}`, `{brainstorm_dir}`, `{spec_session_id}` in `step.args` with corresponding `ctx` values. Append auto-yes flag if applicable. Return `$<skill> <args>`.

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

@@ -152,7 +152,7 @@ Set `state.status` to completed/failed based on `node.status`. Record final hist
 |-------|------|
 | `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-auto-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-audit/SKILL.md

@@ -54,7 +54,15 @@ Spawn Agent for cross-phase validation: shared interfaces, dependency chains, da
 **PASS**: All phases have completed EXC artifacts, no critical integration gaps, all adhoc completed.
 **FAIL**: Missing EXC artifacts or critical integration gaps found.
 
-Display structured audit report with next-step routing.
+Display structured audit report.
+
+**Next-step routing:**
+
+| Verdict | Next Step |
+|---------|-----------|
+| PASS | `$maestro-milestone-complete "{milestone}"` |
+| FAIL, integration gaps | `$maestro-plan "--gaps"` |
+| FAIL, incomplete execution | `$maestro-execute` |
 
 </execution>
 

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

@@ -209,6 +209,40 @@ Each wave generates `wave-{N}.csv` with extra `prev_context` column.
 
 **User validation**: Display exploration breakdown (skip if AUTO_YES or `--auto`).
 
+### Pre-flight: Team Conflict Check
+
+Before starting the plan pipeline:
+```
+Bash("maestro collab preflight --phase <phase-number>")
+```
+If exit code is 1, present warnings and ask whether to proceed.
+
+### Wiki Knowledge Search
+
+During context collection, after loading files and before exploration (Wave 1):
+```
+phase_keywords = extract key terms from goal/title (2-5 terms)
+wiki_result = Bash("maestro wiki search ${phase_keywords} --json 2>/dev/null")
+
+IF wiki_result exit code != 0 OR empty:
+  W003: Wiki search unavailable, continue without prior knowledge
+ELSE:
+  entries = JSON.parse(wiki_result).entries (limit to first 10)
+  Pass wiki_context to Wave 2 planning agent
+```
+
+### Mode Routing
+
+| Mode | Trigger | Behavior |
+|------|---------|----------|
+| Create | Default (no --revise/--check) | Full pipeline: Phase 1 → Wave 1 → Wave 2 → Phase 3 |
+| Revise | `--revise [instructions]` | Load existing plan, apply incremental edits, re-check |
+| Check | `--check <plan-dir>` | Skip exploration/planning, run plan-checker only on existing plan |
+
+**Revise mode**: Load plan.json from target dir, apply user instructions (add/remove/edit tasks, adjust waves), re-run plan-checker, update index.json.
+
+**Check mode**: Read plan.json + .task/TASK-*.json from `--check` path, validate quality, report issues. No exploration, no generation.
+
 ### Phase 2: Wave Execution Engine
 
 **Objective**: Explore codebase then generate plan via spawn_agents_on_csv.
@@ -321,14 +355,38 @@ spawn_agents_on_csv({
    - Export `results.csv` from master `tasks.csv`
    - Generate `context.md`: summary (phase, task count, wave count, complexity, exploration count), exploration findings per angle, plan overview (approach, task IDs, waves), next steps
 
-4. **Update index.json**: set `status: "planning"`, `plan: { task_ids, task_count, complexity, waves }`, `updated_at`
+4. **Collision detection**: Scan same-milestone plans for overlapping file targets:
+   ```
+   other_plans = state.json.artifacts.filter(a => a.milestone == current && a.type == "plan" && a.id != this)
+   For each other_plan: read .task/TASK-*.json, collect files[].path
+   collisions = intersection(this_plan_files, other_plan_files)
+   If collisions.length > 0: emit W004, display collision table (non-blocking)
+   ```
+
+5. **Update index.json**: set `status: "planning"`, `plan: { task_ids, task_count, complexity, waves }`, `updated_at`
 
-5. **Issue linking** (if --gaps):
+6. **Register PLN artifact** in state.json:
+   ```json
+   { "id": "PLN-NNN", "type": "plan", "milestone": "current", "phase": "target_phase",
+     "scope": "phase", "path": "scratch/{YYYYMMDD}-plan-P{N}-{slug}",
+     "status": "completed", "depends_on": "anl_art.id || exec_art.id" }
+   ```
+
+7. **Issue linking** (if --gaps):
    For each TASK with `issue_id`: update issue in `issues.jsonl` (`task_refs` += TASK-NNN, `task_plan_dir`, `status: "planned"`, `updated_at`) + append history entry. Ensures bidirectional issue-TASK traceability.
 
-6. **Display summary + options** (skip options if AUTO_YES):
-   Show phase name, task/wave counts, checker status, output file paths.
-   Next steps: `maestro-execute "{phase}"` (execute) or `maestro-plan "{phase}"` (re-plan).
+8. **Display summary + options** (skip options if AUTO_YES):
+   ```
+   === PLAN READY ===
+   Phase: {phase_name}
+   Tasks: {task_count} tasks in {wave_count} waves
+   Check: {checker_status} (iteration {check_count}/{max_checks})
+   Collision: {collision_status}
+
+   Next steps:
+     $maestro-execute "{phase}"     -- Execute the plan
+     $maestro-plan "{phase}"        -- Re-plan with modifications
+   ```
 
 ### Shared Discovery Board Protocol
 
@@ -371,7 +429,11 @@ echo '{"ts":"<ISO>","worker":"{id}","type":"existing_pattern","data":{"name":"Re
 | Phase argument required | Abort with error: "Phase argument required" |
 | Phase directory not found | Abort with error: "Phase {N} not found. Run init first." |
 | --gaps requires gaps source | Abort with error: "--gaps requires issues.jsonl, verification.json, or uat.md" |
+| No plan found to revise (--revise) | Use --dir to specify plan, or create plan first |
+| Plan directory not found (--check) | Check path, use --dir |
 | No context.md found | Warn, proceed with exploration only |
+| Wiki search unavailable (W003) | Continue without prior knowledge context |
+| Collision detected (W004) | Review colliding files, confirm or adjust scope |
 | Exploration agent timeout | Mark as failed, continue with available explorations |
 | Planning agent fails | Retry once with simplified context, then abort |
 | Plan produces invalid JSON | Retry once, then abort with error details |
@@ -387,8 +449,12 @@ echo '{"ts":"<ISO>","worker":"{id}","type":"existing_pattern","data":{"name":"Re
 - [ ] plan.json produced in phase directory
 - [ ] .task/TASK-*.json files produced for all tasks
 - [ ] Plan passes quality checks (coverage, deps, criteria)
+- [ ] Collision detection executed against same-milestone plans
+- [ ] PLN artifact registered in state.json
 - [ ] context.md produced with exploration findings + plan overview
 - [ ] index.json updated with plan metadata
-- [ ] Issues linked (if --gaps mode)
+- [ ] Issues linked bidirectionally (if --gaps mode)
+- [ ] Wiki knowledge integrated (if available)
+- [ ] Team conflict preflight checked
 - [ ] discoveries.ndjson append-only throughout
 </success_criteria>