maxsimcli 1.0.10 → 1.0.11

package/dist/assets/CHANGELOG.md

@@ -1,3 +1,16 @@
+## 1.0.11 (2026-02-24)
+
+### 🚀 Features
+
+- **core:** add chalk dependency and phase-bars format to cmdProgressRender ([121f17c](https://github.com/maystudios/maxsim/commit/121f17c))
+- **templates:** add /maxsim:roadmap command and workflow ([372c8a3](https://github.com/maystudios/maxsim/commit/372c8a3))
+- **templates:** update progress workflow to use phase-bars format ([c9672ee](https://github.com/maystudios/maxsim/commit/c9672ee))
+- **templates:** add sanity_check guard to five major workflow files ([fca2b19](https://github.com/maystudios/maxsim/commit/fca2b19))
+
+### ❤️ Thank You
+
+- Sven
+
 ## 1.0.10 (2026-02-24)
 
 This was a version bump only, there were no code changes.

package/dist/assets/templates/commands/maxsim/roadmap.md

@@ -0,0 +1,19 @@
+---
+name: maxsim:roadmap
+description: Display the project roadmap with phase status icons, plan counts, and milestone summary
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+---
+<objective>
+Render the project roadmap in a human-readable format with phase status icons (✓ DONE, ► IN PROGRESS, □ PLANNED), plan progress counts per phase, and a milestone summary header.
+</objective>
+
+<execution_context>
+@./workflows/roadmap.md
+</execution_context>
+
+<process>
+Execute the roadmap workflow from @./workflows/roadmap.md end-to-end.
+</process>

package/dist/assets/templates/workflows/discuss-phase.md

@@ -1,3 +1,9 @@
+<sanity_check>
+Before executing any step in this workflow, verify:
+1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:new-project` first.
+2. `.planning/ROADMAP.md` exists — if not, stop and tell the user to initialize the project.
+</sanity_check>
+
 <purpose>
 Extract implementation decisions that downstream agents need. Analyze the phase to identify gray areas, let the user choose what to discuss, then deep-dive each selected area until satisfied.
 

package/dist/assets/templates/workflows/execute-phase.md

@@ -1,3 +1,9 @@
+<sanity_check>
+Before executing any step in this workflow, verify:
+1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:new-project` first.
+2. `.planning/ROADMAP.md` exists — if not, stop and tell the user to initialize the project.
+</sanity_check>
+
 <purpose>
 Execute all plans in a phase using wave-based parallel execution. Orchestrator stays lean — delegates plan execution to subagents.
 </purpose>

package/dist/assets/templates/workflows/plan-phase.md

@@ -1,3 +1,9 @@
+<sanity_check>
+Before executing any step in this workflow, verify:
+1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:new-project` first.
+2. `.planning/ROADMAP.md` exists — if not, stop and tell the user to initialize the project.
+</sanity_check>
+
 <purpose>
 Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification. Default flow: Research (if needed) -> Plan -> Verify -> Done. Orchestrates maxsim-phase-researcher, maxsim-planner, and maxsim-plan-checker agents with a revision loop (max 3 iterations).
 </purpose>

package/dist/assets/templates/workflows/progress.md

@@ -88,7 +88,7 @@ Use this instead of manually reading/parsing ROADMAP.md.
 
 ```bash
 # Get formatted progress bar
-PROGRESS_BAR=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs progress bar --raw)
+PROGRESS_BAR=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs progress phase-bars --raw)
 ```
 
 Present:

package/dist/assets/templates/workflows/quick.md

@@ -1,3 +1,9 @@
+<sanity_check>
+Before executing any step in this workflow, verify:
+1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:new-project` first.
+2. `.planning/ROADMAP.md` exists — if not, stop and tell the user to initialize the project.
+</sanity_check>
+
 <purpose>
 Execute small, ad-hoc tasks with MAXSIM guarantees (atomic commits, STATE.md tracking). Quick mode spawns maxsim-planner (quick mode) + maxsim-executor(s), tracks tasks in `.planning/quick/`, and updates STATE.md's "Quick Tasks Completed" table.
 

package/dist/assets/templates/workflows/roadmap.md

@@ -0,0 +1,81 @@
+<purpose>
+Render the project roadmap in a readable format with phase status icons and plan progress counts. Read-only — does not modify any files.
+</purpose>
+
+<process>
+
+<step name="check_planning">
+Verify the project is initialized:
+
+```bash
+INIT=$(node ./.claude/maxsim/bin/maxsim-tools.cjs state-load --raw)
+```
+
+Parse JSON. If `planning_exists` is false, hard stop:
+
+> No roadmap found. Run /maxsim:new-project to initialize.
+
+Exit immediately. Do not continue.
+</step>
+
+<step name="analyze">
+Load roadmap analysis:
+
+```bash
+ROADMAP=$(node ./.claude/maxsim/bin/maxsim-tools.cjs roadmap analyze)
+```
+
+Parse JSON for: `phases[]` (each with `number`, `name`, `disk_status`, `plan_count`, `summary_count`), `milestone_name`, `milestone_version`.
+
+Count phases by status:
+- `done_count` = phases where `disk_status === 'complete'`
+- `active_count` = phases where `disk_status === 'partial'`
+- `planned_count` = phases where `disk_status === 'planned' || disk_status === 'empty' || disk_status === 'discussed' || disk_status === 'researched' || disk_status === 'no_directory'`
+</step>
+
+<step name="render">
+Print the roadmap to the terminal.
+
+**Milestone header line:**
+```
+{milestone_name} — {done_count} done / {active_count} active / {planned_count} planned
+```
+
+**Blank line.**
+
+**Per-phase lines (in numeric order):**
+
+For each phase in `phases[]`:
+- `disk_status === 'complete'` → icon `✓`, label `DONE`
+- `disk_status === 'partial'` → icon `►`, label `IN PROGRESS`
+- `disk_status === 'planned' || 'empty' || 'discussed' || 'researched' || 'no_directory'` → icon `□`, label `PLANNED`
+
+Format per line:
+```
+{icon}  Phase {number}: {name}    {label}  ({summary_count}/{plan_count} plans)
+```
+
+Pad phase names with spaces so status labels align in a column.
+
+Only show `({summary_count}/{plan_count} plans)` when `plan_count > 0`.
+
+Example output:
+```
+NX Monorepo Migration — 5 done / 1 active / 6 planned
+
+✓  Phase 01: NX Workspace Scaffold                    DONE       (4/4 plans)
+✓  Phase 02: packages/core TypeScript Port            DONE       (6/6 plans)
+►  Phase 09: End-to-end install and publish test loop IN PROGRESS (2/3 plans)
+□  Phase 11: Remove Discord command                   PLANNED
+□  Phase 12: UX Polish + Core Hardening               PLANNED
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Milestone summary header rendered with done/active/planned counts
+- [ ] All phases listed in numeric order with correct icon and label
+- [ ] Plan progress shown inline for phases that have plans
+- [ ] Hard stop if .planning/ is missing
+</success_criteria>

package/dist/assets/templates/workflows/verify-phase.md

@@ -1,3 +1,9 @@
+<sanity_check>
+Before executing any step in this workflow, verify:
+1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:new-project` first.
+2. `.planning/ROADMAP.md` exists — if not, stop and tell the user to initialize the project.
+</sanity_check>
+
 <purpose>
 Verify phase goal achievement through goal-backward analysis. Check that the codebase delivers what the phase promised, not just that tasks completed.