mindsystem-cc 4.3.0 → 4.3.1

package/README.md

@@ -2,9 +2,9 @@
 
 # MINDSYSTEM
 
-**The engineer's meta-prompting system for Claude Code.**
+**The full-cycle development system for Claude Code.**
 
-Amplifies every step of the development workflow you already follow — discovery, research, design, planning, execution, verification. Each one refined, parallelized, and compounded into persistent knowledge. Built for engineers who want to multiply their output without giving up control.
+In lean teams and solo ventures, the person writing the code is also the person deciding what to build, researching the domain, picking the layout, and verifying the result. Mindsystem amplifies each of those steps, making them deeper and faster — discovery, research, design, planning, execution, verification — so one person can cover the full cycle without cutting corners. What it learns carries forward, so phase 10 knows everything phase 1 figured out.
 
 ```bash
 npx mindsystem-cc
@@ -27,17 +27,17 @@ npx mindsystem-cc
 
 ## Why Mindsystem
 
-Fully autonomous coding tools take a spec and run for hours until a product emerges. That works for prototypes and one-shot projects.
+Larger organizations split product delivery across specialists — product owners, designers, researchers, QA engineers. Autonomous coding tools try to replace that entire chain with a single prompt. Both approaches lose something: the first requires headcount, the second loses your judgment.
 
-Mindsystem takes the opposite approach. It follows the same workflow a thorough engineer already uses — and amplifies each step:
+Mindsystem is the middle ground. Each specialist role maps to a phase you control:
 
-| What you'd do manually | What Mindsystem does |
-|---|---|
-| Talk through requirements, catch misalignment early | **Discuss phase** surfaces assumptions with confidence levels, forces tradeoff decisions before any code gets written |
-| Google libraries, read a few docs | **Research phase** runs 3 parallel agents across documentation, your codebase, and community practices — 10x more sources, synthesized in minutes |
-| Try design directions, pick the best one | **Design phase** generates parallel HTML/CSS mockups with side-by-side comparison and exact design tokens |
-| Plan from what you remember about the codebase | **Plan phase** loads knowledge files capturing every decision, pattern, and pitfall from prior phases |
-| Figure out what states to test, mock them manually | **Verify work** determines mock states automatically — you validate visually or programmatically |
+| The role | What you'd do | What Mindsystem does |
+|---|---|---|
+| **Product owner** | Talk through requirements, catch misalignment early | **Discuss phase** surfaces assumptions with confidence levels, forces tradeoff decisions before any code gets written |
+| **Technical researcher** | Google libraries, read a few docs | **Research phase** runs 3 parallel agents across documentation, your codebase, and community practices — 10x more sources, synthesized in minutes |
+| **Designer** | Try design directions, pick the best one | **Design phase** generates parallel HTML/CSS mockups with side-by-side comparison and exact design tokens |
+| **Tech lead** | Plan from what you remember about the codebase | **Plan phase** loads knowledge files capturing every decision, pattern, and pitfall from prior phases |
+| **QA engineer** | Figure out what states to test, mock them manually | **Verify work** determines mock states automatically — you validate visually or programmatically |
 
 The workflow stays yours. Each step finishes in minutes instead of hours. Everything learned compounds into knowledge that survives context resets — phase 10 starts with everything the project learned from phases 1–9.
 

package/agents/ms-compounder.md

@@ -2,7 +2,7 @@
 name: ms-compounder
 description: Compounds raw code changes into per-subsystem knowledge files. Spawned by compound workflow.
 model: sonnet
-tools: Read, Write, Bash, Grep, Glob
+tools: Read, Edit, Write, Bash, Grep, Glob
 color: yellow
 ---
 
@@ -71,23 +71,23 @@ Focus on:
 
 ## Step 4: Merge Into Existing Knowledge
 
-For each affected subsystem, merge extracted content into the knowledge file:
+For each affected subsystem, edit the knowledge file to reflect current state:
 
-- **Decisions:** Add new entries, update superseded decisions, remove contradicted ones.
-- **Architecture:** Update structural descriptions with new components and patterns.
-- **Design:** Add new specs, update changed specs.
-- **Pitfalls:** Add new entries, deduplicate with existing.
-- **Key Files:** Add new paths, remove renamed or deleted files.
+- **Decisions:** Append new entries. Edit superseded decisions in place. Delete contradicted ones.
+- **Architecture:** Edit structural descriptions with new components and patterns.
+- **Design:** Append new specs, edit changed specs.
+- **Pitfalls:** Append new entries. Delete duplicates of existing entries.
+- **Key Files:** Append new paths, delete renamed or deleted files.
 
-Rewrite the full file — not append. The result is the current state of knowledge.
+Use `Edit` for existing files — targeted changes preserve content you haven't inspected. Use `Write` only for new files (subsystem has no knowledge file yet).
 
-## Step 5: Write Knowledge Files and Return Report
+## Step 5: Update Knowledge Files and Return Report
 
 ```bash
 mkdir -p .planning/knowledge/
 ```
 
-Write one file per affected subsystem. Follow the template format from `~/.claude/mindsystem/templates/knowledge.md`. Omit sections with no content.
+For new subsystems (no existing file), use `Write` to create the file following the template format from `~/.claude/mindsystem/templates/knowledge.md`. For existing files, all changes should already be applied via `Edit` in step 4. Omit empty sections.
 
 Return a structured report to the compound workflow.
 
@@ -123,11 +123,11 @@ If changes suggest a subsystem not in the confirmed list, note it as a proposal
 
 **Preserve rationale.** The "because" part is the value. Decisions without rationale are just facts.
 
-**Rewrite, not append.** Each update produces the current state. Superseded decisions get updated, not duplicated.
+**Edit to reflect current state.** Update superseded decisions, remove outdated patterns, append new entries. Use `Edit` for existing files, `Write` only for new files.
 
 **Omit empty sections.** If a subsystem has no design work, do not include a Design section.
 
-**No commits.** Write files only — the compound workflow orchestrator handles commits.
+**No commits.** Edit/write files only — the compound workflow orchestrator handles commits.
 
 **Only write files for confirmed affected subsystems.** Do not invent subsystems or write knowledge files for subsystems not in the confirmed list.
 
@@ -136,7 +136,8 @@ If changes suggest a subsystem not in the confirmed list, note it as a proposal
 </critical_rules>
 
 <success_criteria>
-- [ ] Merge uses rewrite semantics (update, remove, deduplicate — not just add)
+- [ ] Existing files modified via Edit (not Write) — targeted changes, no full-file replacement
+- [ ] Merge reflects current state (update, remove, deduplicate — not just append)
 - [ ] No commits made
 - [ ] Report returned with update counts
 - [ ] Empty sections omitted from knowledge files

package/agents/ms-consolidator.md

@@ -2,7 +2,7 @@
 name: ms-consolidator
 description: Consolidates phase artifacts into per-subsystem knowledge files. Spawned by execute-phase after plan execution.
 model: sonnet
-tools: Read, Write, Bash, Grep, Glob
+tools: Read, Edit, Write, Bash, Grep, Glob
 color: yellow
 ---
 
@@ -137,25 +137,25 @@ Extract knowledge, not descriptions. "Using React" is not knowledge. "Using Reac
 
 ## Step 6: Merge Into Knowledge Files
 
-For each affected subsystem, merge extracted content into the knowledge file:
+For each affected subsystem, edit the knowledge file to reflect current state:
 
-- **Decisions:** Add new entries, update superseded decisions, remove contradicted ones.
-- **Architecture:** Update structural descriptions with new components and patterns.
-- **Design:** Add new specs, update changed specs.
-- **Pitfalls:** Add new entries, deduplicate with existing.
-- **Key Files:** Add new paths, remove renamed or deleted files.
+- **Decisions:** Append new entries. Edit superseded decisions in place. Delete contradicted ones.
+- **Architecture:** Edit structural descriptions with new components and patterns.
+- **Design:** Append new specs, edit changed specs.
+- **Pitfalls:** Append new entries. Delete duplicates of existing entries.
+- **Key Files:** Append new paths, delete renamed or deleted files.
 
-Rewrite the full file — not append. The result is the current state of knowledge.
+Use `Edit` for existing files — targeted changes preserve content you haven't inspected. Use `Write` only for new files (subsystem has no knowledge file yet).
 
-## Step 7: Write Knowledge Files
+## Step 7: Update Knowledge Files
 
 ```bash
 mkdir -p .planning/knowledge/
 ```
 
-Write one file per affected subsystem. Follow the template format from `~/.claude/mindsystem/templates/knowledge.md`. Omit sections with no content.
+For new subsystems (no existing file), use `Write` to create the file following the template format from `~/.claude/mindsystem/templates/knowledge.md`. For existing files, all changes should already be applied via `Edit` in step 6. Omit empty sections.
 
-Only write files for subsystems found in SUMMARY.md frontmatter.
+Only update files for subsystems found in SUMMARY.md frontmatter.
 
 ## Step 8: Delete PLAN.md Files
 
@@ -203,7 +203,7 @@ Use `+N` for new entries added, `updated` for sections rewritten with changes, `
 
 **Preserve rationale.** The "because" part is the value. Decisions without rationale are just facts.
 
-**Rewrite, not append.** Each consolidation produces the current state. Superseded decisions get updated, not duplicated.
+**Edit to reflect current state.** Update superseded decisions, remove outdated patterns, append new entries. Use `Edit` for existing files, `Write` only for new files.
 
 **Handle missing files gracefully.** Not all phases have CONTEXT, DESIGN, or RESEARCH files. This is normal.
 
@@ -220,7 +220,8 @@ Use `+N` for new entries added, `updated` for sections rewritten with changes, `
 <success_criteria>
 - [ ] Subsystem alignment validated against config.json
 - [ ] Content extracted and distributed per extraction guide
-- [ ] Knowledge files written to `.planning/knowledge/`
+- [ ] Existing knowledge files modified via Edit (not Write) — targeted changes, no full-file replacement
+- [ ] New knowledge files created with Write in `.planning/knowledge/`
 - [ ] Empty sections omitted from knowledge files
 - [ ] PLAN.md files deleted from phase directory
 - [ ] CONTEXT.md, DESIGN.md, RESEARCH.md, SUMMARY.md preserved

package/commands/ms/add-phase.md

@@ -148,10 +148,6 @@ Add the new phase entry to the roadmap:
    **Design focus**: {focus} ← only if Likely
    **Research**: {Likely (reason) | Unlikely (reason)}
    **Research topics**: {topics} ← only if Likely
-   **Plans:** 0 plans
-
-   Plans:
-   - [ ] TBD (run /ms:plan-phase {N} to break down)
 
    **Details:**
    [To be added during planning]

package/commands/ms/execute-phase.md

@@ -145,14 +145,14 @@ Then route based on status:
 | Status | Route |
 |--------|-------|
 | `gaps_found` | Route C (gap closure) |
-| `passed` + more phases | Route A (verify + next phase) |
+| `passed` + more phases | Route A (verify) |
 | `passed` + last phase | Route B (verify + milestone complete) |
 
 Thoroughness by default: verify-work is the primary "Next Up" in both routes. Assess skip context per workflow `offer_next` step.
 
 ---
 
-**Route A: Phase verified, more phases remain**
+**Shared steps (Routes A and B):**
 
 1. Show phase completion summary:
 ```
@@ -174,26 +174,33 @@ All {Y} plans finished. Phase goal verified.
 {If skip context: "Phase involved only {description} with no user-facing changes — skip if structural verification is sufficient."}
 ```
 
-4. Read `~/.claude/mindsystem/references/routing/next-phase-routing.md` to determine the most appropriate command for Phase {Z+1}. Present next phase context and options:
-```
-**Phase {Z+1}: {Name}** — {Goal}
-{If pre-work flagged: brief note about recommendations}
+**Then branch by route:**
 
-**Also available:**
-- `/ms:{suggested} {Z+1}` — {reason}
-- `/ms:plan-phase {Z+1}` — skip pre-work, plan directly
-```
+**Route A: More phases remain**
 
----
+4. **If skip context applies:** Determine next phase's primary suggestion:
+   - From ROADMAP.md (already in context), get Phase {Z+1} pre-work flags
+   - Check: CONTEXT.md exists? DESIGN.md? RESEARCH.md? in next phase dir
+   - Priority: discuss (if Likely + no CONTEXT.md) > design (if Likely + no DESIGN.md) > research (if Likely + no RESEARCH.md) > plan-phase
+   - Present ONE "Also available" entry:
+   ```
+   ---
+   **Also available:**
+   - `/ms:{suggested} {Z+1}` — skip verify, start Phase {Z+1}: {Name}
+   ---
+   ```
+   **If skip context does NOT apply:** No "Also available" — verify-work is the sole suggestion.
 
-**Route B: Phase verified, milestone complete**
+**Route B: Milestone complete**
 
-Follow Route A steps 1-3, then present milestone options:
+4. Present milestone options:
 ```
+---
 **Also available:**
 - `/ms:audit-milestone` — verify requirements, cross-phase integration, E2E flows
 - `/ms:complete-milestone` — skip audit, archive directly
 - `/ms:add-phase <description>` — add another phase first
+---
 ```
 
 ---

package/commands/ms/insert-phase.md

@@ -163,10 +163,6 @@ Insert the new phase entry into the roadmap:
    **Design focus**: {focus} ← only if Likely
    **Research**: {Likely (reason) | Unlikely (reason)}
    **Research topics**: {topics} ← only if Likely
-   **Plans:** 0 plans
-
-   Plans:
-   - [ ] TBD (run /ms:plan-phase {decimal_phase} to break down)
 
    **Details:**
    [To be added during planning]

package/mindsystem/references/routing/next-phase-routing.md

@@ -1,6 +1,6 @@
 # Next Phase Routing
 
-Reference for presenting "Next Up" guidance for a phase. Used by progress (current phase), execute-phase (next phase), and verify-work (next phase).
+Reference for presenting "Next Up" guidance for a phase. Used by progress (current phase) and verify-work (next phase).
 
 ## Purpose
 

package/mindsystem/templates/knowledge.md

@@ -66,7 +66,7 @@ Template for `.planning/knowledge/{subsystem}.md` — per-subsystem knowledge fi
 - **Architecture and Design use prose bullets.** Describe how things work, not tables.
 - **Pitfalls use bold titles** for scannability.
 - **Key Files is a flat list.** No nesting, no grouping.
-- **Rewrite semantics, not append.** Each consolidation produces the current state. Superseded decisions get updated. Outdated patterns get removed. The file is always current.
+- **Edit to reflect current state.** Each update produces the current state through targeted edits — update superseded decisions, remove outdated patterns, append new entries. Use `Edit` for existing files, `Write` only for new files. Never replace an entire knowledge file via `Write`.
 
 ## Cross-Reference Pattern
 

package/mindsystem/templates/milestone-archive.md

@@ -10,8 +10,6 @@ This template is used by the complete-milestone workflow to create archive files
 
 **Status:** ✅ SHIPPED {{DATE}}
 **Phases:** {{PHASE_START}}-{{PHASE_END}}
-**Total Plans:** {{TOTAL_PLANS}}
-
 ## Overview
 
 {{MILESTONE_DESCRIPTION}}
@@ -26,13 +24,6 @@ This template is used by the complete-milestone workflow to create archive files
 
 **Goal**: {{PHASE_GOAL}}
 **Depends on**: {{DEPENDS_ON}}
-**Plans**: {{PLAN_COUNT}} plans
-
-Plans:
-
-- [x] {{PHASE}}-01: {{PLAN_DESCRIPTION}}
-- [x] {{PHASE}}-02: {{PLAN_DESCRIPTION}}
-      [... all plans ...]
 
 **Details:**
 {{PHASE_DETAILS_FROM_ROADMAP}}
@@ -43,11 +34,6 @@ Plans:
 
 **Goal**: Fix authentication bypass vulnerability
 **Depends on**: Phase 2
-**Plans**: 1 plan
-
-Plans:
-
-- [x] 02.1-01: Patch auth vulnerability
 
 **Details:**
 {{PHASE_DETAILS_FROM_ROADMAP}}

package/mindsystem/templates/roadmap-milestone.md

@@ -18,12 +18,6 @@ Template for reorganizing `ROADMAP.md` after first milestone ships. Collapse com
 
 ### Phase 1: [Name]
 **Goal**: [What this phase delivers]
-**Plans**: 3 plans
-
-Plans:
-- [x] 01-01: [Brief description]
-- [x] 01-02: [Brief description]
-- [x] 01-03: [Brief description]
 
 [... remaining phases ...]
 
@@ -36,11 +30,6 @@ Plans:
 #### Phase 5: [Name]
 **Goal**: [What this phase delivers]
 **Depends on**: Phase 4
-**Plans**: 2 plans
-
-Plans:
-- [ ] 05-01: [Brief description]
-- [ ] 05-02: [Brief description]
 
 [... remaining phases ...]
 
@@ -52,11 +41,11 @@ Plans:
 
 ## Progress
 
-| Phase | Milestone | Plans Complete | Status | Completed |
-|-------|-----------|----------------|--------|-----------|
-| 1. Foundation | MVP | 3/3 | Complete | YYYY-MM-DD |
-| 2. Features | MVP | 2/2 | Complete | YYYY-MM-DD |
-| 5. Security | Security & Polish | 0/2 | Not started | - |
+| Phase | Milestone | Status | Completed |
+|-------|-----------|--------|-----------|
+| 1. Foundation | MVP | Complete | YYYY-MM-DD |
+| 2. Features | MVP | Complete | YYYY-MM-DD |
+| 5. Security | Security & Polish | Not started | - |
 ```
 
 **Notes:**

package/mindsystem/templates/roadmap.md

@@ -52,12 +52,6 @@ Decimal phases appear between their surrounding integers in numeric order.
 **Discuss**: Unlikely (mechanical setup, zero design decisions)
 **Design**: Unlikely (backend only)
 **Research**: Unlikely (established patterns)
-**Plans**: [Number of plans, e.g., "3 plans" or "TBD"]
-
-Plans:
-- [ ] 01-01: [Brief description of first plan]
-- [ ] 01-02: [Brief description of second plan]
-- [ ] 01-03: [Brief description of third plan]
 
 ### Phase 2: [Name]
 **Goal**: [What this phase delivers]
@@ -72,21 +66,12 @@ Plans:
 **Design focus**: [What to design]
 **Research**: Likely (new integration)
 **Research topics**: [What needs investigating]
-**Plans**: [Number of plans]
-
-Plans:
-- [ ] 02-01: [Brief description]
-- [ ] 02-02: [Brief description]
 
 ### Phase 2.1: Critical Fix (INSERTED)
 **Goal**: [Urgent work inserted between phases]
 **Depends on**: Phase 2
 **Success Criteria** (what must be TRUE):
   1. [What the fix achieves]
-**Plans**: 1 plan
-
-Plans:
-- [ ] 02.1-01: [Description]
 
 ### Phase 3: [Name]
 **Goal**: [What this phase delivers]
@@ -101,11 +86,6 @@ Plans:
 **Design**: Unlikely (API only)
 **Research**: Likely (external API)
 **Research topics**: [What needs investigating]
-**Plans**: [Number of plans]
-
-Plans:
-- [ ] 03-01: [Brief description]
-- [ ] 03-02: [Brief description]
 
 ### Phase 4: [Name]
 **Goal**: [What this phase delivers]
@@ -118,22 +98,18 @@ Plans:
 **Discuss topics**: [Priority rules, batch vs individual, error recovery]
 **Design**: Unlikely (backend only)
 **Research**: Unlikely (internal patterns)
-**Plans**: [Number of plans]
-
-Plans:
-- [ ] 04-01: [Brief description]
 
 ## Progress
 
 **Execution Order:**
 Phases execute in numeric order: 2 → 2.1 → 2.2 → 3 → 3.1 → 4
 
-| Phase | Plans Complete | Status | Completed |
-|-------|----------------|--------|-----------|
-| 1. [Name] | 0/3 | Not started | - |
-| 2. [Name] | 0/2 | Not started | - |
-| 3. [Name] | 0/2 | Not started | - |
-| 4. [Name] | 0/1 | Not started | - |
+| Phase | Status | Completed |
+|-------|--------|-----------|
+| 1. [Name] | Not started | - |
+| 2. [Name] | Not started | - |
+| 3. [Name] | Not started | - |
+| 4. [Name] | Not started | - |
 ```
 
 <guidelines>
@@ -145,11 +121,9 @@ Phases execute in numeric order: 2 → 2.1 → 2.2 → 3 → 3.1 → 4
 **Initial planning:**
 - Phase count derived from actual work (not a target number)
 - Each phase delivers something coherent
-- Phases can have 1+ plans (split by orchestrator judgment — multiple subsystems, context budget, vertical slices)
 - Plans use naming: {phase}-{plan}-PLAN.md (e.g., 01-02-PLAN.md)
 - No time estimates (this isn't enterprise PM)
 - Progress table updated by execute workflow
-- Plan count can be "TBD" initially, refined during planning
 
 **Success criteria:**
 - 2-5 observable behaviors per phase (from user's perspective)

package/mindsystem/workflows/complete-milestone.md

@@ -345,7 +345,6 @@ Extract completed milestone details and create archive file.
    - {{DATE}} — Today's date
    - {{PHASE_START}} — First phase number in milestone
    - {{PHASE_END}} — Last phase number in milestone
-   - {{TOTAL_PLANS}} — Count of all plans in milestone
    - {{MILESTONE_DESCRIPTION}} — From ROADMAP.md overview
    - {{PHASES_SECTION}} — Full phase details extracted
    - {{DECISIONS_FROM_PROJECT}} — Key decisions from PROJECT.md

package/mindsystem/workflows/doctor-fixes.md

@@ -315,7 +315,7 @@ Spawn a `general-purpose` subagent (Task tool) with the following structured pro
 > - Preserve rationale when visible in code comments or config. Do not fabricate reasons.
 > - Do not fabricate specific numbers (limits, thresholds, counts) — read from source or omit.
 > - Omit empty sections. No Design section if subsystem has no UI.
-> - Rewrite semantics — if existing knowledge files exist, merge by producing current state.
+> - Edit to reflect current state — use `Edit` for existing knowledge files (targeted changes), `Write` only for new files.
 > - Cross-reference between subsystems where relevant: "(see api subsystem)".
 > - Decisions table: 5-10 words per cell. Source column: `"existing"` for source code mode, artifact reference for artifact mode.
 > - Key files must reference actual paths verified to exist.

package/mindsystem/workflows/execute-phase.md

@@ -539,24 +539,24 @@ All {Y} plans finished. Phase goal verified.
 
 **Then present "Also available" based on milestone status:**
 
-**If more phases remain:**
+**If more phases remain AND skip context applies:**
 
-Read `~/.claude/mindsystem/references/routing/next-phase-routing.md` to determine the most appropriate command for the next phase (discuss/design/research/plan based on pre-work flags). Present concisely under "Also available":
+Determine the next phase's primary suggestion inline — do NOT read next-phase-routing.md:
+- From ROADMAP.md (already in context), get Phase {Z+1} pre-work flags
+- Check: CONTEXT.md exists? DESIGN.md? RESEARCH.md? in next phase dir
+- Priority: discuss (if Likely + no CONTEXT.md) > design (if Likely + no DESIGN.md) > research (if Likely + no RESEARCH.md) > plan-phase
+- Present ONE "Also available" entry:
 
 ```markdown
 ---
-
-**Phase {Z+1}: {Name}** — {Goal}
-{If pre-work flagged: brief note about recommendations}
-
 **Also available:**
-- `/ms:{suggested} {Z+1}` — {reason from routing}
-- `/ms:plan-phase {Z+1}` — skip pre-work, plan directly
-
+- `/ms:{suggested} {Z+1}` — skip verify, start Phase {Z+1}: {Name}
 ---
 ```
 
-Include the pre-work recommendations table from the routing reference if any pre-work is flagged as "Likely".
+**If more phases remain but skip context does NOT apply:** No "Also available" — verify-work is the sole suggestion.
+
+Do NOT present pre-work recommendation tables or multiple cross-phase alternatives. Cross-phase routing belongs to verify-work and progress.
 
 **If milestone complete:**
 

package/mindsystem/workflows/transition.md

@@ -97,7 +97,6 @@ Update the file:
 
 - Mark current phase: `[x] Complete`
 - Add completion date
-- Update plan count to final (e.g., "3/3 plans complete")
 - Update Progress table
 - Keep next phase as `[ ] Not started`
 
@@ -112,11 +111,11 @@ Update the file:
 
 ## Progress
 
-| Phase             | Plans Complete | Status      | Completed  |
-| ----------------- | -------------- | ----------- | ---------- |
-| 1. Foundation     | 3/3            | Complete    | 2025-01-15 |
-| 2. Authentication | 0/2            | Not started | -          |
-| 3. Core Features  | 0/1            | Not started | -          |
+| Phase             | Status      | Completed  |
+| ----------------- | ----------- | ---------- |
+| 1. Foundation     | Complete    | 2025-01-15 |
+| 2. Authentication | Not started | -          |
+| 3. Core Features  | Not started | -          |
 ```
 
 </step>
@@ -442,7 +441,6 @@ Respect user judgment — they know if work matters.
 
 **If marking complete with incomplete plans:**
 
-- Update ROADMAP: "2/3 plans complete" (not "3/3")
 - Note in transition message which plans were skipped
 
 </partial_completion>
@@ -453,7 +451,7 @@ Transition is complete when:
 
 - [ ] Current phase plan summaries verified (all exist or user chose to skip)
 - [ ] Any stale handoffs deleted
-- [ ] ROADMAP.md updated with completion status and plan count
+- [ ] ROADMAP.md updated with completion status
 - [ ] PROJECT.md evolved (requirements, decisions, description if needed)
 - [ ] STATE.md updated (position, project reference, context, session)
 - [ ] Progress table updated

package/mindsystem/workflows/verify-work.md

@@ -365,24 +365,21 @@ This knowledge informs investigation (where to look, known pitfalls) and any sub
 3. Check git log for recent changes to relevant files
 ```
 
-**2. Determine if cause is found:**
+**2. Report finding and act:**
 
-**If cause found AND fix is simple (single file, straightforward change):**
-- Propose fix in plain language:
-  ```
-  Found the issue. In `ErrorBanner.tsx` line 42, the error message is
-  hardcoded to "Something went wrong" instead of using the actual error
-  from the API response.
+State the root cause and the fix in plain language before applying. This lets the user capture the lesson in persistent instructions or catch a wrong direction before reviewing the diff. No confirmation needed — go straight to fixing.
 
-  I'll change it to use `error.message` from props.
+Format:
+```
+{Root cause — what the code does wrong and why, 1-2 sentences}
 
-  Apply this fix?
-  ```
-- Present options: [Yes / Let me see the code first / Different approach]
-- If approved: Go to `apply_fix`
+Fix: {what the fix changes, 1-2 sentences}
+```
+
+**If fix is simple (single file, straightforward change):**
+- Go to `apply_fix` immediately
 
-**If cause found BUT fix is complex (multiple files, architectural):**
-- Report finding
+**If fix is complex (multiple files, architectural):**
 - Spawn ms-verify-fixer subagent (go to `escalate_to_fixer`)
 
 **If cause NOT found after 2-3 checks:**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mindsystem-cc",
-  "version": "4.3.0",
+  "version": "4.3.1",
   "description": "The engineer's meta-prompting system for Claude Code.",
   "bin": {
     "mindsystem-cc": "bin/install.js"