maxsimcli 5.0.4 → 5.0.5

package/dist/assets/CHANGELOG.md

@@ -1,3 +1,13 @@
+## [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

@@ -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 get-issue N [--include-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 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/execute.md

@@ -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 $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 $PHASE_ISSUE_NUMBER --include-comments
    ```
 
 2. Parse issue comments to identify plan comments. A plan comment is one that contains either:
@@ -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 $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Look for the `<!-- maxsim:type=verification -->` comment and parse the `status:` field from its body.

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 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/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/plan-create.md

@@ -29,7 +29,7 @@ CHECKER_MODEL=$(node .claude/maxsim/bin/maxsim-tools.cjs resolve-model planner -
 
 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 $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Look for comments that contain `<!-- maxsim:type=plan -->`.

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

@@ -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 $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Look for a comment that contains `<!-- maxsim:type=context -->`.

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

@@ -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 $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 $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 $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 $PHASE_ISSUE_NUMBER --include-comments
 ```
 
 Show final gate:

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

@@ -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]
 ```

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

@@ -5,13 +5,11 @@ Before executing any step in this workflow, verify:
 </sanity_check>
 
 <purpose>
-Execute small, ad-hoc tasks with MAXSIM guarantees (atomic commits, STATE.md tracking). Also supports "save for later" todo capture via GitHub Issues.
+Execute small, ad-hoc tasks with MAXSIM guarantees (atomic commits, STATE.md tracking).
 
 Quick mode spawns planner (quick mode) + executor(s), tracks tasks as GitHub Issues (label: "quick"), and updates STATE.md's "Quick Tasks Completed" table.
 
 With `--full` flag: enables plan-checking (max 2 iterations) and post-execution verification for quality guarantees without full milestone ceremony.
-
-With `--todo` flag (or trigger words): enters Todo Mode for listing, capturing, completing, and triaging todos via GitHub Issues.
 </purpose>
 
 <required_reading>
@@ -22,18 +20,9 @@ Read all files referenced by the invoking prompt's execution_context before star
 **Step 1: Parse arguments and detect mode**
 
 Parse `$ARGUMENTS` for:
-- `--todo` flag → store as `$TODO_MODE` (true/false)
 - `--full` flag → store as `$FULL_MODE` (true/false)
 - Remaining text → use as `$DESCRIPTION` if non-empty
 
-**Mode detection:** Enter Todo Mode if ANY of these are true:
-1. `--todo` flag is present
-2. `$DESCRIPTION` starts with "todo", "save", "remember", "later" (case-insensitive)
-
-**If Todo Mode → skip to Step T1 (Todo Mode section below)**
-
-If not Todo Mode, continue with Quick Task Mode:
-
 If `$DESCRIPTION` is empty after parsing, prompt user interactively:
 
 ```
@@ -574,138 +563,6 @@ Ready for next task: /maxsim:quick
 
 ---
 
-## Todo Mode
-
-**Entered when `--todo` flag is set or description starts with "todo", "save", "remember", "later".**
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- MAXSIM ► TODO MODE
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-```
-
-**Step T1: Initialize todo context**
-
-```bash
-INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs init todos)
-```
-
-Extract from init JSON: `todo_count`, `todos`, `date`, `timestamp`, `github_ready`.
-
----
-
-**Step T2: Determine todo action**
-
-Parse `$DESCRIPTION` (text after `--todo` flag or trigger word) for intent:
-
-| Intent | Trigger | Action |
-|--------|---------|--------|
-| List | No description, or "list", "show" | Go to **T3: List** |
-| Capture | Has a description (not a trigger word) | Go to **T4: Capture** |
-| Complete | "done", "complete", "finish" + identifier | Go to **T5: Complete** |
-| Triage | "triage", "what next", "what should I work on" | Go to **T6: Triage** |
-
-If intent is ambiguous, default to **T3: List** (shows todos, then offers options).
-
----
-
-**Step T3: List Existing Todos**
-
-```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs todos list
-```
-
-Display current todos in a clean table:
-
-```
-Pending Todos:
-
-| # | Title | Area | Priority | Age |
-|---|-------|------|----------|-----|
-| 1 | [title] | [area] | [priority] | [relative time] |
-
----
-
-Options:
-1. Add a new todo: /maxsim:quick --todo [description]
-2. Complete a todo: /maxsim:quick --todo done [number]
-3. Triage: /maxsim:quick --todo triage
-4. Back to quick tasks: /maxsim:quick [description]
-```
-
-If no pending todos: "No pending todos. Use `/maxsim:quick --todo [description]` to capture one."
-
-Exit after display.
-
----
-
-**Step T4: Capture New Todo**
-
-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. 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, 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}"
-   ```
-4. Confirm: "Saved: ${TITLE} (priority: ${PRIORITY}) — GitHub Issue #{number}"
-
-Exit after confirm.
-
----
-
-**Step T5: Complete Todo**
-
-If user references an existing todo to complete:
-
-1. Parse identifier (number from list, or title fragment)
-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. Confirm: "Completed: ${TITLE} — GitHub Issue closed"
-
-Exit after confirm.
-
----
-
-**Step T6: Triage**
-
-Help user decide what to work on next:
-
-1. List all pending todos sorted by priority (HIGH first)
-2. Check if any todos relate to the current phase (cross-reference with ROADMAP.md):
-
-```bash
-ROADMAP=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs roadmap analyze)
-```
-
-3. Present prioritized view:
-
-```
-What should I work on?
-
-## Phase-Related Todos
-- [todo title] -- relates to Phase [N]: [phase name]
-
-## Standalone Todos
-- [HIGH] [todo title] (created [age] ago)
-- [MEDIUM] [todo title] (created [age] ago)
-
----
-
-Pick a todo to work on, or:
-- /maxsim:quick [description] -- start a new task
-- /maxsim:quick --todo [description] -- save something for later
-```
-
-Exit after display.
-
 </process>
 
 <success_criteria>
@@ -722,11 +579,4 @@ Exit after display.
 - [ ] (--full) `${next_num}-VERIFICATION.md` created by verifier
 - [ ] STATE.md updated with quick task row (Status column when --full)
 - [ ] Artifacts committed
-
-**Todo Mode:**
-- [ ] `--todo` flag or trigger words detected
-- [ ] Todo action determined (list/capture/complete/triage)
-- [ ] (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/sdd.md

@@ -35,7 +35,7 @@ Parse JSON for: `executor_model`, `verifier_model`, `commit_docs`, `phase_found`
 Find incomplete plans by querying GitHub Issues (the source of truth for plans and completion status):
 
 ```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 ${phase_issue_number} --include-comments
 node ~/.claude/maxsim/bin/maxsim-tools.cjs github list-sub-issues ${phase_issue_number}
 ```
 

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

@@ -304,7 +304,7 @@ Do NOT write a UAT.md file to `.planning/phases/`.
 3. Report to orchestrator: phase complete, issue closed
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github move-issue --project-number P --item-id ID --status "Done"
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github move-issue --issue-number N --status "Done"
 node ~/.claude/maxsim/bin/maxsim-tools.cjs github close-issue N
 ```
 
@@ -319,7 +319,7 @@ node ~/.claude/maxsim/bin/maxsim-tools.cjs github close-issue N
 4. Note which gaps need fixing before re-verification
 
 ```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs github move-issue --project-number P --item-id ID --status "In Progress"
+node ~/.claude/maxsim/bin/maxsim-tools.cjs github move-issue --issue-number N --status "In Progress"
 ```
 
 **If human_needed:**