mindsystem-cc 3.20.0 → 3.22.0

package/commands/ms/help.md

@@ -22,24 +22,25 @@ Output ONLY the reference content below. Do NOT add:
 ## Start Here
 
 - If you already have `.planning/` in this repo: run `/ms:progress`.
-- If you’re starting in an existing codebase (brownfield): run `/ms:map-codebase`, then `/ms:new-project`.
 - Otherwise: run `/ms:new-project`.
 
 ## Quick Start
 
 ### Greenfield (new project)
 
-1. `/ms:new-project` - Initialize project with brief
-2. `/ms:research-project` - (optional) Research domain ecosystem
-3. `/ms:create-roadmap` - Define requirements and create roadmap
-4. `/ms:plan-phase 1` - Create detailed plan for first phase
-5. `/ms:execute-phase 1` - Execute with parallel agents
+1. `/ms:new-project` — Initialize project with brief
+2. `/ms:config` — (optional) Configure code reviewers and gitignore
+3. `/ms:research-project` — (optional) Research domain ecosystem
+4. `/ms:create-roadmap` — Define requirements and create roadmap
+5. `/ms:plan-phase 1` — Create detailed plan for first phase
+6. `/ms:execute-phase 1` — Execute with parallel agents
 
 ### Brownfield (existing codebase)
 
-1. `/ms:map-codebase` - Analyze existing code first
-2. `/ms:new-project` - Questions focus on what you’re adding/changing
-3. Continue with steps 2-5 above (codebase docs load automatically)
+1. `/ms:new-project` — Questions focus on business context and vision
+2. `/ms:map-codebase` — Analyze existing code
+3. `/ms:config` — (optional) Configure code reviewers and gitignore
+4. Continue with research/roadmap/plan/execute
 
 ## Staying Updated
 
@@ -62,8 +63,8 @@ Initialize → (Optional Research) → Roadmap → Plan → Execute → Verify
 ```
 
 Common deviations:
-- Existing repo: `/ms:map-codebase` before `/ms:new-project`
-- Plan looks wrong: `/ms:list-phase-assumptions <phase>` or `/ms:check-phase <phase>`
+- Existing repo: `/ms:map-codebase` after `/ms:new-project` (or before — either works)
+- Plan looks wrong: `/ms:discuss-phase <phase>` or `/ms:check-phase <phase>`
 - Unknown domain: `/ms:research-project` or `/ms:research-phase <phase>`
 - Phase prep: `/ms:discuss-phase` → `/ms:design-phase` → `/ms:research-phase` → `/ms:plan-phase` (all optional before plan)
 - Execution gaps: `/ms:plan-phase <phase> --gaps` then `/ms:execute-phase <phase>`
@@ -82,6 +83,16 @@ Initialize new project with brief and configuration.
 
 Usage: `/ms:new-project`
 
+**`/ms:config`**
+Configure Mindsystem preferences — code reviewers, mockup preferences, gitignore patterns, git remote.
+
+- Use when: you want to set up code review agents, mockup open behavior, manage which .planning/ artifacts are git-ignored, or push your repo to GitHub.
+- Edits `.planning/config.json` and `.gitignore`
+- Suggests code reviewers based on tech stack (needs PROJECT.md)
+- Idempotent — run anytime to reconfigure
+
+Usage: `/ms:config`
+
 **`/ms:research-project`**
 Research domain ecosystem before creating roadmap.
 
@@ -111,18 +122,20 @@ Map an existing codebase for brownfield projects.
 - Analyzes codebase with parallel Explore agents
 - Creates `.planning/codebase/` with 7 focused documents
 - Covers stack, architecture, structure, conventions, testing, integrations, concerns
-- Use before `/ms:new-project` on existing codebases
+- Use on existing codebases (before or after `/ms:new-project`)
 
 Usage: `/ms:map-codebase`
 
 ### Phase Planning
 
 **`/ms:discuss-phase <number>`**
-Help articulate your vision for a phase before planning.
+Product-informed collaborative thinking before planning.
 
-- Captures how you imagine this phase working
-- Creates CONTEXT.md with your vision, essentials, and boundaries
-- Use when you have ideas about how something should look/feel
+- Loads milestone artifacts (PROJECT.md, REQUIREMENTS.md) for product context
+- Surfaces Claude's assumptions and validates before deep questioning
+- Offers competitor/UX research for user-facing phases
+- Grounds every question in target audience, industry patterns, and tradeoffs
+- Creates CONTEXT.md with your vision, essentials, and reasoning-backed decisions
 
 Usage: `/ms:discuss-phase 2`
 
@@ -160,15 +173,6 @@ Comprehensive ecosystem research for niche/complex domains.
 
 Usage: `/ms:research-phase 3`
 
-**`/ms:list-phase-assumptions <number>`**
-See what Claude is planning to do before it starts.
-
-- Shows Claude's intended approach for a phase
-- Lets you course-correct if Claude misunderstood your vision
-- No files created - conversational output only
-
-Usage: `/ms:list-phase-assumptions 3`
-
 **`/ms:plan-phase [number] [--gaps]`**
 Create detailed execution plan for a specific phase.
 
@@ -221,7 +225,7 @@ User acceptance testing of phase or plan.
 
 Usage: `/ms:verify-work 5`
 
-**`/ms:audit-milestone [version]`**
+**`/ms:audit-milestone [name]`**
 Audit milestone completion against original intent.
 
 - Use when: you think you’re “done” and want cross-phase integration + requirements coverage checked before archiving.
@@ -230,7 +234,7 @@ Audit milestone completion against original intent.
 - Maintains TECH-DEBT.md as single source of truth for debt items
 - Creates MILESTONE-AUDIT.md with gaps and tech debt
 
-Usage: `/ms:audit-milestone 1.0.0`
+Usage: `/ms:audit-milestone`
 
 ### Roadmap Management
 
@@ -280,18 +284,19 @@ Discover what to build next and start a new milestone.
 - Routes to create-roadmap or research-project
 
 Usage: `/ms:new-milestone`
-Usage: `/ms:new-milestone "v2.0 Features"`
+Usage: `/ms:new-milestone "Push Notifications"`
 
-**`/ms:complete-milestone <version>`**
-Archive completed milestone and prepare for next version.
+**`/ms:complete-milestone [name]`**
+Archive completed milestone and prepare for next.
 
 - Creates MILESTONES.md entry with stats
 - Extracts curated learnings for future milestone planning
 - Archives full details to milestones/ directory
-- Creates git tag for the release
-- Prepares workspace for next version
+- Prepares workspace for next milestone
+- Auto-detects current milestone from PROJECT.md if no argument provided
 
-Usage: `/ms:complete-milestone 1.0.0`
+Usage: `/ms:complete-milestone`
+Usage: `/ms:complete-milestone "MVP"`
 
 **`/ms:plan-milestone-gaps`**
 Create phases to close gaps identified by milestone audit.
@@ -443,6 +448,7 @@ Usage: `/ms:release-notes`
 
 ```
 /ms:new-project                 # Extract your idea through questions
+/ms:config                      # (optional) Configure code reviewers and gitignore
 /ms:research-project            # (recommended) Research domain ecosystem
 /ms:create-roadmap              # Define requirements and create phases
 /ms:plan-phase 1                # Create detailed plan
@@ -452,8 +458,9 @@ Usage: `/ms:release-notes`
 **Starting with existing code (brownfield):**
 
 ```
-/ms:map-codebase                # Step 1: Analyze existing code
-/ms:new-project                 # Step 2: Questions focus on what you're adding/changing
+/ms:new-project                 # Step 1: Questions focus on business context and vision
+/ms:map-codebase                # Step 2: Analyze existing code
+/ms:config                      # (optional) Configure code reviewers and gitignore
 /ms:research-project            # (optional) Research new domain areas
 /ms:create-roadmap              # Define requirements and create roadmap
 /ms:plan-phase 1                # Codebase docs load automatically
@@ -517,19 +524,19 @@ Common options:
 **Completing a milestone:**
 
 ```
-/ms:audit-milestone 1.0.0       # Verify before completing
-/ms:complete-milestone 1.0.0    # Archive and tag
+/ms:audit-milestone             # Verify before completing
+/ms:complete-milestone          # Archive milestone
 /ms:new-milestone               # Discover and start next milestone
 ```
 
 **Closing gaps from audit:**
 
 ```
-/ms:audit-milestone 1.0.0       # Finds gaps
+/ms:audit-milestone             # Finds gaps
 /ms:plan-milestone-gaps         # Creates phases to fix them
 /ms:plan-phase 6                # Plan first gap closure phase
 /ms:execute-phase 6
-/ms:audit-milestone 1.0.0       # Re-audit when done
+/ms:audit-milestone             # Re-audit when done
 ```
 
 **Capturing ideas during work:**

package/commands/ms/insert-phase.md

@@ -136,9 +136,9 @@ Insert the new phase entry into the roadmap:
 
 2. Before writing the phase entry, analyze the description to determine pre-work flags:
 
-   **Discuss**: Likely when description mentions user-facing features, UX decisions,
-   experiential qualities, or novel features. Unlikely for backend/infra, bug fixes,
-   technical debt, or clear-cut work.
+   **Discuss**: Default Likely — enumerate 2-4 assumptions or open questions specific
+   to the phase. Unlikely only for fully mechanical zero-decision work (version bump,
+   rename-only refactor, config-only change, pure deletion/cleanup).
 
    **Design**: Likely when description involves UI work, visual elements, forms,
    dashboards, or multi-screen flows. Unlikely for backend-only, API, infrastructure,
@@ -216,10 +216,9 @@ After the "Next Up" section, add:
 </step>
 
 <step name="update_last_command">
-Update `.planning/STATE.md` Last Command field:
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:insert-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
+```bash
+ms-tools set-last-command "ms:insert-phase $ARGUMENTS"
+```
 </step>
 
 </process>

package/commands/ms/map-codebase.md

@@ -60,8 +60,7 @@ Check for .planning/STATE.md - loads context if project already initialized
 5. Verify all 7 documents exist with line counts
 6. Commit codebase map
 7. Offer next steps (typically: /ms:new-project or /ms:plan-phase)
-8. Update `.planning/STATE.md` Last Command field (if STATE.md exists):
-   - Format: `Last Command: ms:map-codebase $ARGUMENTS | YYYY-MM-DD HH:MM`
+8. **Update last command:** `ms-tools set-last-command "ms:map-codebase $ARGUMENTS"`
 </process>
 
 <success_criteria>

package/commands/ms/new-milestone.md

@@ -1,7 +1,7 @@
 ---
 name: ms:new-milestone
 description: Start a new milestone — discover what to build, update PROJECT.md, create context for downstream
-argument-hint: "[milestone name, e.g., 'v1.1 Notifications']"
+argument-hint: "[name, e.g., 'Notifications']"
 allowed-tools:
   - Read
   - Write
@@ -39,12 +39,36 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
 
 ## Phase 1: Orient
 
+0. **Validate PROJECT.md exists:**
+
+   ```bash
+   [ -f .planning/PROJECT.md ] || { echo "NO_PROJECT"; exit 0; }
+   ```
+
+   **If `NO_PROJECT`:** Present message and stop:
+
+   ```
+   No PROJECT.md found. Initialize the project first to capture business context, target audience, and project vision.
+
+   ---
+
+   ## ▶ Next Up
+
+   `/ms:new-project` — Initialize project with business context and vision
+
+   <sub>`/clear` first → fresh context window</sub>
+
+   ---
+   ```
+
+   **You MUST run the bash command above using the Bash tool before proceeding.**
+
 1. **Load context:**
    - Read PROJECT.md (existing project, validated requirements, decisions)
    - Read MILESTONES.md (what shipped previously)
    - Read STATE.md (pending todos, blockers)
    - Read config.json (project settings)
-   - Calculate previous milestone version from MILESTONES.md (e.g., if last shipped was v1.0, previous=1.0)
+   - Identify previous milestone name from MILESTONES.md (e.g., last shipped was "MVP")
 
 2. **Check for active milestone:**
 
@@ -52,7 +76,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
 
    Use AskUserQuestion:
    - header: "Active milestone"
-   - question: "There's a milestone in progress (v[X.Y]). What do you want to do?"
+   - question: "There's a milestone in progress ([Name]). What do you want to do?"
    - options:
      - "Complete it first" — run /ms:complete-milestone
      - "Add phases to it" — run /ms:add-phase
@@ -62,9 +86,9 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
    If "Continue anyway": proceed.
 
 3. **Strategic assessment (silent — do not output this step):**
-   - Check for previous milestone artifacts using calculated version:
+   - Check for previous milestone artifacts:
      - `.planning/knowledge/*.md` (subsystem knowledge files — persist across milestones)
-     - `.planning/milestones/v{VERSION}/MILESTONE-AUDIT.md` (if exists)
+     - `.planning/milestones/{slug}/MILESTONE-AUDIT.md` (if exists, for last completed milestone)
      - `.planning/TECH-DEBT.md` (if exists)
    - Identify: outstanding tech debt, untested assumptions, high-impact gaps, unaddressed requirements
    - This is background analysis — synthesize silently, surface through suggestions in step 4
@@ -74,7 +98,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
    ```
    ## Last Milestone
 
-   v[X.Y] [Name] — [key accomplishments, 1-2 lines]
+   [Name] — [key accomplishments, 1-2 lines]
 
    ## Suggested Directions
 
@@ -91,7 +115,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
    - Strategic features inferred from PROJECT.md: Who It's For, Core Problem, How It's Different
    - Pending todos from STATE.md
 
-   If no meaningful artifacts exist (first milestone after v1.0), base suggestions purely on PROJECT.md.
+   If no meaningful artifacts exist (first milestone), base suggestions purely on PROJECT.md.
 
 5. **Freeform opening:**
 
@@ -157,17 +181,17 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
 
 ## Phase 3: Commit
 
-12. **Determine milestone version:**
-    - Parse last version from MILESTONES.md
-    - Suggest next version (v1.0 → v1.1, or v2.0 for major shifts)
-    - Confirm with user via AskUserQuestion
+12. **Determine milestone name:**
+    - Derive milestone name from the conversation (e.g., "Push Notifications", "Security Hardening")
+    - Generate slug from name (e.g., "push-notifications", "security-hardening")
+    - Confirm name with user via AskUserQuestion
 
 13. **Present milestone summary:**
 
     ```
     ## Milestone Summary
 
-    **Version:** v[X.Y] [Name]
+    **Name:** [Name]
     **Goal:** [One sentence]
     **Target features:**
     - [Feature 1]
@@ -189,7 +213,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
     Add/update these sections:
 
     ```markdown
-    ## Current Milestone: v[X.Y] [Name]
+    ## Current Milestone: [Name]
 
     **Goal:** [One sentence describing milestone focus]
 
@@ -222,7 +246,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
     Phase: Not started (run /ms:create-roadmap)
     Plan: —
     Status: Defining requirements
-    Last activity: [today] — Milestone v[X.Y] started
+    Last activity: [today] — Milestone [Name] started
 
     Progress: ░░░░░░░░░░ 0%
     ```
@@ -234,7 +258,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
     ```bash
     git add .planning/PROJECT.md .planning/STATE.md .planning/MILESTONE-CONTEXT.md
     git commit -m "$(cat <<'EOF'
-    docs: start milestone v[X.Y] [Name]
+    docs: start milestone [Name]
     EOF
     )"
     ```
@@ -256,7 +280,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
     Based on the conversation, recommend ONE path. If unfamiliar domains or open questions surfaced during discovery, recommend `/ms:research-project`. Otherwise recommend `/ms:create-roadmap`.
 
     ```
-    Milestone v[X.Y] [Name] initialized.
+    Milestone [Name] initialized.
 
     PROJECT.md updated with new goals.
     Context saved to MILESTONE-CONTEXT.md
@@ -277,9 +301,7 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
     ---
     ```
 
-20. **Update last command:**
-    - Update `.planning/STATE.md` Last Command field
-    - Format: `Last Command: ms:new-milestone $ARGUMENTS | YYYY-MM-DD HH:MM`
+20. **Update last command:** `ms-tools set-last-command "ms:new-milestone $ARGUMENTS"`
 
 </process>
 

package/commands/ms/new-project.md

@@ -12,7 +12,7 @@ allowed-tools:
 
 Initialize a new project through comprehensive context gathering.
 
-This is the most leveraged moment in any project. Deep questioning here means better plans, better execution, better outcomes. The quality of PROJECT.md determines the quality of everything downstream.
+Questioning depth determines PROJECT.md quality, which determines everything downstream. Invest disproportionate effort here — the other steps are mechanical.
 
 Creates `.planning/` with PROJECT.md and config.json.
 
@@ -31,11 +31,11 @@ Creates `.planning/` with PROJECT.md and config.json.
 
 <step name="setup">
 
-**MANDATORY FIRST STEP — Execute these checks before ANY user interaction:**
+**Run before any user interaction:**
 
-1. **Abort if project exists:**
+1. **Detect update mode:**
    ```bash
-   [ -f .planning/PROJECT.md ] && echo "ERROR: Project already initialized. Use /ms:progress" && exit 1
+   [ -f .planning/PROJECT.md ] && echo "IS_UPDATE=true" || echo "IS_UPDATE=false"
    ```
 
 2. **Initialize git repo in THIS directory** (required even if inside a parent repo):
@@ -54,37 +54,11 @@ Creates `.planning/` with PROJECT.md and config.json.
    # Check for existing code files
    CODE_FILES=$(find . -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.swift" -o -name "*.java" 2>/dev/null | grep -v node_modules | grep -v .git | head -20)
    HAS_PACKAGE=$([ -f package.json ] || [ -f requirements.txt ] || [ -f Cargo.toml ] || [ -f go.mod ] || [ -f Package.swift ] && echo "yes")
+   IS_BROWNFIELD=$( ([ -n "$CODE_FILES" ] || [ "$HAS_PACKAGE" = "yes" ]) && echo "yes" || echo "no")
    HAS_CODEBASE_MAP=$([ -d .planning/codebase ] && echo "yes")
    ```
 
-   **You MUST run all bash commands above using the Bash tool before proceeding.**
-
-</step>
-
-<step name="brownfield_offer">
-
-**If existing code detected and .planning/codebase/ doesn't exist:**
-
-Check the results from setup step:
-- If `CODE_FILES` is non-empty OR `HAS_PACKAGE` is "yes"
-- AND `HAS_CODEBASE_MAP` is NOT "yes"
-
-Use AskUserQuestion:
-- header: "Existing Code"
-- question: "I detected existing code in this directory. Would you like to map the codebase first?"
-- options:
-  - "Map codebase first" — Run /ms:map-codebase to understand existing architecture (Recommended)
-  - "Skip mapping" — Proceed with project initialization
-
-**If "Map codebase first":**
-```
-Run `/ms:map-codebase` first, then return to `/ms:new-project`
-```
-Exit command.
-
-**If "Skip mapping":** Continue to question step.
-
-**If no existing code detected OR codebase already mapped:** Continue to question step.
+   **Run all commands above before proceeding.**
 
 </step>
 
@@ -92,6 +66,14 @@ Exit command.
 
 **Open the conversation:**
 
+**If IS_UPDATE=true (update mode):**
+- Read existing `.planning/PROJECT.md`
+- Present a brief summary of the current project context
+- Ask inline (freeform, NOT AskUserQuestion): "What do you want to update?"
+- Follow the same questioning principles below, but focused on what changed
+
+**If IS_UPDATE=false (first run):**
+
 Ask inline (freeform, NOT AskUserQuestion):
 
 - **Greenfield** (no existing code): "What do you want to build?"
@@ -119,21 +101,22 @@ Use grounding questions from `questioning.md` instead of template-shaped questio
 
 When the conversation pauses and sections are still fuzzy, use success-backward: "Imagine this is wildly successful in a year. What does that look like?"
 
-Consult `questioning.md` for techniques — challenge vagueness, derive before asking, use grounding questions over template-shaped questions.
+Consult `questioning.md` for techniques — challenge vagueness, derive before asking.
 
 **Decision gate:**
 
 When you could write a clear PROJECT.md, use AskUserQuestion:
 
 - header: "Ready?"
-- question: "I think I understand what you're after. Ready to create PROJECT.md?"
+- question (first run): "I think I understand what you're after. Ready to create PROJECT.md?"
+- question (update mode): "Ready to update PROJECT.md with these changes?"
 - options:
-  - "Create PROJECT.md" — Let's move forward
+  - "Create PROJECT.md" / "Update PROJECT.md" — Let's move forward
   - "Keep exploring" — I want to share more / ask me more
 
 If "Keep exploring" — ask what they want to add, or identify gaps and probe naturally.
 
-Loop until "Create PROJECT.md" selected.
+Loop until create/update selected.
 
 </step>
 
@@ -195,7 +178,7 @@ Do not compress. Capture everything gathered.
 
 <step name="config">
 
-Create `.planning/config.json` with subsystems and code_review using `templates/config.json` structure.
+Create or update `.planning/config.json` with subsystems and code_review using `templates/config.json` structure.
 
 **Subsystems:** Derive 5-10 initial subsystems from the project context gathered during questioning. These are short, lowercase identifiers for the major functional areas of the project.
 
@@ -206,10 +189,13 @@ Examples by project type:
 
 These values are used throughout the system for consistent categorization of summaries, debug docs, and adhoc work.
 
+**Update mode (config.json already exists):** Re-derive subsystems from updated context. Preserve any existing `code_review` values — do not overwrite configured reviewers with nulls.
+
 </step>
 
 <step name="commit">
 
+**First run:**
 ```bash
 git add .planning/PROJECT.md .planning/config.json
 git commit -m "$(cat <<'EOF'
@@ -222,19 +208,43 @@ EOF
 )"
 ```
 
+**Update mode:**
+```bash
+git add .planning/PROJECT.md .planning/config.json
+git commit -m "$(cat <<'EOF'
+docs: update [project-name] project context
+
+[Brief description of what changed]
+EOF
+)"
+```
+
 </step>
 
 <step name="done">
 
 Present completion with next steps (see ~/.claude/mindsystem/references/continuation-format.md):
 
+**First run:**
 ```
 Project initialized:
 
 - Project: .planning/PROJECT.md
 - Config: .planning/config.json
 [If .planning/codebase/ exists:] - Codebase: .planning/codebase/ (7 documents)
+```
 
+**Update mode:**
+```
+Project updated:
+
+- Project: .planning/PROJECT.md
+- Config: .planning/config.json
+```
+
+**Routing (both modes):**
+
+```
 ---
 
 ## ▶ Next Up
@@ -246,7 +256,8 @@ Project initialized:
 ---
 
 **Also available:**
-- `/ms:create-roadmap` — Skip milestone discovery, define requirements and roadmap directly
+- `/ms:config` — Configure code reviewers, gitignore, and other preferences
+[If brownfield detected and no codebase map:] - `/ms:map-codebase` — Analyze existing codebase for technical context
 
 ---
 ```
@@ -254,11 +265,9 @@ Project initialized:
 </step>
 
 <step name="update_last_command">
-Update `.planning/STATE.md` Last Command field (if STATE.md exists):
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:new-project | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
-- Note: STATE.md may not exist yet if this is the first command
+```bash
+ms-tools set-last-command "ms:new-project"
+```
 </step>
 
 </process>
@@ -272,12 +281,12 @@ Update `.planning/STATE.md` Last Command field (if STATE.md exists):
 
 <success_criteria>
 
-- [ ] Deep questioning completed with business context extracted
+- [ ] All committed to git
+- [ ] config.json has subsystems and code_review settings (existing code_review preserved in update mode)
+- [ ] Validated requirements initialized (empty for greenfield, inferred for brownfield)
+- [ ] Deep questioning completed with business context extracted (or update conversation completed)
 - [ ] PROJECT.md captures product identity (What/Value/Audience/Problem/Differentiation/Flows)
 - [ ] PROJECT.md captures boundaries (Out of Scope, Constraints, Technical Context)
-- [ ] Validated requirements initialized (empty for greenfield, inferred for brownfield)
 - [ ] Key Decisions table initialized
-- [ ] config.json has subsystems and code_review settings
-- [ ] All committed to git
 
 </success_criteria>

package/commands/ms/plan-milestone-gaps.md

@@ -25,7 +25,7 @@ One command creates all fix phases — no manual `/ms:add-phase` per gap.
 
 <context>
 **Audit results:**
-Glob: .planning/v*-MILESTONE-AUDIT.md (use most recent)
+@.planning/MILESTONE-AUDIT.md
 
 **Original intent (for prioritization):**
 @.planning/PROJECT.md
@@ -41,8 +41,7 @@ Glob: .planning/v*-MILESTONE-AUDIT.md (use most recent)
 ## 1. Load Audit Results
 
 ```bash
-# Find the most recent audit file
-ls -t .planning/v*-MILESTONE-AUDIT.md 2>/dev/null | head -1
+cat .planning/MILESTONE-AUDIT.md
 ```
 
 Parse YAML frontmatter to extract structured gaps:
@@ -105,7 +104,7 @@ New phases continue from there:
 ```markdown
 ## Gap Closure Plan
 
-**Milestone:** {version}
+**Milestone:** {name}
 **Gaps to close:** {N} requirements, {M} integration, {K} flows
 
 ### Proposed Phases
@@ -191,15 +190,14 @@ git commit -m "docs(roadmap): add gap closure phases {N}-{M}"
 **After all gap phases complete:**
 
 `/ms:audit-milestone` — re-audit to verify gaps closed
-`/ms:complete-milestone {version}` — archive when audit passes
+`/ms:complete-milestone` — archive when audit passes
 ```
 
 ## 10. Update Last Command
 
-Update `.planning/STATE.md` Last Command field:
-- Find line starting with `Last Command:` in Current Position section
-- Replace with: `Last Command: ms:plan-milestone-gaps | YYYY-MM-DD HH:MM`
-- If line doesn't exist, add it after `Status:` line
+```bash
+ms-tools set-last-command "ms:plan-milestone-gaps"
+```
 
 </process>
 

package/commands/ms/plan-phase.md

@@ -34,11 +34,12 @@ When invoked with `--gaps`, plans address gaps identified by the verifier. Load
 Phase number: $ARGUMENTS (optional - auto-detects next unplanned phase if not provided)
 Gap closure mode: `--gaps` flag triggers gap closure workflow
 
-**Normalize phase number if provided:**
+**Resolve phase if provided:**
 ```bash
+# ms-tools is on PATH — invoke directly, not as a script path
 PHASE_ARG=$(echo "$ARGUMENTS" | grep -oE '^[0-9]+' | head -1)
 if [ -n "$PHASE_ARG" ]; then
-  PHASE=$(printf "%02d" "$PHASE_ARG" 2>/dev/null || echo "$PHASE_ARG")
+  ms-tools find-phase "$PHASE_ARG"
 fi
 ```
 
@@ -104,9 +105,7 @@ Check for `.planning/codebase/` and load relevant documents based on phase type.
    - Number plans sequentially after existing (if 01-03 exist, create 04, 05...)
    - Create PLAN.md file(s) focused on closing specific gaps
 
-6. **Update last command**
-   - Update `.planning/STATE.md` Last Command field
-   - Format: `Last Command: ms:plan-phase $ARGUMENTS | YYYY-MM-DD HH:MM`
+6. **Update last command:** `ms-tools set-last-command "ms:plan-phase $ARGUMENTS"`
 
 7. **Risk assessment** (skip if `--gaps` flag present)
    - Calculate risk score from context already loaded (task count, plan count, external services, CONTEXT.md, cross-cutting concerns, new deps, complex domains)