maxsimcli 4.7.1 → 4.9.0

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

@@ -1,306 +0,0 @@
-<trigger>
-Use this workflow when:
-- Starting a new session on an existing project
-- User says "continue", "what's next", "where were we", "resume"
-- Any planning operation when .planning/ already exists
-- User returns after time away from project
-</trigger>
-
-<purpose>
-Instantly restore full project context so "Where were we?" has an immediate, complete answer.
-</purpose>
-
-<required_reading>
-@./references/continuation-format.md
-</required_reading>
-
-<process>
-
-<step name="initialize">
-Load all context in one call:
-
-```bash
-INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs init resume)
-```
-
-Parse JSON for: `state_exists`, `roadmap_exists`, `project_exists`, `planning_exists`, `has_interrupted_agent`, `interrupted_agent_id`, `commit_docs`.
-
-**If `state_exists` is true:** Proceed to load_state
-**If `state_exists` is false but `roadmap_exists` or `project_exists` is true:** Offer to reconstruct STATE.md
-**If `planning_exists` is false:** This is a new project - route to /maxsim:new-project
-</step>
-
-<step name="load_state">
-
-Read and parse STATE.md, then PROJECT.md:
-
-```bash
-cat .planning/STATE.md
-cat .planning/PROJECT.md
-```
-
-**From STATE.md extract:**
-
-- **Project Reference**: Core value and current focus
-- **Current Position**: Phase X of Y, Plan A of B, Status
-- **Progress**: Visual progress bar
-- **Recent Decisions**: Key decisions affecting current work
-- **Pending Todos**: Ideas captured during sessions
-- **Blockers/Concerns**: Issues carried forward
-- **Session Continuity**: Where we left off, any resume files
-
-**From PROJECT.md extract:**
-
-- **What This Is**: Current accurate description
-- **Requirements**: Validated, Active, Out of Scope
-- **Key Decisions**: Full decision log with outcomes
-- **Constraints**: Hard limits on implementation
-
-</step>
-
-<step name="check_incomplete_work">
-Look for incomplete work that needs attention:
-
-```bash
-# Check for continue-here files (mid-plan resumption)
-ls .planning/phases/*/.continue-here*.md 2>/dev/null
-
-# Check for plans without summaries (incomplete execution)
-for plan in .planning/phases/*/*-PLAN.md; do
-  summary="${plan/PLAN/SUMMARY}"
-  [ ! -f "$summary" ] && echo "Incomplete: $plan"
-done 2>/dev/null
-
-# Check for interrupted agents (use has_interrupted_agent and interrupted_agent_id from init)
-if [ "$has_interrupted_agent" = "true" ]; then
-  echo "Interrupted agent: $interrupted_agent_id"
-fi
-```
-
-**If .continue-here file exists:**
-
-- This is a mid-plan resumption point
-- Read the file for specific resumption context
-- Flag: "Found mid-plan checkpoint"
-
-**If PLAN without SUMMARY exists:**
-
-- Execution was started but not completed
-- Flag: "Found incomplete plan execution"
-
-**If interrupted agent found:**
-
-- Subagent was spawned but session ended before completion
-- Read agent-history.json for task details
-- Flag: "Found interrupted agent"
-  </step>
-
-<step name="present_status">
-Present complete project status to user:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PROJECT STATUS                                               ║
-╠══════════════════════════════════════════════════════════════╣
-║  Building: [one-liner from PROJECT.md "What This Is"]         ║
-║                                                               ║
-║  Phase: [X] of [Y] - [Phase name]                            ║
-║  Plan:  [A] of [B] - [Status]                                ║
-║  Progress: [██████░░░░] XX%                                  ║
-║                                                               ║
-║  Last activity: [date] - [what happened]                     ║
-╚══════════════════════════════════════════════════════════════╝
-
-[If incomplete work found:]
-⚠️  Incomplete work detected:
-    - [.continue-here file or incomplete plan]
-
-[If interrupted agent found:]
-⚠️  Interrupted agent detected:
-    Agent ID: [id]
-    Task: [task description from agent-history.json]
-    Interrupted: [timestamp]
-
-    Resume with: Task tool (resume parameter with agent ID)
-
-[If pending todos exist:]
-📋 [N] pending todos — /maxsim:check-todos to review
-
-[If blockers exist:]
-⚠️  Carried concerns:
-    - [blocker 1]
-    - [blocker 2]
-
-[If alignment is not ✓:]
-⚠️  Brief alignment: [status] - [assessment]
-```
-
-</step>
-
-<step name="determine_next_action">
-Based on project state, determine the most logical next action:
-
-**If interrupted agent exists:**
-→ Primary: Resume interrupted agent (Task tool with resume parameter)
-→ Option: Start fresh (abandon agent work)
-
-**If .continue-here file exists:**
-→ Primary: Resume from checkpoint
-→ Option: Start fresh on current plan
-
-**If incomplete plan (PLAN without SUMMARY):**
-→ Primary: Complete the incomplete plan
-→ Option: Abandon and move on
-
-**If phase in progress, all plans complete:**
-→ Primary: Transition to next phase
-→ Option: Review completed work
-
-**If phase ready to plan:**
-→ Check if CONTEXT.md exists for this phase:
-
-- If CONTEXT.md missing:
-  → Primary: Discuss phase vision (how user imagines it working)
-  → Secondary: Plan directly (skip context gathering)
-- If CONTEXT.md exists:
-  → Primary: Plan the phase
-  → Option: Review roadmap
-
-**If phase ready to execute:**
-→ Primary: Execute next plan
-→ Option: Review the plan first
-</step>
-
-<step name="offer_options">
-Present contextual options based on project state:
-
-```
-What would you like to do?
-
-[Primary action based on state - e.g.:]
-1. Resume interrupted agent [if interrupted agent found]
-   OR
-1. Execute phase (/maxsim:execute-phase {phase})
-   OR
-1. Discuss Phase 3 context (/maxsim:discuss-phase 3) [if CONTEXT.md missing]
-   OR
-1. Plan Phase 3 (/maxsim:plan-phase 3) [if CONTEXT.md exists or discuss option declined]
-
-[Secondary options:]
-2. Review current phase status
-3. Check pending todos ([N] pending)
-4. Review brief alignment
-5. Something else
-```
-
-**Note:** When offering phase planning, check for CONTEXT.md existence first:
-
-```bash
-ls .planning/phases/XX-name/*-CONTEXT.md 2>/dev/null
-```
-
-If missing, suggest discuss-phase before plan. If exists, offer plan directly.
-
-Wait for user selection.
-</step>
-
-<step name="route_to_workflow">
-Based on user selection, route to appropriate workflow:
-
-- **Execute plan** → Show command for user to run after clearing:
-  ```
-  ---
-
-  ## ▶ Next Up
-
-  **{phase}-{plan}: [Plan Name]** — [objective from PLAN.md]
-
-  `/maxsim:execute-phase {phase}`
-
-  <sub>`/clear` first → fresh context window</sub>
-
-  ---
-  ```
-- **Plan phase** → Show command for user to run after clearing:
-  ```
-  ---
-
-  ## ▶ Next Up
-
-  **Phase [N]: [Name]** — [Goal from ROADMAP.md]
-
-  `/maxsim:plan-phase [phase-number]`
-
-  <sub>`/clear` first → fresh context window</sub>
-
-  ---
-
-  **Also available:**
-  - `/maxsim:discuss-phase [N]` — gather context first
-  - `/maxsim:research-phase [N]` — investigate unknowns
-
-  ---
-  ```
-- **Transition** → ./transition.md
-- **Check todos** → Read .planning/todos/pending/, present summary
-- **Review alignment** → Read PROJECT.md, compare to current state
-- **Something else** → Ask what they need
-</step>
-
-<step name="update_session">
-Before proceeding to routed workflow, update session continuity:
-
-Update STATE.md:
-
-```markdown
-## Session Continuity
-
-Last session: [now]
-Stopped at: Session resumed, proceeding to [action]
-Resume file: [updated if applicable]
-```
-
-This ensures if session ends unexpectedly, next resume knows the state.
-</step>
-
-</process>
-
-<reconstruction>
-If STATE.md is missing but other artifacts exist:
-
-"STATE.md missing. Reconstructing from artifacts..."
-
-1. Read PROJECT.md → Extract "What This Is" and Core Value
-2. Read ROADMAP.md → Determine phases, find current position
-3. Scan \*-SUMMARY.md files → Extract decisions, concerns
-4. Count pending todos in .planning/todos/pending/
-5. Check for .continue-here files → Session continuity
-
-Reconstruct and write STATE.md, then proceed normally.
-
-This handles cases where:
-
-- Project predates STATE.md introduction
-- File was accidentally deleted
-- Cloning repo without full .planning/ state
-  </reconstruction>
-
-<quick_resume>
-If user says "continue" or "go":
-- Load state silently
-- Determine primary action
-- Execute immediately without presenting options
-
-"Continuing from [state]... [action]"
-</quick_resume>
-
-<success_criteria>
-Resume is complete when:
-
-- [ ] STATE.md loaded (or reconstructed)
-- [ ] Incomplete work detected and flagged
-- [ ] Clear status presented to user
-- [ ] Contextual next actions offered
-- [ ] User knows exactly where project stands
-- [ ] Session continuity updated
-      </success_criteria>

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

@@ -1,130 +0,0 @@
-<purpose>
-Render the project roadmap in a readable format with phase status icons and plan progress counts. Auto-collapses completed phases to one-liners for visual clarity and paginates at 20 phases per page for large projects. 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.
-
-**Parse `--page` argument:** If the command was invoked with `--page N`, extract the page number (default: 1). This controls which page of phases to display when total phases exceed 20.
-</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.**
-
-**Auto-collapse completed phases (always active, regardless of phase count):**
-
-Render phases in two visual groups:
-
-1. **Completed phases** — collapsed one-liners with no plan counts or status label:
-   ```
-   ✓  Phase {number}: {name}
-   ```
-   Just checkmark + phase number + name. One line per completed phase. This keeps the roadmap scannable when many phases are done.
-
-2. **Active and upcoming phases** — full detail format with icon, label, and plan counts:
-   ```
-   {icon}  Phase {number}: {name}    {label}  ({summary_count}/{plan_count} plans)
-   ```
-
-For active/upcoming phases:
-- `disk_status === 'partial'` -> icon `>`, label `IN PROGRESS`
-- `disk_status === 'planned' || 'empty' || 'discussed' || 'researched' || 'no_directory'` -> icon `[ ]`, label `PLANNED`
-
-Pad phase names with spaces so status labels align in a column (within the active/upcoming group only).
-
-Only show `({summary_count}/{plan_count} plans)` when `plan_count > 0`.
-
-**Pagination (only when total phases exceed 20):**
-
-After assembling all phase lines (both collapsed completed and full-detail active/upcoming), check the total phase count:
-
-- If total phases is **20 or fewer**: show all phases. No pagination footer. This is the default experience for small/medium projects.
-- If total phases **exceeds 20**: apply pagination.
-  - Page size: 20 phases per page.
-  - Use the `--page N` argument (default page 1) to determine which slice to show.
-  - Calculate: `first = (page - 1) * 20 + 1`, `last = min(page * 20, total)`.
-  - Show only phases from index `first` to `last`.
-  - Add a footer line after the phase list:
-    ```
-    Showing phases {first}-{last} of {total}. Use --page {next_page} for next.
-    ```
-  - If on the last page, omit the "Use --page" hint.
-
-Example output (small project, no pagination):
-```
-Context-Aware SDD — 3 done / 1 active / 1 planned
-
-✓  Phase 1: Context Rot Prevention
-✓  Phase 2: Init Flow Overhaul
-✓  Phase 3: Agent Coherence
-
->  Phase 4: Spec Drift Management        IN PROGRESS  (2/3 plans)
-[ ]  Phase 5: Workflow Coverage             PLANNED
-```
-
-Example output (large project with pagination, page 1):
-```
-NX Monorepo Migration — 15 done / 1 active / 9 planned
-
-✓  Phase 01: NX Workspace Scaffold
-✓  Phase 02: packages/core TypeScript Port
-✓  Phase 03: Shared Types
-...
-✓  Phase 15: CI Pipeline
-
->  Phase 16: Dashboard Rewrite              IN PROGRESS  (2/5 plans)
-[ ]  Phase 17: Plugin System                  PLANNED
-[ ]  Phase 18: Performance Optimization       PLANNED
-[ ]  Phase 19: Documentation                  PLANNED
-[ ]  Phase 20: Security Audit                 PLANNED
-
-Showing phases 1-20 of 25. Use --page 2 for next.
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Milestone summary header rendered with done/active/planned counts
-- [ ] Completed phases auto-collapsed to one-liners (checkmark + name only, no plan counts)
-- [ ] Active/upcoming phases shown with full detail (icon, label, plan counts)
-- [ ] Phases listed in numeric order within each group
-- [ ] Pagination footer shown only when total phases exceed 20
-- [ ] `--page N` argument controls which page to display
-- [ ] Plan progress shown inline for active/upcoming phases that have plans
-- [ ] Hard stop if .planning/ is missing
-</success_criteria>

package/dist/assets/templates/workflows/set-profile.md

@@ -1,81 +0,0 @@
-<purpose>
-Switch the model profile used by MAXSIM agents. Controls which Claude model each agent uses, balancing quality vs token spend.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="validate">
-Validate argument:
-
-```
-if $ARGUMENTS.profile not in ["quality", "balanced", "budget", "tokenburner"]:
-  Error: Invalid profile "$ARGUMENTS.profile"
-  Valid profiles: quality, balanced, budget, tokenburner
-  EXIT
-```
-</step>
-
-<step name="ensure_and_load_config">
-Ensure config exists and load current state:
-
-```bash
-node ~/.claude/maxsim/bin/maxsim-tools.cjs config-ensure-section
-INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs state load)
-```
-
-This creates `.planning/config.json` with defaults if missing and loads current config.
-</step>
-
-<step name="update_config">
-Read current config from state load or directly:
-
-Update `model_profile` field:
-```json
-{
-  "model_profile": "$ARGUMENTS.profile"
-}
-```
-
-Write updated config back to `.planning/config.json`.
-</step>
-
-<step name="confirm">
-Display confirmation with model table for selected profile:
-
-```
-✓ Model profile set to: $ARGUMENTS.profile
-
-Agents will now use:
-
-[Show table from MODEL_PROFILES in maxsim-tools.cjs for selected profile]
-
-Example:
-| Agent | Model |
-|-------|-------|
-| maxsim-planner | opus |
-| maxsim-executor | sonnet |
-| maxsim-verifier | haiku |
-| ... | ... |
-
-Next spawned agents will use the new profile.
-```
-
-Map profile names:
-- quality: use "quality" column from MODEL_PROFILES
-- balanced: use "balanced" column from MODEL_PROFILES
-- budget: use "budget" column from MODEL_PROFILES
-- tokenburner: use "tokenburner" column from MODEL_PROFILES (all opus)
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Argument validated
-- [ ] Config file ensured
-- [ ] Config updated with new model_profile
-- [ ] Confirmation displayed with model table
-</success_criteria>