maxsimcli 5.0.2 → 5.0.4

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

@@ -8,7 +8,7 @@ Before executing any step in this workflow, verify:
 Thin orchestrator for the /maxsim:execute state machine. Detects the current state of a phase (already done, needs verification, needs execution), delegates per-plan execution to execute-plan.md subagents, runs auto-verification, and handles retry with gap closure.
 
 This file is the ORCHESTRATOR ONLY. Per-plan execution logic lives in:
-- @./workflows/execute-plan.md (per-plan subagent execution)
+- @~/.claude/maxsim/workflows/execute-plan.md (per-plan subagent execution)
 
 Verification is handled inline (spawning verifier agent) since it is a stage of this workflow, not a separate command.
 </purpose>
@@ -213,10 +213,10 @@ Execute each wave in sequence. Within a wave: parallel if `parallelization` is t
        </objective>
 
        <execution_context>
-       @./workflows/execute-plan.md
-       @./templates/summary.md
-       @./references/checkpoints.md
-       @./references/tdd.md
+       @~/.claude/maxsim/workflows/execute-plan.md
+       @~/.claude/maxsim/templates/summary.md
+       @~/.claude/maxsim/references/checkpoints.md
+       @~/.claude/maxsim/references/tdd.md
        </execution_context>
 
        <github_context>

package/dist/assets/templates/workflows/init-existing.md

@@ -6,8 +6,8 @@ Output: `.planning/` directory with config.json, PROJECT.md, REQUIREMENTS.md, RO
 
 <required_reading>
 Read all files referenced by the invoking prompt's execution_context before starting.
-@./references/thinking-partner.md
-@./references/questioning.md
+@~/.claude/maxsim/references/thinking-partner.md
+@~/.claude/maxsim/references/questioning.md
 </required_reading>
 
 <auto_mode>

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

@@ -1,10 +1,10 @@
 <purpose>
 
 Unified initialization router. Detects the current project state and delegates to the appropriate sub-workflow:
-- **New project** (no .planning/) -> delegates to @./workflows/new-project.md
-- **Existing project** (.planning/ exists, no ROADMAP.md) -> delegates to @./workflows/init-existing.md
+- **New project** (no .planning/) -> delegates to @~/.claude/maxsim/workflows/new-project.md
+- **Existing project** (.planning/ exists, no ROADMAP.md) -> delegates to @~/.claude/maxsim/workflows/init-existing.md
 - **Active milestone** (.planning/ + ROADMAP.md, phases in progress) -> shows status, offers options
-- **Milestone complete** (all phases done) -> offers completion or new milestone via @./workflows/new-milestone.md
+- **Milestone complete** (all phases done) -> offers completion or new milestone via @~/.claude/maxsim/workflows/new-milestone.md
 
 This file is a THIN ROUTER. All heavy logic lives in the sub-workflows.
 
@@ -81,7 +81,7 @@ echo "$INIT_CONTEXT"
 
 Save this JSON output — the sub-workflow will use it as `INIT_CONTEXT` and skip its own init call.
 
-Now delegate to @./workflows/new-project.md — execute the full new-project workflow end-to-end. The `INIT_CONTEXT` JSON is already loaded; the sub-workflow will detect this and skip Step 1's CLI call.
+Now delegate to @~/.claude/maxsim/workflows/new-project.md — execute the full new-project workflow end-to-end. The `INIT_CONTEXT` JSON is already loaded; the sub-workflow will detect this and skip Step 1's CLI call.
 
 Pass through:
 - `--auto` flag if set
@@ -114,7 +114,7 @@ echo "$INIT_CONTEXT"
 
 Save this JSON output — the sub-workflow will use it as `INIT_CONTEXT` and skip its own init call.
 
-Now delegate to @./workflows/init-existing.md — execute the full init-existing workflow end-to-end. The `INIT_CONTEXT` JSON is already loaded; the sub-workflow will detect this and skip Step 1's CLI call.
+Now delegate to @~/.claude/maxsim/workflows/init-existing.md — execute the full init-existing workflow end-to-end. The `INIT_CONTEXT` JSON is already loaded; the sub-workflow will detect this and skip Step 1's CLI call.
 
 Pass through:
 - `--auto` flag if set
@@ -159,7 +159,7 @@ Then present options conversationally (natural language, not AskUserQuestion):
    - If verification is pending: "Verify the current phase"
 
 2. **Start a new milestone** -- If the user wants to pivot or start fresh:
-   - Delegate to @./workflows/new-milestone.md for the milestone creation flow
+   - Delegate to @~/.claude/maxsim/workflows/new-milestone.md for the milestone creation flow
 
 3. **View detailed progress** -- Direct to `/maxsim:progress` for full status
 
@@ -189,12 +189,12 @@ Then present options conversationally:
 **Options:**
 
 1. **Complete and archive this milestone** -- Run the milestone completion flow:
-   - Delegate to @./workflows/new-milestone.md with completion mode
+   - Delegate to @~/.claude/maxsim/workflows/new-milestone.md with completion mode
    - Archives current milestone data
    - Updates MILESTONES.md with summary
 
 2. **Start a new milestone** -- Begin the next cycle:
-   - Delegate to @./workflows/new-milestone.md for creation flow
+   - Delegate to @~/.claude/maxsim/workflows/new-milestone.md for creation flow
    - Gathers new milestone goals
    - Creates fresh REQUIREMENTS.md and ROADMAP.md
 

package/dist/assets/templates/workflows/new-project.md

@@ -4,8 +4,8 @@ Initialize a new project through unified flow: questioning, research (optional),
 
 <required_reading>
 Read all files referenced by the invoking prompt's execution_context before starting.
-@./references/thinking-partner.md
-@./references/questioning.md
+@~/.claude/maxsim/references/thinking-partner.md
+@~/.claude/maxsim/references/questioning.md
 </required_reading>
 
 <auto_mode>

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

@@ -7,7 +7,7 @@ You are a thinking partner, not an interviewer. The user is the visionary -- you
 </purpose>
 
 <required_reading>
-@./references/thinking-partner.md
+@~/.claude/maxsim/references/thinking-partner.md
 </required_reading>
 
 <downstream_awareness>

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

@@ -8,9 +8,9 @@ Before executing any step in this workflow, verify:
 Thin orchestrator for the /maxsim:plan state machine. Detects the current stage of a phase (Discussion, Research, Planning), delegates to stage sub-workflows, shows gate confirmations between stages, and handles re-entry on already-planned phases.
 
 This file is the ORCHESTRATOR ONLY. Stage-specific logic lives in:
-- @./workflows/plan-discuss.md (Discussion stage)
-- @./workflows/plan-research.md (Research stage)
-- @./workflows/plan-create.md (Planning stage)
+- @~/.claude/maxsim/workflows/plan-discuss.md (Discussion stage)
+- @~/.claude/maxsim/workflows/plan-research.md (Research stage)
+- @~/.claude/maxsim/workflows/plan-create.md (Planning stage)
 </purpose>
 
 <process>
@@ -97,7 +97,7 @@ Wait for user choice via natural conversation.
 
 Delegate to the discussion sub-workflow for full discussion logic:
 
-@./workflows/plan-discuss.md
+@~/.claude/maxsim/workflows/plan-discuss.md
 
 Pass context: `phase_number`, `phase_name`, `phase_dir`, `padded_phase`, `phase_slug`, `commit_docs`, `roadmap_path`, `state_path`, `phase_issue_number`.
 
@@ -132,7 +132,7 @@ Wait for user response via natural conversation (not AskUserQuestion).
 
 Delegate to the research sub-workflow:
 
-@./workflows/plan-research.md
+@~/.claude/maxsim/workflows/plan-research.md
 
 Pass context: `phase_number`, `phase_name`, `phase_dir`, `padded_phase`, `phase_slug`, `commit_docs`, `researcher_model`, `research_enabled`, `has_research`, `state_path`, `roadmap_path`, `requirements_path`, `context_path`, `phase_req_ids`, `phase_issue_number`. Also pass the `--force-research` flag if present in $ARGUMENTS.
 
@@ -164,7 +164,7 @@ Wait for user response via natural conversation.
 
 Delegate to the planning sub-workflow:
 
-@./workflows/plan-create.md
+@~/.claude/maxsim/workflows/plan-create.md
 
 Pass context: `phase_number`, `phase_name`, `phase_dir`, `padded_phase`, `phase_slug`, `commit_docs`, `planner_model`, `checker_model`, `plan_checker_enabled`, `state_path`, `roadmap_path`, `requirements_path`, `context_path`, `research_path`, `phase_req_ids`, `phase_issue_number`. Also pass the `--skip-verify` flag if present in $ARGUMENTS.
 

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

@@ -588,10 +588,9 @@ Ready for next task: /maxsim:quick
 
 ```bash
 INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs init todos)
-mkdir -p .planning/todos/pending .planning/todos/done
 ```
 
-Extract from init JSON: `todo_count`, `todos`, `pending_dir`, `date`, `timestamp`, `github_ready`.
+Extract from init JSON: `todo_count`, `todos`, `date`, `timestamp`, `github_ready`.
 
 ---
 
@@ -646,38 +645,14 @@ If user provided a description:
 
 1. Parse priority from description (look for HIGH/MEDIUM/LOW keywords, default MEDIUM)
 2. Infer area from file paths mentioned or conversation context (default "general")
-3. Generate slug: `slug=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs generate-slug "$TITLE" --raw)`
-4. Create todo file at `.planning/todos/pending/${date}-${slug}.md`:
-
-```markdown
----
-created: [timestamp]
-title: [title]
-area: [area]
-priority: [HIGH/MEDIUM/LOW]
-mode: quick
-files: []
----
-
-## Problem
-
-[description - enough context for future Claude to understand]
-
-## Solution
-
-TBD
-```
-
-5. GitHub Issue creation (primary):
+3. Create GitHub Issue (primary action):
    - Run `github add-todo` with title, priority, area, and description to create a tracked GitHub Issue (label: "todo")
-   - If GitHub is unavailable, fall back to local file only and warn user: "Todo saved locally. Run `/maxsim:init` to enable GitHub tracking."
+   - If GitHub is unavailable, warn user: "GitHub unavailable. Run `/maxsim:init` to enable GitHub tracking."
 
    ```bash
    node ~/.claude/maxsim/bin/maxsim-tools.cjs github add-todo --title "${TITLE}" --description "${DESCRIPTION}" --area "${AREA}"
    ```
-6. Local file cache: also create the local todo file for offline access
-7. Commit: `node ~/.claude/maxsim/bin/maxsim-tools.cjs commit "docs: capture todo - ${TITLE}" --files .planning/todos/pending/${date}-${slug}.md`
-8. Confirm: "Saved: ${TITLE} (priority: ${PRIORITY}) — GitHub Issue #{number}"
+4. Confirm: "Saved: ${TITLE} (priority: ${PRIORITY}) — GitHub Issue #{number}"
 
 Exit after confirm.
 
@@ -688,14 +663,12 @@ Exit after confirm.
 If user references an existing todo to complete:
 
 1. Parse identifier (number from list, or title fragment)
-2. Close the corresponding GitHub Issue (primary): run `github close-issue` with the todo's issue number
+2. Close the corresponding GitHub Issue: run `github close-issue` with the todo's issue number
 
    ```bash
    node ~/.claude/maxsim/bin/maxsim-tools.cjs github close-issue N
    ```
-3. Move local cache file: `mv ".planning/todos/pending/[filename]" ".planning/todos/done/"`
-4. Commit: `node ~/.claude/maxsim/bin/maxsim-tools.cjs commit "docs: complete todo - ${TITLE}" --files .planning/todos/done/${filename}`
-5. Confirm: "Completed: ${TITLE} — GitHub Issue closed"
+3. Confirm: "Completed: ${TITLE} — GitHub Issue closed"
 
 Exit after confirm.
 
@@ -753,8 +726,7 @@ Exit after display.
 **Todo Mode:**
 - [ ] `--todo` flag or trigger words detected
 - [ ] Todo action determined (list/capture/complete/triage)
-- [ ] (capture) Todo file created with valid frontmatter
-- [ ] (capture) Best-effort GitHub Issue creation attempted
-- [ ] (complete) Todo moved from pending to done
+- [ ] (capture) GitHub Issue created with todo label
+- [ ] (complete) GitHub Issue closed
 - [ ] (triage) Prioritized view with phase context shown
 </success_criteria>

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

@@ -8,14 +8,14 @@ Standalone research command. For most workflows, use `/maxsim:plan` which integr
 
 ## Step 0: Resolve Model Profile
 
-@./references/model-profile-resolution.md
+@~/.claude/maxsim/references/model-profile-resolution.md
 
 Resolve model for:
 - `researcher`
 
 ## Step 1: Normalize and Validate Phase
 
-@./references/phase-argument-parsing.md
+@~/.claude/maxsim/references/phase-argument-parsing.md
 
 ```bash
 PHASE_INFO=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs roadmap get-phase "${PHASE}")

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

@@ -24,8 +24,8 @@ Then verify each level against the actual codebase.
 </core_principle>
 
 <required_reading>
-@./references/verification-patterns.md
-@./templates/verification-report.md
+@~/.claude/maxsim/references/verification-patterns.md
+@~/.claude/maxsim/templates/verification-report.md
 </required_reading>
 
 <process>

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

@@ -18,7 +18,7 @@ No Pass/Fail buttons. No severity questions. Just: "Here's what should happen. D
 </required_reading>
 
 <template>
-@./templates/UAT.md
+@~/.claude/maxsim/templates/UAT.md
 </template>
 
 <process>
@@ -337,7 +337,7 @@ Spawning parallel debug agents to investigate each issue.
 ```
 
 - Load diagnose-issues workflow
-- Follow @./workflows/diagnose-issues.md
+- Follow @~/.claude/maxsim/workflows/diagnose-issues.md
 - Spawn parallel debug agents for each issue
 - Collect root causes
 - Update UAT.md with root causes

package/dist/install.cjs

@@ -7699,6 +7699,7 @@ function checkForUpdate(options) {
 	const projectVersionFile = node_path.join(cwd, CLAUDE_DIR, "maxsim", "VERSION");
 	const globalVersionFile = node_path.join(homeDir, CLAUDE_DIR, "maxsim", "VERSION");
 	if (!node_fs.existsSync(cacheDir)) node_fs.mkdirSync(cacheDir, { recursive: true });
+	const isWindows = process.platform === "win32";
 	(0, node_child_process.spawn)(process.execPath, ["-e", `
   const fs = require('fs');
   const { execSync } = require('child_process');
@@ -7733,7 +7734,7 @@ function checkForUpdate(options) {
 `], {
 		stdio: "ignore",
 		windowsHide: true,
-		detached: true
+		detached: !isWindows
 	}).unref();
 }
 /**