mindsystem-cc 3.20.0 → 3.21.0

package/commands/ms/research-project.md

@@ -65,8 +65,8 @@ mkdir -p .planning/research
 ```
 
 **Determine milestone context:**
-- If no "Validated" requirements in REQUIREMENTS.md → Greenfield (v1.0)
-- If "Validated" requirements exist → Subsequent milestone (v1.1+)
+- If no "Validated" requirements in REQUIREMENTS.md → Greenfield
+- If "Validated" requirements exist → Subsequent milestone
 
 Spawn all 4 in parallel with rich context:
 
@@ -79,10 +79,10 @@ Project Research — Stack dimension for [domain].
 <milestone_context>
 {greenfield OR subsequent}
 
-**Greenfield (v1.0):**
+**Greenfield (first milestone):**
 Research the standard stack for building [domain] from scratch. Full ecosystem investigation.
 
-**Subsequent (v1.1+):**
+**Subsequent (later milestones):**
 Research what's needed to add [target features] to an existing [domain] app.
 
 IMPORTANT for subsequent milestones:
@@ -128,10 +128,10 @@ Project Research — Features dimension for [domain].
 <milestone_context>
 {greenfield OR subsequent}
 
-**Greenfield (v1.0):**
+**Greenfield (first milestone):**
 What features do [domain] products have? What's table stakes vs differentiating?
 
-**Subsequent (v1.1+):**
+**Subsequent (later milestones):**
 How do [target features] typically work? What's expected behavior?
 
 IMPORTANT for subsequent milestones:
@@ -176,10 +176,10 @@ Project Research — Architecture dimension for [domain].
 <milestone_context>
 {greenfield OR subsequent}
 
-**Greenfield (v1.0):**
+**Greenfield (first milestone):**
 How are [domain] systems typically structured? What are major components?
 
-**Subsequent (v1.1+):**
+**Subsequent (later milestones):**
 How do [target features] integrate with existing [domain] architecture?
 
 IMPORTANT for subsequent milestones:
@@ -224,10 +224,10 @@ Project Research — Pitfalls dimension for [domain].
 <milestone_context>
 {greenfield OR subsequent}
 
-**Greenfield (v1.0):**
+**Greenfield (first milestone):**
 What do [domain] projects commonly get wrong? Critical mistakes?
 
-**Subsequent (v1.1+):**
+**Subsequent (later milestones):**
 What are common mistakes when adding [target features] to [domain]?
 
 IMPORTANT for subsequent milestones:
@@ -303,8 +303,8 @@ After creating SUMMARY.md, update config.json code_review fields with agent name
 1. Read recommended stack from STACK.md
 2. Map to code review agent names:
    - Flutter/Dart:
-     - adhoc: \"ms-flutter-simplifier\"
-     - phase: \"ms-flutter-simplifier\"
+     - adhoc: \"ms-flutter-code-quality\"
+     - phase: \"ms-flutter-code-quality\"
      - milestone: \"ms-flutter-reviewer\"
    - All others:
      - adhoc: \"ms-code-simplifier\"

package/mindsystem/references/continuation-format.md

@@ -59,7 +59,7 @@ When there's meaningful additional context (like a phase identifier), add it as
 
 **Also available:**
 - Review plans before executing
-- `/ms:list-phase-assumptions 2` — check assumptions
+- `/ms:discuss-phase 2` — gather context and validate assumptions
 
 ---
 ```
@@ -84,7 +84,7 @@ Add note that this is the last phase and what comes after:
 
 **After this completes:**
 - Milestone complete
-- Next: `/ms:complete-milestone` — archive and tag
+- Next: `/ms:complete-milestone` — archive milestone
 
 ---
 ```
@@ -168,7 +168,7 @@ When there's no clear primary action:
 ```
 ---
 
-## 🎉 Milestone v1.0 Complete
+## 🎉 Milestone Complete
 
 All 4 phases shipped
 

package/mindsystem/references/principles.md

@@ -54,7 +54,7 @@ No enterprise process. No approval gates.
 
 Plan → Execute → Ship → Learn → Repeat
 
-Milestones mark shipped versions (v1.0 → v1.1 → v2.0).
+Milestones mark shipped work (MVP → Push Notifications → ...).
 </ship_fast>
 
 <anti_enterprise>

package/mindsystem/references/routing/audit-result-routing.md

@@ -9,7 +9,8 @@ Route user to appropriate next action based on audit status (passed, gaps_found,
 ## Variables
 
 From calling context:
-- `{version}` — milestone version
+- `{name}` — milestone name
+- `{slug}` — milestone slug (for file paths)
 - `{N}/{M}` — requirements score
 - `{status}` — audit result: passed | gaps_found | tech_debt
 - `{assumptions_count}` — number of untested assumptions (from UAT)
@@ -21,10 +22,10 @@ Read the audit status and present the matching section below.
 ## If Passed
 
 ```markdown
-## ✓ Milestone {version} — Audit Passed
+## ✓ Milestone {name} — Audit Passed
 
 **Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+**Report:** .planning/MILESTONE-AUDIT.md
 
 All requirements covered. Cross-phase integration verified. E2E flows complete.
 
@@ -38,7 +39,7 @@ See full list in MILESTONE-AUDIT.md. Consider addressing in next milestone.
 
 ## ▶ Next Up
 
-`/ms:complete-milestone {version}` — archive and tag
+`/ms:complete-milestone` — archive milestone
 
 <sub>`/clear` first → fresh context window</sub>
 ```
@@ -46,10 +47,10 @@ See full list in MILESTONE-AUDIT.md. Consider addressing in next milestone.
 ## If Gaps Found
 
 ```markdown
-## ⚠ Milestone {version} — Gaps Found
+## ⚠ Milestone {name} — Gaps Found
 
 **Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+**Report:** .planning/MILESTONE-AUDIT.md
 
 ### Unsatisfied Requirements
 
@@ -78,17 +79,17 @@ See full list in MILESTONE-AUDIT.md. Consider addressing in next milestone.
 ---
 
 **Also available:**
-- `cat .planning/v{version}-MILESTONE-AUDIT.md` — see full report
-- `/ms:complete-milestone {version}` — proceed anyway (accept tech debt)
+- `cat .planning/MILESTONE-AUDIT.md` — see full report
+- `/ms:complete-milestone` — proceed anyway (accept tech debt)
 ```
 
 ## If Tech Debt (no blockers but accumulated debt)
 
 ```markdown
-## ⚡ Milestone {version} — Tech Debt Review
+## ⚡ Milestone {name} — Tech Debt Review
 
 **Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
+**Report:** .planning/MILESTONE-AUDIT.md
 
 All requirements met. No critical blockers. Accumulated tech debt needs review.
 
@@ -108,7 +109,7 @@ See full list in MILESTONE-AUDIT.md. Consider addressing in next milestone.
 
 ## ▶ Options
 
-- `/ms:complete-milestone {version}` — accept debt, track in backlog
+- `/ms:complete-milestone` — accept debt, track in backlog
 - `/ms:plan-milestone-gaps` — address debt before completing
 
 <sub>`/clear` first → fresh context window</sub>

package/mindsystem/references/routing/between-milestones-routing.md

@@ -15,14 +15,14 @@ cat .planning/MILESTONES.md 2>/dev/null
 ```
 
 Extract:
-- `{X.Y}` — last completed milestone version
+- `{name}` — last completed milestone name from MILESTONES.md
 
 ## Output Format
 
 ```markdown
 ---
 
-## ✓ Milestone v{X.Y} Complete
+## ✓ Milestone {name} Complete
 
 Ready to plan the next milestone.
 

package/mindsystem/references/routing/milestone-complete-routing.md

@@ -10,7 +10,7 @@ Celebrate milestone completion and guide user toward audit or archive.
 
 From calling context:
 - `{N}` — total number of phases in milestone
-- `{version}` — milestone version (if known)
+- `{name}` — milestone name (if known)
 
 ## Output Format
 

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

@@ -108,7 +108,7 @@ ELSE:
 
 ### Suggested
 
-`/ms:discuss-phase 3` — ambiguous user flow
+`/ms:discuss-phase 3` — assumes grid layout, unclear what metrics matter
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -130,17 +130,19 @@ ELSE:
 
 | Pre-work | Status | Topics/Focus |
 |----------|--------|--------------|
+| Discuss | Likely | assumes one-time payments only, unclear if subscriptions needed, refund policy unspecified |
 | Research | Likely | Stripe API, webhook handling, idempotency |
 
 ### Suggested
 
-`/ms:research-phase 4` — external API integration
+`/ms:discuss-phase 4` — assumes one-time payments, subscription model unclear
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
+- `/ms:research-phase 4` — external API integration
 - `/ms:plan-phase 4` — plan directly
 ```
 

package/mindsystem/templates/context.md

@@ -53,10 +53,10 @@ Template for `.planning/phases/XX-name/{phase}-CONTEXT.md` - captures the user's
 <decisions>
 ## Decisions (Locked)
 
-[Concrete implementation decisions made during discussion. These are NOT optional — plans must implement these exactly.]
+[Concrete implementation decisions made during discussion. These are NOT optional — plans must implement these exactly. Each decision includes inline reasoning grounded in vision, audience, or tradeoff analysis.]
 
-- [Decision 1]
-- [Decision 2]
+- [Decision 1] — [Why: grounded in vision, audience, or tradeoff]
+- [Decision 2] — [Reasoning from product analysis or user preference]
 
 ### Claude's Discretion
 
@@ -128,9 +128,9 @@ Priority is clarity over features. Better to show less and make it obvious than
 <decisions>
 ## Decisions (Locked)
 
-- Card layout for projects (not a list)
-- "Today" section at top showing urgent items
-- Dark mode support (already exists from Phase 2)
+- Card layout for projects (not a list) — Why: user wants personal feel, cards feel more like a notebook than enterprise software; Linear uses cards successfully for similar "what's mine" views
+- "Today" section at top showing urgent items — Why: at-a-glance clarity is the #1 essential; surfacing urgency immediately matches user's "what should I work on today" mental model
+- Dark mode support (already exists from Phase 2) — Why: user considers this essential for the calm aesthetic
 
 ### Claude's Discretion
 
@@ -173,6 +173,7 @@ Vision sections capture the user's own words — how they imagine it, what they
 - Concrete choices (not vague preferences)
 - Checkable by downstream agents
 - Clear about what's locked vs discretionary
+- Include inline reasoning ("— Why: ...") grounded in vision, audience needs, competitor patterns, or explicit tradeoff analysis
 
 **Content should NOT read like:**
 - A technical specification

package/mindsystem/templates/milestone-archive.md

@@ -6,7 +6,7 @@ This template is used by the complete-milestone workflow to create archive files
 
 ## File Template
 
-# Milestone v{{VERSION}}: {{MILESTONE_NAME}}
+# Milestone: {{MILESTONE_NAME}}
 
 **Status:** ✅ SHIPPED {{DATE}}
 **Phases:** {{PHASE_START}}-{{PHASE_END}}
@@ -97,13 +97,13 @@ _For current project status, see .planning/PROJECT.md_
 
 <guidelines>
 **When to create milestone archives:**
-- After completing all phases in a milestone (v1.0, v1.1, v2.0, etc.)
+- After completing all phases in a milestone
 - Triggered by complete-milestone workflow
 - Before planning next milestone work
 
 **How to fill template:**
 
-- Replace {{PLACEHOLDERS}} with actual values
+- Replace {{PLACEHOLDERS}} with actual values ({{MILESTONE_NAME}}, {{MILESTONE_SLUG}} for paths)
 - Extract phase details from ROADMAP.md
 - Document decimal phases with (INSERTED) marker
 - Include key decisions from PROJECT-STATE.md or SUMMARY files
@@ -112,8 +112,8 @@ _For current project status, see .planning/PROJECT.md_
 
 **Archive location:**
 
-- Save to `.planning/milestones/v{VERSION}/ROADMAP.md`
-- Example: `.planning/milestones/v1.0/ROADMAP.md`
+- Save to `.planning/milestones/{MILESTONE_SLUG}/ROADMAP.md`
+- Example: `.planning/milestones/mvp/ROADMAP.md`
 
 **After archiving:**
 

package/mindsystem/templates/milestone-context.md

@@ -5,7 +5,7 @@ Template for `.planning/MILESTONE-CONTEXT.md` — captures brainstorming context
 <template>
 
 ```markdown
-# Milestone Context: v[X.Y] [Name]
+# Milestone Context: [Name]
 
 **Generated:** [date]
 **Source:** /ms:new-milestone brainstorming session

package/mindsystem/templates/milestone.md

@@ -3,7 +3,7 @@
 Add this entry to `.planning/MILESTONES.md` when completing a milestone:
 
 ```markdown
-## v[X.Y] [Name] (Shipped: YYYY-MM-DD)
+## [Name] (Shipped: YYYY-MM-DD)
 
 **Delivered:** [One sentence describing what shipped]
 
@@ -40,9 +40,9 @@ If MILESTONES.md doesn't exist, create it with header:
 
 <guidelines>
 **When to create milestones:**
-- Initial v1.0 MVP shipped
-- Major version releases (v2.0, v3.0)
-- Significant feature milestones (v1.1, v1.2)
+- Initial MVP shipped
+- Major feature sets complete
+- Significant feature milestones
 - Before archiving planning (capture what was shipped)
 
 **Don't create milestones for:**
@@ -65,7 +65,7 @@ If MILESTONES.md doesn't exist, create it with header:
 ```markdown
 # Project Milestones: WeatherBar
 
-## v1.1 Security & Polish (Shipped: 2025-12-10)
+## Security & Polish (Shipped: 2025-12-10)
 
 **Delivered:** Security hardening with Keychain integration and comprehensive error handling
 
@@ -81,15 +81,15 @@ If MILESTONES.md doesn't exist, create it with header:
 - 23 files modified
 - 650 lines of Swift added
 - 2 phases, 3 plans, 12 tasks
-- 8 days from v1.0 to v1.1
+- 8 days
 
 **Git range:** `feat(05-01)` → `feat(06-02)`
 
-**What's next:** v2.0 SwiftUI redesign with widget support
+**What's next:** SwiftUI redesign with widget support
 
 ---
 
-## v1.0 MVP (Shipped: 2025-11-25)
+## MVP (Shipped: 2025-11-25)
 
 **Delivered:** Menu bar weather app with current conditions and 3-day forecast
 
@@ -110,6 +110,6 @@ If MILESTONES.md doesn't exist, create it with header:
 
 **Git range:** `feat(01-01)` → `feat(04-01)`
 
-**What's next:** Security audit and hardening for v1.1
+**What's next:** Security audit and hardening
 ```
 </example>

package/mindsystem/templates/project.md

@@ -115,7 +115,7 @@ Common types: Tech stack, Timeline, Budget, Dependencies, Compatibility, Perform
 
 **Validated:**
 - Requirements that shipped and proved valuable
-- Format: `- ✓ [Requirement] — [version/phase]`
+- Format: `- ✓ [Requirement] — [Milestone Name]`
 - These are locked — changing them requires explicit discussion
 
 **Key Decisions:**
@@ -128,7 +128,7 @@ Common types: Tech stack, Timeline, Budget, Dependencies, Compatibility, Perform
 
 **Last Updated:**
 - Always note when and why the document was updated
-- Format: `after Phase 2` or `after v1.0 milestone`
+- Format: `after Phase 2` or `after [Name] milestone`
 - Triggers review of whether content is still accurate
 
 </guidelines>

package/mindsystem/templates/research-subagent-prompt.md

@@ -33,8 +33,8 @@ Phase Research — External Documentation focus.
 <focus>
 Library documentation, APIs, version-specific behavior, verified code examples.
 Use the ms-lookup CLI for library docs and deep research:
-  ~/.claude/mindsystem/scripts/ms-lookup-wrapper.sh docs <library> '<query>'
-  ~/.claude/mindsystem/scripts/ms-lookup-wrapper.sh deep '<query>'
+  ms-lookup docs <library> '<query>'
+  ms-lookup deep '<query>'
 Use WebSearch for ecosystem discovery.
 Focus on finding authoritative, current documentation for the libraries and tools
 needed to implement this phase.
@@ -129,7 +129,7 @@ Phase Research — Best Practices & Community Consensus focus.
 <focus>
 Community consensus, common pitfalls, proven approaches, state of the art.
 Use the ms-lookup CLI for deep research on high-value questions:
-  ~/.claude/mindsystem/scripts/ms-lookup-wrapper.sh deep '<query>'
+  ms-lookup deep '<query>'
 Use WebSearch for community articles, blog posts, Stack Overflow patterns.
 Focus on what practitioners recommend and what mistakes to avoid.
 </focus>

package/mindsystem/templates/roadmap-milestone.md

@@ -7,14 +7,14 @@ Template for reorganizing `ROADMAP.md` after first milestone ships. Collapse com
 
 ## Milestones
 
-- ✅ **v1.0 MVP** - Phases 1-4 (shipped YYYY-MM-DD)
-- 🚧 **v1.1 [Name]** - Phases 5-6 (in progress)
-- 📋 **v2.0 [Name]** - Phases 7-10 (planned)
+- ✅ **MVP** - Phases 1-4 (shipped YYYY-MM-DD)
+- 🚧 **[Name]** - Phases 5-6 (in progress)
+- 📋 **[Name]** - Phases 7-10 (planned)
 
 ## Phases
 
 <details>
-<summary>✅ v1.0 MVP (Phases 1-4) - SHIPPED YYYY-MM-DD</summary>
+<summary>✅ MVP (Phases 1-4) - SHIPPED YYYY-MM-DD</summary>
 
 ### Phase 1: [Name]
 **Goal**: [What this phase delivers]
@@ -25,13 +25,13 @@ Plans:
 - [x] 01-02: [Brief description]
 - [x] 01-03: [Brief description]
 
-[... remaining v1.0 phases ...]
+[... remaining phases ...]
 
 </details>
 
-### 🚧 v1.1 [Name] (In Progress)
+### 🚧 [Name] (In Progress)
 
-**Milestone Goal:** [What v1.1 delivers]
+**Milestone Goal:** [What this milestone delivers]
 
 #### Phase 5: [Name]
 **Goal**: [What this phase delivers]
@@ -42,21 +42,21 @@ Plans:
 - [ ] 05-01: [Brief description]
 - [ ] 05-02: [Brief description]
 
-[... remaining v1.1 phases ...]
+[... remaining phases ...]
 
-### 📋 v2.0 [Name] (Planned)
+### 📋 [Name] (Planned)
 
-**Milestone Goal:** [What v2.0 delivers]
+**Milestone Goal:** [What this milestone delivers]
 
-[... v2.0 phases ...]
+[... phases ...]
 
 ## Progress
 
 | Phase | Milestone | Plans Complete | Status | Completed |
 |-------|-----------|----------------|--------|-----------|
-| 1. Foundation | v1.0 | 3/3 | Complete | YYYY-MM-DD |
-| 2. Features | v1.0 | 2/2 | Complete | YYYY-MM-DD |
-| 5. Security | v1.1 | 0/2 | Not started | - |
+| 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 | - |
 ```
 
 **Notes:**

package/mindsystem/templates/roadmap.md

@@ -2,7 +2,7 @@
 
 Template for `.planning/ROADMAP.md`.
 
-## Initial Roadmap (v1.0 Greenfield)
+## Initial Roadmap (Greenfield)
 
 ```markdown
 # Roadmap: [Project Name]
@@ -34,7 +34,7 @@ Decimal phases appear between their surrounding integers in numeric order.
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
   3. [Observable behavior from user perspective]
-**Discuss**: Unlikely (clear requirements)
+**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"]
@@ -51,7 +51,7 @@ Plans:
 **Success Criteria** (what must be TRUE):
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
-**Discuss**: Likely (ambiguous user flow)
+**Discuss**: Likely (assumes email/password only, unclear if social login needed, session duration unspecified)
 **Discuss topics**: [What to clarify]
 **Design**: Likely (significant new UI)
 **Design focus**: [What to design]
@@ -81,7 +81,8 @@ Plans:
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
   3. [Observable behavior from user perspective]
-**Discuss**: Unlikely (established patterns)
+**Discuss**: Likely (assumes standard REST patterns, error handling strategy unspecified, rate limiting approach unclear)
+**Discuss topics**: [Integration scope, error UX, retry behavior]
 **Design**: Unlikely (API only)
 **Research**: Likely (external API)
 **Research topics**: [What needs investigating]
@@ -98,7 +99,8 @@ Plans:
 **Success Criteria** (what must be TRUE):
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
-**Discuss**: Unlikely (clear requirements)
+**Discuss**: Likely (assumes priority ordering of requirements, unclear if batch processing needed, edge case handling unspecified)
+**Discuss topics**: [Priority rules, batch vs individual, error recovery]
 **Design**: Unlikely (backend only)
 **Research**: Unlikely (internal patterns)
 **Plans**: [Number of plans]
@@ -120,7 +122,7 @@ Phases execute in numeric order: 2 → 2.1 → 2.2 → 3 → 3.1 → 4
 ```
 
 <guidelines>
-**Initial planning (v1.0):**
+**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)
@@ -137,7 +139,7 @@ Phases execute in numeric order: 2 → 2.1 → 2.2 → 3 → 3.1 → 4
 - Format: "User can [action]" or "[Thing] works/exists"
 
 **Pre-work indicators** (all use Likely/Unlikely with parenthetical reason):
-- `Discuss` - Vision unknowns: ambiguous requirements, UX decisions, novel features
+- `Discuss` - Default Likely. Surfaces Claude's assumptions before planning. Unlikely only for fully mechanical zero-decision work (version bump, rename-only refactor, config-only change, pure deletion/cleanup). When Likely, rationale enumerates 2-4 phase-specific assumptions or open questions.
 - `Design` - Visual unknowns: significant new UI, novel interactions, multi-screen flows
 - `Research` - Technical unknowns: external APIs, new libraries, architectural decisions
 - Include topic/focus fields only when Likely

package/mindsystem/workflows/adhoc.md

@@ -381,7 +381,7 @@ Generate patch file from the adhoc commit:
 ```bash
 patch_file=".planning/adhoc/${timestamp}-${slug}.patch"
 
-~/.claude/mindsystem/scripts/generate-adhoc-patch.sh "$commit_hash" "$patch_file"
+ms-tools generate-adhoc-patch "$commit_hash" "$patch_file"
 ```
 
 If patch generated (file exists and non-empty):