maestro-flow 0.3.10 → 0.3.12

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

@@ -1,111 +1,133 @@
----
-name: maestro-fork
-description: Create a worktree for milestone-level parallel development, or sync existing worktree with main
-argument-hint: "-m <milestone-number> [--base <branch>] [--sync]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Create a git worktree for an entire milestone, enabling inter-milestone parallel development. All phases within the milestone are owned by the worktree and executed sequentially inside it.
-
-Since `.workflow/` is gitignored, this command explicitly copies project context and all milestone phase directories into the worktree. Per-phase parallelism within a milestone is NOT supported.
-
-Also supports `--sync` mode to pull latest main branch changes and shared artifacts into an active worktree (prevents source and artifact drift for long-lived worktrees).
-
-Produces `.workflow/worktrees.json` registry in the main worktree and `.workflow/worktree-scope.json` marker in the worktree.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/fork.md
-</required_reading>
-
-<deferred_reading>
-- [worktrees.json](~/.maestro/templates/worktrees.json) — read when updating registry
-- [worktree-scope.json](~/.maestro/templates/worktree-scope.json) — read when writing scope marker
-</deferred_reading>
-
-<context>
-$ARGUMENTS -- milestone name and optional flags.
-
-**Modes:**
-
-| Mode | Trigger | Behavior |
-|------|---------|----------|
-| Fork | `-m 2` or `2` | Create worktree for all phases in milestone 2 |
-| Sync | `-m 2 --sync` | Sync existing milestone 2 worktree with main branch |
-
-**Flags:**
-- `-m <N>` or bare `<N>`: Milestone number (1-based, maps to `state.json.milestones[]`)
-- `--base <branch>`: Override base branch for worktree creation (default: HEAD)
-- `--sync`: Sync mode — pull main into existing worktree, re-copy shared artifacts
-
-**Milestone resolution:** `state.json.milestones[N-1]` → `{name, title, phases: [...]}`
-
-**Worktree layout:**
-```
-.worktrees/m{N}-{slug}/
-├── .workflow/
-│   ├── worktree-scope.json     (scope marker — lists all owned phases)
-│   ├── state.json              (scoped to this milestone)
-│   ├── project.md              (read-only copy)
-│   ├── roadmap.md              (read-only copy)
-│   ├── config.json             (read-only copy)
-│   ├── specs/                  (read-only copy)
-│   └── phases/
-│       ├── {NN}-{slug}/        (owned — all phases in milestone)
-│       └── {dep}-{dep-slug}/   (read-only dependency reference from prior milestones)
-└── <source code>               (git worktree checkout)
-```
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/fork.md' completely.
-
-**Next-step routing on completion:**
-
-Fork mode:
-- Enter worktree → `cd {wt.path} && /maestro-analyze {first_phase}`
-- Automated → `maestro delegate "run full lifecycle for milestone" --cd {wt.path} --mode write`
-- Status → Skill({ skill: "manage-status" })
-
-Sync mode:
-- Sync complete → resume work in worktree
-- Conflicts found → resolve manually, then retry
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Project not initialized | Run maestro-init first |
-| E002 | error | No roadmap found | Run maestro-roadmap first |
-| E003 | error | Running inside a worktree | Run from main worktree |
-| E004 | error | No milestone number provided | Provide `-m <N>` |
-| E005 | error | No milestones defined in state.json | Run maestro-roadmap first |
-| E006 | error | Milestone number out of range | Check available milestones |
-| E007 | error | No active worktree for milestone (--sync) | Check worktrees.json |
-| E008 | error | Milestone already has active worktree | Merge or cleanup first |
-</error_codes>
-
-<success_criteria>
-Fork mode:
-- [ ] Milestone phases identified from roadmap
-- [ ] Git worktree created with branch (`milestone/{slug}`)
-- [ ] `.workflow/` context copied into worktree (all milestone phases + dependency phases)
-- [ ] `worktree-scope.json` written with all owned phase numbers
-- [ ] Scoped `state.json` written (current_phase = first pending phase)
-- [ ] `worktrees.json` registry updated in main worktree
-- [ ] Milestone phase indexes marked as "forked" in main worktree
-- [ ] Summary displayed with next-step commands
-
-Sync mode:
-- [ ] Git merge main into worktree branch
-- [ ] Shared artifacts re-copied (project.md, roadmap.md, config.json, specs/)
-- [ ] Conflicts reported if any
-</success_criteria>
+---
+name: maestro-fork
+description: Create a worktree for milestone-level parallel development, or sync existing worktree with main
+argument-hint: "-m <milestone-number> [--base <branch>] [--sync]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Create a git worktree for an entire milestone, enabling inter-milestone parallel development. The worktree scope is milestone-level — all scratch artifacts for that milestone are owned by the worktree.
+
+Since `.workflow/` is gitignored, this command explicitly copies project context and existing milestone scratch artifacts into the worktree. Per-phase parallelism within a milestone is NOT supported.
+
+Also supports `--sync` mode to pull latest main branch changes and shared artifacts into an active worktree (prevents source and artifact drift for long-lived worktrees).
+
+Produces `.workflow/worktrees.json` registry in the main worktree and `.workflow/worktree-scope.json` marker in the worktree.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/fork.md
+</required_reading>
+
+<deferred_reading>
+- [worktrees.json](~/.maestro/templates/worktrees.json) — read when updating registry
+- [worktree-scope.json](~/.maestro/templates/worktree-scope.json) — read when writing scope marker
+</deferred_reading>
+
+<context>
+$ARGUMENTS -- milestone name and optional flags.
+
+**Modes:**
+
+| Mode | Trigger | Behavior |
+|------|---------|----------|
+| Fork | `-m 2` or `2` | Create worktree for milestone 2 |
+| Sync | `-m 2 --sync` | Sync existing milestone 2 worktree with main branch |
+
+**Flags:**
+- `-m <N>` or bare `<N>`: Milestone number (1-based, maps to `state.json.milestones[]`)
+- `--base <branch>`: Override base branch for worktree creation (default: HEAD)
+- `--sync`: Sync mode — pull main into existing worktree, re-copy shared artifacts
+
+**Milestone resolution:** `state.json.milestones[N-1]` → `{id, name, status}`
+
+**Worktree layout:**
+```
+.worktrees/m{N}-{slug}/
+├── .workflow/
+│   ├── worktree-scope.json     (milestone scope marker)
+│   ├── state.json              (scoped — only this milestone's artifacts)
+│   ├── project.md              (read-only copy)
+│   ├── roadmap.md              (read-only copy)
+│   ├── config.json             (read-only copy)
+│   ├── specs/                  (read-only copy)
+│   └── scratch/                (milestone's existing + new artifacts)
+│       ├── analyze-auth-2026-04-20/
+│       ├── plan-auth-2026-04-20/
+│       └── ...
+└── <source code>               (git worktree checkout)
+```
+
+**Artifact scoping:**
+Fork copies scratch artifacts that belong to the target milestone (filtered from `state.json.artifacts[]` where `milestone == target`). New work in the worktree creates scratch artifacts normally; they are registered in the worktree's local `state.json`.
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/fork.md' completely.
+
+**Fork flow:**
+1. Validate: project initialized, roadmap exists, not inside worktree, milestone not already forked
+2. Resolve milestone: `state.json.milestones[N-1]`
+3. Create git worktree: `git worktree add -b milestone/{slug} .worktrees/m{N}-{slug} HEAD`
+4. Copy `.workflow/` into worktree:
+   - Shared files (read-only): `project.md`, `roadmap.md`, `config.json`, `specs/`
+   - Milestone scratch artifacts: filter `state.json.artifacts[]` by `milestone == target`, copy each `scratch/{path}`
+5. Write scope marker: `worktree-scope.json` with milestone number and main path
+6. Write scoped `state.json`: only this milestone's artifacts, `current_milestone` set
+7. Update main: `worktrees.json` registry, mark milestone as `"forked"` in `state.json.milestones[]`
+
+**Sync flow:**
+1. Find worktree from `worktrees.json`
+2. `cd worktree && git merge main`
+3. Re-copy shared files: `project.md`, `roadmap.md`, `config.json`, `specs/`
+4. Report conflicts if any
+
+**Next-step routing on completion:**
+
+Fork mode:
+- Enter worktree → `cd {wt.path} && /maestro-analyze`
+- Automated → `maestro delegate "run full lifecycle for milestone" --cd {wt.path} --mode write`
+- Status → Skill({ skill: "manage-status" })
+
+Sync mode:
+- Sync complete → resume work in worktree
+- Conflicts found → resolve manually, then retry
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Project not initialized | Run maestro-init first |
+| E002 | error | No roadmap found | Run maestro-roadmap first |
+| E003 | error | Running inside a worktree | Run from main worktree |
+| E004 | error | No milestone number provided | Provide `-m <N>` |
+| E005 | error | No milestones defined in state.json | Run maestro-roadmap first |
+| E006 | error | Milestone number out of range | Check available milestones |
+| E007 | error | No active worktree for milestone (--sync) | Check worktrees.json |
+| E008 | error | Milestone already has active worktree | Merge or cleanup first |
+</error_codes>
+
+<success_criteria>
+Fork mode:
+- [ ] Milestone resolved from state.json.milestones[]
+- [ ] Git worktree created with branch (`milestone/{slug}`)
+- [ ] Shared `.workflow/` files copied (project.md, roadmap.md, config.json, specs/)
+- [ ] Milestone scratch artifacts copied (filtered from artifact registry)
+- [ ] `worktree-scope.json` written with milestone scope
+- [ ] Scoped `state.json` written (only this milestone's artifacts)
+- [ ] `worktrees.json` registry updated in main worktree
+- [ ] Milestone marked as `"forked"` in main `state.json.milestones[]`
+- [ ] Summary displayed with next-step commands
+
+Sync mode:
+- [ ] Git merge main into worktree branch
+- [ ] Shared artifacts re-copied (project.md, roadmap.md, config.json, specs/)
+- [ ] Conflicts reported if any
+</success_criteria>

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

@@ -1,77 +1,85 @@
----
-name: maestro-merge
-description: Two-phase merge of milestone worktree branch back — git merge first, artifact sync only on success
-argument-hint: "-m <milestone-number> [--force] [--dry-run] [--no-cleanup] [--continue]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Merge a completed milestone worktree branch back into the main branch, sync workflow artifacts for all phases, and reconcile project state. Uses a two-phase approach: git merge first (source code), artifact sync second (only after git succeeds). This prevents partial state corruption when merge conflicts occur.
-
-Includes registry health check, pre-merge rebase (pull main into worktree to minimize conflicts), and atomic state reconciliation (patch, don't overwrite).
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/merge.md
-</required_reading>
-
-<context>
-$ARGUMENTS -- milestone name and optional flags.
-
-**Flags:**
-- `-m <N>` or bare `<N>`: Milestone number (1-based, maps to registry)
-- `--force`: Merge even if not all phases are completed
-- `--dry-run`: Show what would be merged without executing
-- `--no-cleanup`: Keep worktree and branch after merge (for inspection)
-- `--continue`: Resume a merge that was paused due to git conflict
-
-**Merge sequence:**
-1. Registry health check (remove stale entries)
-2. Validate phase readiness across all owned phases
-3. Pre-merge rebase (`git merge main` in worktree)
-4. Phase 1: Git merge (source code only)
-5. Phase 2: Artifact sync (only after git merge succeeds)
-6. Atomic state reconciliation
-7. Cleanup (worktree remove + branch delete)
-
-**Conflict handling:**
-If git merge fails, the command saves state to `.workflow/.merge-state.json` and exits. User resolves conflicts, then runs `maestro-merge --continue` to resume artifact sync.
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/merge.md' completely.
-
-**Next-step routing on completion:**
-- View dashboard → Skill({ skill: "manage-status" })
-- Audit milestone → Skill({ skill: "maestro-milestone-audit" })
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Running inside a worktree | Run from main worktree |
-| E002 | error | No worktree registry found | Nothing to merge |
-| E003 | error | --continue but no merge state | Start fresh merge |
-| E004 | error | No milestone number provided | Provide `-m <N>` |
-| W001 | warning | Stale registry entries found | Auto-cleaned |
-| W002 | warning | Incomplete phases (without --force) | Confirm or use --force |
-| W003 | warning | Conflict pulling main into worktree | Resolve in worktree first |
-</error_codes>
-
-<success_criteria>
-- [ ] Registry health check passed (stale entries cleaned)
-- [ ] Pre-merge rebase successful (worktree has latest main)
-- [ ] Git merge completed without conflicts (or conflicts resolved via --continue)
-- [ ] All owned phase artifacts synced to main `.workflow/phases/`
-- [ ] `state.json` reconciled (phases_summary, accumulated_context, transition_history patched)
-- [ ] `roadmap.md` completed phases marked
-- [ ] Worktree removed and branch deleted (unless --no-cleanup)
-- [ ] Registry updated (entry removed)
-</success_criteria>
+---
+name: maestro-merge
+description: Two-phase merge of milestone worktree branch back — git merge first, scratch artifact sync only on success
+argument-hint: "-m <milestone-number> [--force] [--dry-run] [--no-cleanup] [--continue]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Merge a completed milestone worktree branch back into the main branch, sync scratch artifacts, and reconcile the artifact registry. Uses a two-phase approach: git merge first (source code), artifact sync second (only after git succeeds). This prevents partial state corruption when merge conflicts occur.
+
+Includes registry health check, pre-merge rebase (pull main into worktree to minimize conflicts), and atomic state reconciliation (merge artifact entries, don't overwrite).
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/merge.md
+</required_reading>
+
+<context>
+$ARGUMENTS -- milestone name and optional flags.
+
+**Flags:**
+- `-m <N>` or bare `<N>`: Milestone number (1-based, maps to registry)
+- `--force`: Merge even if milestone has incomplete artifacts
+- `--dry-run`: Show what would be merged without executing
+- `--no-cleanup`: Keep worktree and branch after merge (for inspection)
+- `--continue`: Resume a merge that was paused due to git conflict
+
+**Merge sequence:**
+1. Registry health check (remove stale worktree entries)
+2. Validate milestone artifact completeness (all EXC artifacts completed)
+3. Pre-merge rebase (`git merge main` in worktree)
+4. Phase 1: Git merge (source code only)
+5. Phase 2: Scratch artifact sync (only after git merge succeeds)
+6. Atomic artifact registry reconciliation
+7. Cleanup (worktree remove + branch delete)
+
+**Phase 2 — Artifact sync detail:**
+- Copy worktree `scratch/*` dirs back to main `.workflow/scratch/`
+- Merge worktree `state.json.artifacts[]` entries into main `state.json.artifacts[]`
+  - Dedup by artifact id; worktree version wins for same id
+- Update milestone status in main `state.json.milestones[]` (remove "forked" flag)
+- Mark `harvested` status from worktree artifacts
+
+**Conflict handling:**
+If git merge fails, the command saves state to `.workflow/.merge-state.json` and exits. User resolves conflicts, then runs `maestro-merge --continue` to resume artifact sync.
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/merge.md' completely.
+
+**Next-step routing on completion:**
+- View dashboard → Skill({ skill: "manage-status" })
+- Audit milestone → Skill({ skill: "maestro-milestone-audit" })
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Running inside a worktree | Run from main worktree |
+| E002 | error | No worktree registry found | Nothing to merge |
+| E003 | error | --continue but no merge state | Start fresh merge |
+| E004 | error | No milestone number provided | Provide `-m <N>` |
+| W001 | warning | Stale registry entries found | Auto-cleaned |
+| W002 | warning | Incomplete artifacts (without --force) | Confirm or use --force |
+| W003 | warning | Conflict pulling main into worktree | Resolve in worktree first |
+</error_codes>
+
+<success_criteria>
+- [ ] Registry health check passed (stale entries cleaned)
+- [ ] Pre-merge rebase successful (worktree has latest main)
+- [ ] Git merge completed without conflicts (or conflicts resolved via --continue)
+- [ ] All scratch artifacts synced to main `.workflow/scratch/`
+- [ ] `state.json.artifacts[]` reconciled (worktree entries merged into main)
+- [ ] Milestone `"forked"` flag removed in `state.json.milestones[]`
+- [ ] `roadmap.md` completed phases marked
+- [ ] Worktree removed and branch deleted (unless --no-cleanup)
+- [ ] `worktrees.json` registry updated (entry removed)
+</success_criteria>

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

@@ -1,7 +1,7 @@
 ---
 name: maestro-plan
 description: Explore, clarify, plan, check, and confirm a phase execution plan
-argument-hint: "[phase] [--collab] [--spec SPEC-xxx] [--auto] [--gaps] [--dir <path>]"
+argument-hint: "[phase] [--collab] [--spec SPEC-xxx] [--auto] [--gaps] [--dir <path>] [--revise [instructions]] [--check <plan-dir>]"
 allowed-tools:
   - Read
   - Write
@@ -13,7 +13,12 @@ allowed-tools:
   - AskUserQuestion
 ---
 <purpose>
-Create a verified execution plan (plan.json + .task/TASK-*.json) through a 5-stage pipeline: Exploration, Clarification, Planning, Plan Checking, and Confirmation. Produces plan.json with waves, task definitions, and user-confirmed execution strategy.
+Create, revise, or verify an execution plan through a 5-stage pipeline: Exploration, Clarification, Planning, Plan Checking, and Confirmation. Produces plan.json with waves, task definitions, and user-confirmed execution strategy.
+
+Supports three modes:
+- **Create** (default): Build plan from analysis context or phase requirements
+- **Revise** (`--revise`): Incrementally modify existing plan — edit tasks, adjust waves, add/remove tasks
+- **Check** (`--check`): Standalone plan verification — run plan-checker against existing plan
 
 All plan output goes to `.workflow/scratch/plan-{slug}-{date}/`. Registers PLN artifact in state.json. Performs collision detection against other plans in same milestone.
 </purpose>
@@ -37,6 +42,8 @@ $ARGUMENTS — phase number, or no args for milestone-wide planning, with option
 - `--auto` -- Skip interactive clarification (P2), use defaults
 - `--gaps` -- Gap closure mode: load verification/issue gaps, skip exploration, plan only gap fixes
 - `--dir <path>` -- Use arbitrary scratch directory as context source (e.g., from analyze session)
+- `--revise [instructions]` -- Revise existing plan. Auto-discovers latest plan for current phase from state.json, or use with `--dir` to target specific plan. If instructions provided, apply directly (e.g. `--revise "add TASK-005 for error handling"`). If omitted, ask user via AskUserQuestion. Skips P1-P3 (exploration/clarification/planning), loads existing plan.json + tasks, applies targeted modifications, re-runs P4 (plan-checker).
+- `--check <plan-dir>` -- Standalone plan verification. Run plan-checker (P4 only) against existing plan without modification. Also checks roadmap consistency and collision detection. Read-only.
 
 **Scope routing:**
 
@@ -45,6 +52,9 @@ $ARGUMENTS — phase number, or no args for milestone-wide planning, with option
 | `plan` (no args) | init + roadmap | milestone | Plan all phases in current milestone |
 | `plan 1` | init + roadmap | phase | Plan phase 1 only |
 | `plan --dir scratch/analyze-xxx` | none | inherited | Plan against specified analyze session |
+| `plan --revise "instructions"` | existing plan | revise | Modify existing plan with instructions |
+| `plan --revise` | existing plan | revise | Modify existing plan, ask user for instructions |
+| `plan --check scratch/plan-xxx` | existing plan | check | Verify existing plan (read-only) |
 
 **Upstream context:**
 - Reads `context.md` from prior analyze artifact (auto-discovered from state.json or via --dir)
@@ -141,6 +151,80 @@ Next steps:
   /maestro-execute --dir {dir}  -- Execute specific plan
   /maestro-plan {phase}         -- Re-plan with modifications
 ```
+
+### Mode: Revise (`--revise [instructions]`)
+
+Incrementally modify an existing plan without rebuilding from scratch.
+
+**Plan discovery:**
+- With `--dir`: use specified plan directory
+- Without `--dir`: auto-discover latest completed plan for current phase from `state.json.artifacts[]` (type=plan, status=completed, matching phase)
+
+**Execution flow:**
+
+1. **Load existing plan**
+   - Read `plan.json` + all `.task/TASK-*.json` from discovered directory
+   - Show current plan summary: task count, waves, status per task
+
+2. **Obtain revision instructions**
+   - If `--revise "instructions"` provided → parse as change directive
+   - If `--revise` without instructions → AskUserQuestion for what to change:
+     - Add/remove tasks
+     - Modify task scope, action, implementation
+     - Reorder waves or adjust dependencies
+     - Update convergence criteria
+   - Parse instructions into concrete changes
+
+3. **Apply targeted changes**
+   - Modify affected TASK files in-place
+   - If tasks added/removed: re-sequence task IDs, regenerate wave assignments
+   - Update plan.json summary (task count, wave structure)
+   - Preserve unmodified tasks completely
+
+4. **Re-run plan-checker (P4)**
+   - Validate modified plan with same checker as create mode
+   - Re-run collision detection against same-milestone plans
+   - Present check results for confirmation
+
+5. **Update artifact**
+   - Overwrite plan files in existing scratch directory
+   - Update artifact timestamp in state.json (no new artifact created)
+
+### Mode: Check (`--check <plan-dir>`)
+
+Read-only plan verification without modification.
+
+**Execution flow:**
+
+1. **Load plan**
+   - Read `plan.json` + `.task/TASK-*.json` from specified directory
+   - Read `.workflow/roadmap.md` for consistency comparison
+
+2. **Run checks**
+   - Plan-checker (P4 pipeline stage) — task quality, convergence criteria
+   - Roadmap consistency — plan tasks align with phase scope and requirements
+   - Collision detection — file overlaps with other plans in same milestone
+   - Dependency integrity — no broken cross-task dependencies
+
+3. **Produce check report**
+   ```
+   === PLAN CHECK ===
+   Plan: {plan_dir}/plan.json
+   Tasks: {total} ({completed} done, {pending} pending)
+
+   Checker: {PASS|WARN|FAIL} ({issues} issues)
+   Roadmap: {aligned|drift detected}
+   Collision: {clear|{N} overlaps}
+
+   Issues:
+     1. [{severity}] {description}
+
+   Suggested actions:
+     /maestro-plan --revise "fix instructions"  -- Apply fixes
+     /maestro-execute --dir {plan_dir}          -- Execute as-is
+   ```
+
+**No file modifications.** Pure verification + report.
 </execution>
 
 <error_codes>
@@ -148,6 +232,8 @@ Next steps:
 |------|----------|-----------|----------|
 | E001 | error | No args and no roadmap (cannot determine scope) | Provide phase number or topic, or create roadmap |
 | E003 | error | --gaps requires prior verification/issues to exist | Run maestro-verify first |
+| E004 | error | No plan found to revise (--revise without target) | Use --dir to specify plan, or create plan first |
+| E005 | error | Plan directory not found (--check) | Check path, use --dir |
 | W001 | warning | Exploration agent returned incomplete results | Retry exploration or proceed with available context |
 | W002 | warning | Plan-checker found minor issues, continuing | Review plan-checker feedback, adjust plan if needed |
 | W003 | warning | Wiki search unavailable or returned no results | Continue without prior knowledge context |