mindsystem-cc 3.17.0 → 3.17.1

package/agents/ms-roadmapper.md

@@ -214,25 +214,12 @@ For each phase, analyze whether pre-work would reduce risk before planning. Thre
 
 | Pre-Work | Question It Answers | Command |
 |----------|---------------------|---------|
-| **Research** | "Do I know HOW to build this?" | `/ms:research-phase` |
 | **Discussion** | "Do I understand WHAT the user wants?" | `/ms:discuss-phase` |
 | **Design** | "Do I know what this should LOOK like?" | `/ms:design-phase` |
+| **Research** | "Do I know HOW to build this?" | `/ms:research-phase` |
 
 All use binary Likely/Unlikely with parenthetical reason. These are hints to users, not mandates.
 
-### Research Indicators
-
-**Likely when ANY of:**
-- External APIs or services involved
-- New libraries/frameworks to learn
-- Architectural decisions not yet made
-- Technical approach unclear
-
-**Unlikely when ALL of:**
-- Using established internal patterns
-- CRUD operations with known stack
-- Well-documented conventions exist
-
 ### Discussion Indicators
 
 **Problem it solves:** User's mental model isn't documented. Planning happens without understanding what's essential vs nice-to-have.
@@ -266,6 +253,19 @@ All use binary Likely/Unlikely with parenthetical reason. These are hints to use
 - Infrastructure, testing, deployment phases
 - Uses established UI patterns exclusively
 
+### Research Indicators
+
+**Likely when ANY of:**
+- External APIs or services involved
+- New libraries/frameworks to learn
+- Architectural decisions not yet made
+- Technical approach unclear
+
+**Unlikely when ALL of:**
+- Using established internal patterns
+- CRUD operations with known stack
+- Well-documented conventions exist
+
 **Note:** Discussion and Design often overlap for UI-facing phases. This is intentional — they serve different purposes (vision vs specification) and a phase may benefit from both.
 
 ### Output Format
@@ -273,12 +273,12 @@ All use binary Likely/Unlikely with parenthetical reason. These are hints to use
 For each phase in ROADMAP.md:
 
 ```markdown
-**Research**: Likely (external API) | Unlikely (established patterns)
-**Research topics**: [What needs investigating] (only if Likely)
 **Discuss**: Likely (ambiguous user flow) | Unlikely (clear requirements)
 **Discuss topics**: [What to clarify] (only if Likely)
 **Design**: Likely (significant new UI) | Unlikely (backend only)
 **Design focus**: [What to design] (only if Likely)
+**Research**: Likely (external API) | Unlikely (established patterns)
+**Research topics**: [What needs investigating] (only if Likely)
 ```
 
 </pre_work_analysis>
@@ -461,11 +461,11 @@ When presenting to user for approval:
 
 ### Pre-Work Recommendations
 
-| Phase | Research | Discuss | Design |
-|-------|----------|---------|--------|
+| Phase | Discuss | Design | Research |
+|-------|---------|--------|----------|
 | 1 - Setup | Unlikely | Unlikely | Unlikely |
-| 2 - Auth | Likely | Likely | Unlikely |
-| 3 - Content | Unlikely | Likely | Likely |
+| 2 - Auth | Likely | Unlikely | Likely |
+| 3 - Content | Likely | Likely | Unlikely |
 
 **Phase 2 topics:**
 - Research: [external auth providers]
@@ -601,8 +601,8 @@ When files are written and returning to orchestrator:
 
 ### Pre-Work Recommendations
 
-| Phase | Research | Discuss | Design |
-|-------|----------|---------|--------|
+| Phase | Discuss | Design | Research |
+|-------|---------|--------|----------|
 | 1 - {name} | {Likely/Unlikely} | {Likely/Unlikely} | {Likely/Unlikely} |
 | 2 - {name} | {Likely/Unlikely} | {Likely/Unlikely} | {Likely/Unlikely} |
 

package/commands/ms/audit-milestone.md

@@ -328,9 +328,7 @@ Plans:
 
 ## ▶ Next Up
 
-**Plan the quality phase**
-
-`/ms:plan-phase {N}`
+`/ms:plan-phase {N}` — plan the quality phase
 
 <sub>`/clear` first → fresh context window</sub>
 ```

package/commands/ms/new-milestone.md

@@ -266,15 +266,13 @@ Milestone name: $ARGUMENTS (optional — will emerge during discovery if not pro
 
     ## ▶ Next Up
 
-    **[Recommended command]** — [one-line reason from conversation]
-
-    `/ms:[recommended-command]`
+    `/ms:[recommended-command]` — [one-line reason from conversation]
 
     <sub>`/clear` first → fresh context window</sub>
 
     ---
 
-    **Also available:** `/ms:[alternative-command]`
+    **Also available:** `/ms:[alternative-command]` — [brief reason]
 
     ---
     ```

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

@@ -176,9 +176,7 @@ git commit -m "docs(roadmap): add gap closure phases {N}-{M}"
 
 ## ▶ Next Up
 
-**Plan first gap closure phase**
-
-`/ms:plan-phase {N}`
+`/ms:plan-phase {N}` — plan first gap closure phase
 
 <sub>`/clear` first → fresh context window</sub>
 

package/commands/ms/research-project.md

@@ -335,9 +335,9 @@ Key findings:
 - Critical pitfall: [one-liner]
 
 ---
-## > Next Up
-**Define requirements and create roadmap** - `/ms:create-roadmap`
-<sub>`/clear` first</sub>
+## ▶ Next Up
+`/ms:create-roadmap` — define requirements and create roadmap
+<sub>`/clear` first → fresh context window</sub>
 ---
 ```
 

package/mindsystem/references/continuation-format.md

@@ -9,9 +9,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 ## ▶ Next Up
 
-**{identifier}: {name}** — {one-line description}
-
-`{command to copy-paste}`
+`{command to copy-paste}` — {one-line description}
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -24,14 +22,23 @@ Standard format for presenting next steps after completing a command or workflow
 ---
 ```
 
+When there's meaningful additional context (like a phase identifier), add it as a header line:
+
+```
+**Phase {N}: {Name}** — {Goal}
+
+`/ms:plan-phase {N}`
+```
+
 ## Format Rules
 
-1. **Always show what it is** — name + description, never just a command path
-2. **Pull context from source** — ROADMAP.md for phases, PLAN.md `<objective>` for plans
-3. **Command in inline code** — backticks, easy to copy-paste, renders as clickable link
-4. **`/clear` explanation** — always include, keeps it concise but explains why
-5. **"Also available" not "Other options"** — sounds more app-like
-6. **Visual separators** — `---` above and below to make it stand out
+1. **Command is the anchor** — backtick command + description on one line, no separate bold label restating the command name
+2. **Phase identifiers are additive context** — `**Phase 2: Auth**` carries info the command doesn't; bold labels like `**Plan gap closure**` just restate `/ms:plan-phase --gaps` and should be omitted
+3. **Pull context from source** — ROADMAP.md for phases, PLAN.md `<objective>` for plans
+4. **Command in inline code** — backticks, easy to copy-paste, renders as clickable link
+5. **`/clear` explanation** — always include, keeps it concise but explains why
+6. **"Also available" not "Other options"** — sounds more app-like
+7. **Visual separators** — `---` above and below to make it stand out
 
 ## Variants
 
@@ -167,9 +174,7 @@ All 4 phases shipped
 
 ## ▶ Next Up
 
-**Start v1.1** — discover what to build next
-
-`/ms:new-milestone`
+`/ms:new-milestone` — discover what to build next
 
 <sub>`/clear` first → fresh context window</sub>
 

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

@@ -38,9 +38,7 @@ See full list in MILESTONE-AUDIT.md. Consider addressing in next milestone.
 
 ## ▶ Next Up
 
-**Complete milestone** — archive and tag
-
-`/ms:complete-milestone {version}`
+`/ms:complete-milestone {version}` — archive and tag
 
 <sub>`/clear` first → fresh context window</sub>
 ```
@@ -73,9 +71,7 @@ See full list in MILESTONE-AUDIT.md. Consider addressing in next milestone.
 
 ## ▶ Next Up
 
-**Plan gap closure** — create phases to complete milestone
-
-`/ms:plan-milestone-gaps`
+`/ms:plan-milestone-gaps` — create phases to complete milestone
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -112,13 +108,8 @@ See full list in MILESTONE-AUDIT.md. Consider addressing in next milestone.
 
 ## ▶ Options
 
-**A. Complete milestone** — accept debt, track in backlog
-
-`/ms:complete-milestone {version}`
-
-**B. Plan cleanup phase** — address debt before completing
-
-`/ms:plan-milestone-gaps`
+- `/ms:complete-milestone {version}` — 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

@@ -28,9 +28,7 @@ Ready to plan the next milestone.
 
 ## ▶ Next Up
 
-**Start Next Milestone** — discover what to build, update PROJECT.md
-
-`/ms:new-milestone`
+`/ms:new-milestone` — discover what to build, update PROJECT.md
 
 <sub>`/clear` first → fresh context window</sub>
 

package/mindsystem/references/routing/gap-closure-routing.md

@@ -46,9 +46,7 @@ Extract:
 
 ## ▶ Next Up
 
-**Plan gap closure** — create additional plans to complete the phase
-
-`/ms:plan-phase {Z} --gaps`
+`/ms:plan-phase {Z} --gaps` — create additional plans to complete the phase
 
 <sub>`/clear` first → fresh context window</sub>
 

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

@@ -23,9 +23,7 @@ All {N} phases finished!
 
 ## ▶ Next Up
 
-**Audit milestone** — verify requirements, cross-phase integration, E2E flows
-
-`/ms:audit-milestone`
+`/ms:audit-milestone` — verify requirements, cross-phase integration, E2E flows
 
 <sub>`/clear` first → fresh context window</sub>
 

package/mindsystem/templates/roadmap.md

@@ -34,9 +34,9 @@ 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]
-**Research**: Unlikely (established patterns)
 **Discuss**: Unlikely (clear requirements)
 **Design**: Unlikely (backend only)
+**Research**: Unlikely (established patterns)
 **Plans**: [Number of plans, e.g., "3 plans" or "TBD"]
 
 Plans:
@@ -51,12 +51,12 @@ Plans:
 **Success Criteria** (what must be TRUE):
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
-**Research**: Likely (new integration)
-**Research topics**: [What needs investigating]
 **Discuss**: Likely (ambiguous user flow)
 **Discuss topics**: [What to clarify]
 **Design**: Likely (significant new UI)
 **Design focus**: [What to design]
+**Research**: Likely (new integration)
+**Research topics**: [What needs investigating]
 **Plans**: [Number of plans]
 
 Plans:
@@ -81,10 +81,10 @@ Plans:
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
   3. [Observable behavior from user perspective]
-**Research**: Likely (external API)
-**Research topics**: [What needs investigating]
 **Discuss**: Unlikely (established patterns)
 **Design**: Unlikely (API only)
+**Research**: Likely (external API)
+**Research topics**: [What needs investigating]
 **Plans**: [Number of plans]
 
 Plans:
@@ -98,9 +98,9 @@ Plans:
 **Success Criteria** (what must be TRUE):
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
-**Research**: Unlikely (internal patterns)
 **Discuss**: Unlikely (clear requirements)
 **Design**: Unlikely (backend only)
+**Research**: Unlikely (internal patterns)
 **Plans**: [Number of plans]
 
 Plans:
@@ -137,9 +137,9 @@ 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):
-- `Research` - Technical unknowns: external APIs, new libraries, architectural decisions
 - `Discuss` - Vision unknowns: ambiguous requirements, UX decisions, novel features
 - `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
 - Indicators are hints, not mandates - validate at planning time
 - UI-facing phases often need both Discuss and Design (this is intentional)

package/mindsystem/workflows/complete-milestone.md

@@ -734,9 +734,7 @@ Tag: v[X.Y]
 
 ## ▶ Next Up
 
-**Start Next Milestone** — define goals and requirements
-
-`/ms:new-milestone`
+`/ms:new-milestone` — define goals and requirements
 
 <sub>`/clear` first → fresh context window</sub>
 

package/mindsystem/workflows/define-requirements.md

@@ -289,9 +289,7 @@ Requirements defined:
 
 ## ▶ Next Up
 
-**Create roadmap** — phases mapped to requirements
-
-`/ms:create-roadmap`
+`/ms:create-roadmap` — phases mapped to requirements
 
 <sub>`/clear` first → fresh context window</sub>
 

package/mindsystem/workflows/diagnose-issues.md

@@ -181,9 +181,7 @@ Debug sessions: ${DEBUG_DIR}/
 
 ## Next Up
 
-**Plan fixes** — create fix plans from diagnosed gaps
-
-`/ms:plan-phase {phase} --gaps`
+`/ms:plan-phase {phase} --gaps` — create fix plans from diagnosed gaps
 
 `/clear` first for fresh context window
 

package/mindsystem/workflows/execute-phase.md

@@ -386,9 +386,7 @@ Present gaps and offer next command:
 
 ## ▶ Next Up
 
-**Plan gap closure** — create additional plans to complete the phase
-
-`/ms:plan-phase {X} --gaps`
+`/ms:plan-phase {X} --gaps` — create additional plans to complete the phase
 
 <sub>`/clear` first → fresh context window</sub>
 

package/mindsystem/workflows/map-codebase.md

@@ -271,9 +271,7 @@ Created .planning/codebase/:
 
 ## ▶ Next Up
 
-**Initialize project** — use codebase context for planning
-
-`/ms:new-project`
+`/ms:new-project` — use codebase context for planning
 
 <sub>`/clear` first → fresh context window</sub>
 

package/mindsystem/workflows/plan-phase.md

@@ -213,9 +213,7 @@ Also create or update EXECUTION-ORDER.md to include gap closure plans (typically
 
 ## ▶ Next Up
 
-**Execute gap closure plans**
-
-`/ms:execute-phase {X}`
+`/ms:execute-phase {X}` — execute gap closure plans
 
 <sub>`/clear` first → fresh context window</sub>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mindsystem-cc",
-  "version": "3.17.0",
+  "version": "3.17.1",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
   "bin": {
     "mindsystem-cc": "bin/install.js"