maxsimcli 5.0.4 → 5.0.6

package/dist/assets/CHANGELOG.md

@@ -1,3 +1,20 @@
+## [5.0.5](https://github.com/maystudios/maxsimcli/compare/v5.0.4...v5.0.5) (2026-03-12)
+
+
+### Bug Fixes
+
+* correct template-CLI argument discrepancies (D1, D2, D3) ([a2936fb](https://github.com/maystudios/maxsimcli/commit/a2936fbf729effc8229f3af8752f67f253773f0a))
+
+## [5.0.4](https://github.com/maystudios/maxsimcli/compare/v5.0.3...v5.0.4) (2026-03-12)
+
+
+### Bug Fixes
+
+* **agents:** correct skill path prefix in available_skills frontmatter ([37d4a84](https://github.com/maystudios/maxsimcli/commit/37d4a84255b85990e6aafd1467617f3b0b6398c4))
+* **commands:** use absolute [@path](https://github.com/path) refs so commands resolve after install ([ff86aae](https://github.com/maystudios/maxsimcli/commit/ff86aaee0d02aae064ee1ac82bfba7730f1f2a42))
+* **hooks:** prevent console window flashes on Windows ([35a2591](https://github.com/maystudios/maxsimcli/commit/35a2591e18fe81cce5e0a10ae81595852804dcfa))
+* **workflows:** correct [@path](https://github.com/path) references to use ~/.claude/maxsim/ prefix ([9fdacc0](https://github.com/maystudios/maxsimcli/commit/9fdacc08f0adc6236288f4edcfef7a5845531797))
+
 ## [5.0.3](https://github.com/maystudios/maxsimcli/compare/v5.0.2...v5.0.3) (2026-03-12)
 
 

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

@@ -1,7 +1,7 @@
 ---
 name: maxsim:quick
-description: Execute a quick task with MAXSIM guarantees, or capture todos for later work
-argument-hint: "[--full] [--todo]"
+description: Execute a quick task with MAXSIM guarantees
+argument-hint: "[--full]"
 allowed-tools:
   - Read
   - Write
@@ -13,7 +13,7 @@ allowed-tools:
   - AskUserQuestion
 ---
 <objective>
-Execute small, ad-hoc tasks with MAXSIM guarantees (atomic commits, STATE.md tracking). Also supports "save for later" -- capturing ideas as GitHub Issues with 'todo' label for future work.
+Execute small, ad-hoc tasks with MAXSIM guarantees (atomic commits, STATE.md tracking).
 
 Quick mode is the same system with a shorter path:
 - Spawns planner (quick mode) + executor(s)
@@ -23,8 +23,6 @@ Quick mode is the same system with a shorter path:
 **Default:** Skips research, plan-checker, verifier. Use when you know exactly what to do.
 
 **`--full` flag:** Enables plan-checking (max 2 iterations) and post-execution verification. Use when you want quality guarantees without full milestone ceremony.
-
-**`--todo` flag:** Enters todo management mode. List, capture, complete, and triage todos without executing tasks. "Save for later" creates a GitHub Issue with 'todo' label (primary) with local file cache.
 </objective>
 
 <execution_context>

package/dist/assets/templates/references/thinking-partner.md

@@ -44,8 +44,6 @@ You are a thinking partner, not a task executor. Your role is to help the user a
 
 **Phase discussion** (discuss-phase): Focus on implementation decisions, gray area resolution, downstream impact. Challenge hand-wavy integration plans. Push for concrete acceptance criteria per deliverable.
 
-**Todo/bug triage** (/maxsim:quick --todo triage): Focus on problem definition, scope containment, approach selection. Shorter rounds — 2-3 questions vs 4. Time-boxed to 20-30 min. Don't over-explore — capture enough to unblock, not to solve.
-
 **General discussion**: Default behaviors from core_behaviors apply. Read the energy — if the user is exploring, explore with them. If they want a quick answer, give it.
 
 </context_modes>

package/dist/assets/templates/skills/github-artifact-protocol/SKILL.md

@@ -65,4 +65,3 @@ On partial failure during batch operations:
 - `STATE.md` -- decisions, blockers, metrics
 - `github-issues.json` -- mapping cache (rebuildable)
 - `codebase/` -- stack, architecture, conventions
-- `todos/` -- pending/completed todos

package/dist/assets/templates/skills/github-tools-guide/SKILL.md

@@ -25,7 +25,7 @@ Add `--raw` to get machine-readable JSON output (no formatting).
 |---------|-------------|
 | `github create-phase --phase-number "01" --phase-name "Name" --goal "Goal" [--requirements "R1,R2"] [--success-criteria "SC1,SC2"]` | Create phase issue + add to board + set "To Do" |
 | `github create-task --phase-number "01" --task-id "T1" --title "Title" --body "Body" --parent-issue-number N` | Create task sub-issue |
-| `github batch-create-tasks --phase-number "01" --parent-issue-number N --tasks-json '[...]'` | Batch create tasks with rollback |
+| `github batch-create-tasks --phase-number "01" --parent-issue-number N --tasks '[{"task_id":"1.1","title":"Title","body":"Body"}, ...]'` | Batch create tasks with rollback |
 | `github post-plan-comment --phase-issue-number N --plan-number "01" --plan-content "..." [--plan-content-file F]` | Post plan comment on phase issue |
 
 ### Comments
@@ -37,12 +37,12 @@ Add `--raw` to get machine-readable JSON output (no formatting).
 ### Issue Operations
 | Command | Description |
 |---------|-------------|
-| `github get-issue N [--comments]` | Get issue details (with optional comments) |
-| `github list-sub-issues N` | List sub-issues of a phase issue |
-| `github close-issue N [--reason "..."] [--state-reason completed\|not_planned]` | Close issue |
-| `github reopen-issue N` | Reopen closed issue |
+| `github get-issue --issue-number N [--include-comments]` | Get issue details (with optional comments) |
+| `github list-sub-issues --phase-issue-number N` | List sub-issues of a phase issue |
+| `github close-issue --issue-number N [--reason "..."] [--state-reason completed\|not_planned]` | Close issue |
+| `github reopen-issue --issue-number N` | Reopen closed issue |
 | `github bounce-issue --issue-number N --reason "feedback"` | Bounce to In Progress with feedback |
-| `github move-issue --project-number P --item-id ID --status "STATUS"` | Move to board column (To Do, In Progress, In Review, Done) |
+| `github move-issue --issue-number N --status "STATUS"` | Move to board column (To Do, In Progress, In Review, Done) |
 | `github detect-external-edits --phase-number "01"` | Check body hash mismatch |
 
 ### Board Operations
@@ -60,13 +60,6 @@ Add `--raw` to get machine-readable JSON output (no formatting).
 | `github all-progress` | All phases progress overview |
 | `github detect-interrupted --phase-issue-number N` | Detect interrupted phase |
 
-### Todos
-| Command | Description |
-|---------|-------------|
-| `github add-todo --title "T" [--description "D"] [--area A] [--phase P]` | Create todo issue |
-| `github complete-todo --todo-id "N" [--github-issue-number N]` | Complete todo |
-| `github list-todos [--area A] [--status pending\|completed\|all]` | List todos |
-
 ### Convenience
 | Command | Description |
 |---------|-------------|

package/dist/assets/templates/templates/state.md

@@ -54,12 +54,6 @@ Recent decisions affecting current work:
 - [Phase X]: [Decision summary]
 - [Phase Y]: [Decision summary]
 
-### Pending Todos
-
-[From GitHub Issues with label 'todo' — ideas captured during sessions]
-
-None yet.
-
 ### Blockers/Concerns
 
 [Issues that affect future work]
@@ -145,10 +139,6 @@ Updated after each plan completion.
 
 **Decisions:** Reference to PROJECT.md Key Decisions table, plus recent decisions summary for quick access. Full decision log lives in PROJECT.md.
 
-**Pending Todos:** Ideas captured via /maxsim:quick --todo (tracked as GitHub Issues)
-- Count of pending todos
-- Brief list if few, count if many (e.g., "5 pending todos — see /maxsim:quick --todo")
-
 **Blockers/Concerns:** From "Next Phase Readiness" sections
 - Issues that affect future work
 - Prefix with originating phase

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

@@ -427,7 +427,7 @@ After writing CONTEXT.md, append phase-specific entries to the project-level art
 **Append to DECISIONS.md:**
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-append .planning/DECISIONS.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-append decisions --entry "..."
 ```
 
 Append content:
@@ -444,7 +444,7 @@ Append content:
 **Append to ACCEPTANCE-CRITERIA.md:**
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-append .planning/ACCEPTANCE-CRITERIA.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-append acceptance-criteria --entry "..."
 ```
 
 Append content under "Phase-Level Criteria":
@@ -463,7 +463,7 @@ Append content under "Phase-Level Criteria":
 If any "don't do this" or "avoid this approach" decisions were made during discussion:
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-append .planning/NO-GOS.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-append no-gos --entry "..."
 ```
 
 Append content:

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

@@ -194,7 +194,7 @@ Deviations are normal — handle via rules below.
      ```
    - Close the task sub-issue and move to "Done":
      ```bash
-     node ~/.claude/maxsim/bin/maxsim-tools.cjs github close-issue $TASK_SUB_ISSUE_NUMBER
+     node ~/.claude/maxsim/bin/maxsim-tools.cjs github close-issue --issue-number $TASK_SUB_ISSUE_NUMBER
      node ~/.claude/maxsim/bin/maxsim-tools.cjs github move-issue --issue-number $TASK_SUB_ISSUE_NUMBER --status "Done"
      ```
 
@@ -351,7 +351,7 @@ If verification fails: STOP. Present: "Verification failed for Task [X]: [name].
 
 **On review failure (WIRE-07):** If the task sub-issue was already moved to "Done", reopen and move back:
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github reopen-issue $TASK_SUB_ISSUE_NUMBER
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github reopen-issue --issue-number $TASK_SUB_ISSUE_NUMBER
 node ~/.claude/maxsim/bin/maxsim-tools.cjs github move-issue --issue-number $TASK_SUB_ISSUE_NUMBER --status "In Progress"
 TMPFILE=$(mktemp)
 cat > "$TMPFILE" << 'BODY_EOF'
@@ -596,7 +596,7 @@ Wait for user response:
 
 If the code review identifies failures tied to specific tasks, and those task sub-issues were already closed:
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github reopen-issue $TASK_SUB_ISSUE_NUMBER
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github reopen-issue --issue-number $TASK_SUB_ISSUE_NUMBER
 node ~/.claude/maxsim/bin/maxsim-tools.cjs github move-issue --issue-number $TASK_SUB_ISSUE_NUMBER --status "In Progress"
 TMPFILE=$(mktemp)
 cat > "$TMPFILE" << 'BODY_EOF'
@@ -1058,7 +1058,7 @@ If `USER_SETUP_CREATED=true`: display `⚠️ USER SETUP REQUIRED` with path + e
 
 Check completion by querying the phase issue's task sub-issues:
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github list-sub-issues $PHASE_ISSUE_NUMBER
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github list-sub-issues --phase-issue-number $PHASE_ISSUE_NUMBER
 ```
 
 Count open vs closed sub-issues. Map closed count to plans complete.

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

@@ -20,7 +20,7 @@ Verification is handled inline (spawning verifier agent) since it is a stage of
 Load phase state in one call:
 
 ```bash
-INIT=$(node .claude/maxsim/bin/maxsim-tools.cjs init execute-phase "$PHASE")
+INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs init execute-phase "$PHASE")
 ```
 
 Parse `$ARGUMENTS` for: phase number (required), `--worktrees` (force worktree mode), `--no-worktrees` (force standard mode), `--auto` (auto-advance), `--gaps-only` (gap plans only).
@@ -42,7 +42,7 @@ Exit workflow.
 When GitHub integration is active (phase_issue_number is set), check for plan comments on the phase issue before reporting no plans:
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Parse the response to find comments with `<!-- maxsim:type=plan -->` markers or `## Plan NN` headings. If no plan comments are found:
@@ -62,7 +62,7 @@ When GitHub integration is active (`phase_issue_number` is set):
 
 1. Fetch the phase issue and its comments:
    ```bash
-   node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments
+   node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments
    ```
 
 2. Parse issue comments to identify plan comments. A plan comment is one that contains either:
@@ -76,7 +76,7 @@ When GitHub integration is active (`phase_issue_number` is set):
 
 4. Check completion status for each plan by calling:
    ```bash
-   node ~/.claude/maxsim/bin/maxsim-tools.cjs github list-sub-issues $PHASE_ISSUE_NUMBER
+   node ~/.claude/maxsim/bin/maxsim-tools.cjs github list-sub-issues --phase-issue-number $PHASE_ISSUE_NUMBER
    ```
    A plan is considered complete when ALL of its task sub-issues are closed (state: closed).
    Additionally, check for `<!-- maxsim:type=summary -->` comments on the phase issue as a secondary completion signal.
@@ -306,7 +306,7 @@ Verify that the phase achieved its GOAL, not just that tasks completed.
 Resolve verifier model and spawn the verifier agent:
 
 ```bash
-VERIFIER_MODEL=$(node .claude/maxsim/bin/maxsim-tools.cjs resolve-model verifier --raw)
+VERIFIER_MODEL=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs resolve-model verifier --raw)
 ```
 
 ```
@@ -330,7 +330,7 @@ Also write VERIFICATION.md to the phase directory for local reference.",
 Read verification status from the verification comment on the phase issue:
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Look for the `<!-- maxsim:type=verification -->` comment and parse the `status:` field from its body.
@@ -368,12 +368,12 @@ node ~/.claude/maxsim/bin/maxsim-tools.cjs github post-comment --issue-number $P
 
 Mark phase complete:
 ```bash
-COMPLETION=$(node .claude/maxsim/bin/maxsim-tools.cjs phase complete "${PHASE_NUMBER}")
+COMPLETION=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs phase complete "${PHASE_NUMBER}")
 ```
 
 Update tracking files:
 ```bash
-node .claude/maxsim/bin/maxsim-tools.cjs commit "docs(phase-{X}): complete phase execution" --files .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md {phase_dir}/*-VERIFICATION.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs commit "docs(phase-{X}): complete phase execution" --files .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md {phase_dir}/*-VERIFICATION.md
 ```
 
 **If `gaps_found`:** Post a gaps comment on the phase issue, then proceed to Retry Loop (step 6).
@@ -493,7 +493,7 @@ The state detection in step 2 handles resume automatically -- completed plans ha
 After verification passes, update STATE.md:
 
 ```bash
-node .claude/maxsim/bin/maxsim-tools.cjs state record-session \
+node ~/.claude/maxsim/bin/maxsim-tools.cjs state record-session \
   --stopped-at "Phase ${PHASE} executed and verified" \
   --resume-file "${phase_dir}"
 ```

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

@@ -112,7 +112,7 @@ Block until user responds.
 Check if any phase issue has a verification comment with FAIL status (from live GitHub data via `github all-progress` — look for phases stuck in "In Review" with a known failure, or check recent comments via `github get-issue` for the current phase issue):
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue N --comments
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number N --include-comments
 ```
 ```
 ## Problem Detected

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

@@ -117,9 +117,8 @@ Usage: `/maxsim:debug login form returns 500` or `/maxsim:debug` (resume)
 
 Ad-hoc tasks with MAXSIM guarantees.
 
-- Atomic commits, state tracking, todo capture
+- Atomic commits, state tracking
 - `--full` flag enables plan-checking and verification agents
-- "Save for later" captures ideas as todos for future work
 
 Usage: `/maxsim:quick` or `/maxsim:quick --full`
 

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

@@ -662,9 +662,9 @@ If "No, change it": capture the preferred convention via freeform.
 - Set `{{source}}` to "init-existing scan + user confirmation"
 - Set `{{generated_or_confirmed}}` to "confirmed"
 
-Write `.planning/CONVENTIONS.md`:
+Write `.planning/CONVENTIONS.md` directly using the Write tool (CONVENTIONS.md is not a valid artefakt type):
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write .planning/CONVENTIONS.md
+# Use the Write tool to create .planning/CONVENTIONS.md with the content above
 ```
 
 ## Step 6d: No-Gos from Scan
@@ -1222,7 +1222,7 @@ Generate structured artefakte documents from gathered context.
 **DECISIONS.md:**
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write .planning/DECISIONS.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write decisions
 ```
 
 Write content:
@@ -1246,7 +1246,7 @@ Write content:
 **ACCEPTANCE-CRITERIA.md:**
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write .planning/ACCEPTANCE-CRITERIA.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write acceptance-criteria
 ```
 
 Write content:
@@ -1274,7 +1274,7 @@ Populated per-phase during /maxsim:plan (discussion stage).
 **NO-GOS.md:**
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write .planning/NO-GOS.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write no-gos
 ```
 
 Write content:

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

@@ -52,7 +52,7 @@ Use the results to route:
 For Scenario C vs D, check phase progress:
 
 ```bash
-node .claude/maxsim/bin/maxsim-tools.cjs roadmap analyze 2>/dev/null || echo "NO_ANALYSIS"
+node ~/.claude/maxsim/bin/maxsim-tools.cjs roadmap analyze 2>/dev/null || echo "NO_ANALYSIS"
 ```
 
 If all phases show status "complete" -> Scenario D (Milestone Complete).
@@ -140,7 +140,7 @@ Display:
 Load current state:
 
 ```bash
-node .claude/maxsim/bin/maxsim-tools.cjs state load 2>/dev/null
+node ~/.claude/maxsim/bin/maxsim-tools.cjs state load 2>/dev/null
 ```
 
 Read `.planning/ROADMAP.md` and `.planning/STATE.md` to display:

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

@@ -16,7 +16,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 
 - Read PROJECT.md (existing project, validated requirements, decisions)
 - Read MILESTONES.md (what shipped previously)
-- Read STATE.md (pending todos, blockers)
+- Read STATE.md (blockers, decisions)
 - Check for MILESTONE-CONTEXT.md (from /maxsim:plan)
 
 ## 2. Gather Milestone Goals

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

@@ -469,7 +469,7 @@ After PROJECT.md is committed, generate artefakte documents that capture structu
 **DECISIONS.md** — Key decisions made during questioning with rationale:
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write .planning/DECISIONS.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write decisions
 ```
 
 Write content:
@@ -492,7 +492,7 @@ Write content:
 **ACCEPTANCE-CRITERIA.md** — Measurable success criteria derived from user's vision:
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write .planning/ACCEPTANCE-CRITERIA.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write acceptance-criteria
 ```
 
 Write content:
@@ -522,7 +522,7 @@ Populated per-phase during /maxsim:plan.
 **NO-GOS.md** — Explicit exclusions and anti-patterns:
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write .planning/NO-GOS.md
+node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write no-gos
 ```
 
 Write content:
@@ -573,8 +573,9 @@ Populate from questioning context + reasonable defaults:
 
 Write content using the 4 must-have sections (Tech Stack, File Layout, Error Handling, Testing). Remove HTML comment examples and replace with actual project-specific conventions.
 
+Write `.planning/CONVENTIONS.md` directly using the Write tool (CONVENTIONS.md is not a valid artefakt type):
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs artefakte-write .planning/CONVENTIONS.md
+# Use the Write tool to create .planning/CONVENTIONS.md with the content above
 ```
 
 **Commit artefakte:**

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

@@ -21,15 +21,15 @@ The orchestrator provides phase context. Verify we have what we need:
 ## Step 2: Resolve Models
 
 ```bash
-PLANNER_MODEL=$(node .claude/maxsim/bin/maxsim-tools.cjs resolve-model planner --raw)
-CHECKER_MODEL=$(node .claude/maxsim/bin/maxsim-tools.cjs resolve-model planner --raw)
+PLANNER_MODEL=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs resolve-model planner --raw)
+CHECKER_MODEL=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs resolve-model planner --raw)
 ```
 
 ## Step 3: Check Existing Plans
 
 Query the phase GitHub Issue for existing plan comments:
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Look for comments that contain `<!-- maxsim:type=plan -->`.
@@ -324,7 +324,7 @@ Parse tasks from the posted plans. For each `<task>` element in the plan XML, ex
 Run `github batch-create-tasks` with the full tasks array and the phase issue number:
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github batch-create-tasks --phase-number "$PHASE_NUMBER" --parent-issue-number $PHASE_ISSUE_NUMBER --tasks-json '[{"id":"1.1","title":"Task title","description":"Task body"}, ...]'
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github batch-create-tasks --phase-number "$PHASE_NUMBER" --parent-issue-number $PHASE_ISSUE_NUMBER --tasks '[{"task_id":"1.1","title":"Task title","body":"Task body"}, ...]'
 ```
 
 Each task becomes a GitHub sub-issue linked to the phase issue.

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

@@ -128,7 +128,7 @@ Phase: "API documentation"
 Phase number, name, directory, and GitHub issue number come from the orchestrator context.
 
 ```bash
-INIT=$(node .claude/maxsim/bin/maxsim-tools.cjs init phase-op "${PHASE}")
+INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs init phase-op "${PHASE}")
 ```
 
 Parse JSON for: `commit_docs`, `phase_found`, `phase_dir`, `phase_number`, `phase_name`, `phase_slug`, `padded_phase`, `has_research`, `has_context`, `has_plans`, `plan_count`, `roadmap_exists`, `planning_exists`.
@@ -141,7 +141,7 @@ Also extract `phase_issue_number` passed from the orchestrator.
 
 Check if a context comment already exists on the phase GitHub Issue by calling:
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Look for a comment that contains `<!-- maxsim:type=context -->`.

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

@@ -21,7 +21,7 @@ The orchestrator provides phase context. Verify we have what we need:
 ## Step 2: Resolve Researcher Model
 
 ```bash
-RESEARCHER_MODEL=$(node .claude/maxsim/bin/maxsim-tools.cjs resolve-model researcher --raw)
+RESEARCHER_MODEL=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs resolve-model researcher --raw)
 ```
 
 ## Step 3: Check Existing Research
@@ -58,7 +58,7 @@ Return control to orchestrator.
 ## Step 4: Gather Phase Context
 
 ```bash
-PHASE_DESC=$(node .claude/maxsim/bin/maxsim-tools.cjs roadmap get-phase "${PHASE}" 2>/dev/null)
+PHASE_DESC=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs roadmap get-phase "${PHASE}" 2>/dev/null)
 ```
 
 Extract the phase section/description from the JSON output for the researcher prompt.

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

@@ -20,7 +20,7 @@ This file is the ORCHESTRATOR ONLY. Stage-specific logic lives in:
 Load phase state in one call:
 
 ```bash
-INIT=$(node .claude/maxsim/bin/maxsim-tools.cjs init plan-phase "$PHASE")
+INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs init plan-phase "$PHASE")
 ```
 
 Parse JSON for: `phase_found`, `phase_dir`, `phase_number`, `phase_name`, `phase_slug`, `padded_phase`, `has_context`, `has_research`, `has_plans`, `plan_count`, `plans`, `commit_docs`, `researcher_model`, `planner_model`, `checker_model`, `research_enabled`, `plan_checker_enabled`, `state_path`, `roadmap_path`, `requirements_path`, `context_path`, `research_path`, `phase_req_ids`, `phase_issue_number`.
@@ -47,7 +47,7 @@ Detect planning stage by querying the phase GitHub Issue:
 2. **If no `phase_issue_number` exists:** The phase has not been set up on GitHub yet.
    - Run `node ~/.claude/maxsim/bin/maxsim-tools.cjs github create-phase --phase-number "$PHASE_NUMBER" --phase-name "$PHASE_NAME" --goal "$GOAL" --requirements "$REQUIREMENTS" --success-criteria "$SUCCESS_CRITERIA"` to create the issue (uses roadmap data).
    - Store the returned issue number as `phase_issue_number`.
-3. Run `node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments` to read the phase issue body and comments.
+3. Run `node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments` to read the phase issue body and comments.
 4. Check issue comments for existing artifacts using HTML marker comments:
    - Has a comment containing `<!-- maxsim:type=context -->`? → Discussion stage complete
    - Has a comment containing `<!-- maxsim:type=research -->`? → Research stage complete
@@ -105,7 +105,7 @@ Pass context: `phase_number`, `phase_name`, `phase_dir`, `padded_phase`, `phase_
 
 Re-query the phase issue to verify the `type=context` comment now exists:
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Show gate:
@@ -140,7 +140,7 @@ Pass context: `phase_number`, `phase_name`, `phase_dir`, `padded_phase`, `phase_
 
 Re-query the phase issue to verify the `type=research` comment now exists:
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Show gate:
@@ -172,7 +172,7 @@ Pass context: `phase_number`, `phase_name`, `phase_dir`, `padded_phase`, `phase_
 
 Re-query the phase issue to verify `type=plan` comments exist:
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue $PHASE_ISSUE_NUMBER --comments
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github get-issue --issue-number $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Show final gate:
@@ -229,7 +229,7 @@ The stage detection in step 3 handles resume automatically -- completed stages p
 After all stages complete, update STATE.md:
 
 ```bash
-node .claude/maxsim/bin/maxsim-tools.cjs state record-session \
+node ~/.claude/maxsim/bin/maxsim-tools.cjs state record-session \
   --stopped-at "Phase ${PHASE} planned" \
   --resume-file "GitHub Issue #${phase_issue_number}"
 ```

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

@@ -107,7 +107,7 @@ For the current active phase (or any phase requested by user):
 
 ```bash
 node ~/.claude/maxsim/bin/maxsim-tools.cjs github phase-progress --phase-issue-number N
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github list-sub-issues N
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github list-sub-issues --phase-issue-number N
 ```
 
 **Detect external edits:**
@@ -124,11 +124,9 @@ node ~/.claude/maxsim/bin/maxsim-tools.cjs github detect-external-edits --phase-
 
 - Use `current_phase` and `next_phase` from `$ROADMAP` (local) cross-referenced with GitHub board status
 - Note `paused_at` if work was paused (from `$STATE`)
-- Count pending todos: run `github list-todos` for live todo count
 - Check for interrupted phases via `github detect-interrupted`
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github list-todos --status pending
 node ~/.claude/maxsim/bin/maxsim-tools.cjs github detect-interrupted --phase-issue-number N
 ```
 </step>
@@ -173,9 +171,6 @@ CONTEXT: [✓ if has_context | - if not]
 - Phase [N]: [issue description, e.g., "External edit detected — body_hash mismatch"]
 - Phase [M]: [issue description, e.g., "Local: complete, GitHub: In Progress — discrepancy"]
 
-## Pending Todos
-- [count] pending — /maxsim:quick --todo to review
-
 ## What's Next
 [Next phase/plan objective from live GitHub data and local roadmap]
 ```