maxsimcli 4.0.1 → 4.0.2

package/dist/assets/templates/skills/using-maxsim/SKILL.md

@@ -1,36 +1,33 @@
 ---
 name: using-maxsim
-description: Entry skill that establishes MAXSIM workflow rules — triggers before any action to route work through the correct MAXSIM commands, skills, and agents
 alwaysApply: true
+description: >-
+  Routes all work through MAXSIM's spec-driven workflow: checks for planning
+  directory, determines active phase, and dispatches to the correct MAXSIM
+  command. Use when starting any work session, resuming work, or when unsure
+  which MAXSIM command to run.
 ---
 
 # Using MAXSIM
 
-MAXSIM is a spec-driven development system. Work flows through phases, plans, and tasks — not ad-hoc coding.
+MAXSIM is a spec-driven development system. Work flows through phases, plans, and tasks -- not ad-hoc coding.
 
-**If you are about to write code without a plan, STOP. Route through MAXSIM first.**
-
-## The Iron Law
-
-<HARD-GATE>
-NO IMPLEMENTATION WITHOUT A PLAN.
-If there is no .planning/ directory, run `/maxsim:init` first.
+**HARD GATE -- No implementation without a plan.**
+If there is no `.planning/` directory, run `/maxsim:init` first.
 If there is no current phase, run `/maxsim:plan-phase` first.
 If there is no PLAN.md for the current phase, run `/maxsim:plan-phase` first.
 If there IS a plan, run `/maxsim:execute-phase` to execute it.
-Skipping the workflow is a violation — not a shortcut.
-</HARD-GATE>
 
-## When This Skill Triggers
+## Process
 
-This skill applies to ALL work sessions. Before starting any task:
+Before starting any task:
 
-1. **Check for `.planning/` directory** — if missing, initialize with `/maxsim:init`
-2. **Check STATE.md** — resume from last checkpoint if one exists
-3. **Check current phase** — determine what phase is active in ROADMAP.md
-4. **Route to the correct command** based on the situation (see routing table below)
+1. **Check for `.planning/` directory** -- if missing, initialize with `/maxsim:init`
+2. **Check STATE.md** -- resume from last checkpoint if one exists
+3. **Check current phase** -- determine what phase is active in ROADMAP.md
+4. **Route to the correct command** based on the routing table below
 
-## Routing Table
+### Routing Table
 
 | Situation | Route To |
 |-----------|----------|
@@ -39,18 +36,18 @@ This skill applies to ALL work sessions. Before starting any task:
 | Active phase has no PLAN.md | `/maxsim:plan-phase` |
 | Active phase has PLAN.md, not started | `/maxsim:execute-phase` |
 | Checkpoint exists in STATE.md | `/maxsim:resume-work` |
-| Bug found during execution | `/maxsim:debug` (triggers systematic-debugging skill) |
-| Phase complete, needs verification | `/maxsim:verify-phase` (triggers verification-before-completion skill) |
+| Bug found during execution | `/maxsim:debug` |
+| Phase complete, needs verification | `/maxsim:verify-phase` |
 | Quick standalone task | `/maxsim:quick` |
 | User asks for help | `/maxsim:help` |
 
-## Available Skills
+### Available Skills
 
 Skills are behavioral rules that activate automatically based on context:
 
 | Skill | Triggers When |
 |-------|---------------|
-| `using-maxsim` | Always (alwaysApply) — entry point for all MAXSIM work |
+| `using-maxsim` | Always (alwaysApply) -- entry point for all MAXSIM work |
 | `systematic-debugging` | Any bug, test failure, or unexpected behavior encountered |
 | `tdd` | Implementing any feature or bug fix (write test first) |
 | `verification-before-completion` | Before claiming any work is complete or passing |
@@ -60,7 +57,7 @@ Skills are behavioral rules that activate automatically based on context:
 | `simplify` | When reviewing and cleaning up code changes |
 | `code-review` | When reviewing implementation quality |
 
-## Available Agents
+### Available Agents
 
 Agents are specialized subagent prompts spawned by MAXSIM commands:
 
@@ -80,17 +77,7 @@ Agents are specialized subagent prompts spawned by MAXSIM commands:
 | `maxsim-codebase-mapper` | Maps codebase structure | `/maxsim:init` |
 | `maxsim-integration-checker` | Checks integration points | `/maxsim:verify-phase` |
 
-## Common Rationalizations — REJECT THESE
-
-| Excuse | Why It Violates the Rule |
-|--------|--------------------------|
-| "It's just a small fix" | Small fixes have context and consequences. Use `/maxsim:quick`. |
-| "I know what to do, I don't need a plan" | Plans catch what you miss. The plan is the checkpoint. |
-| "MAXSIM overhead is too much for this" | `/maxsim:quick` exists for lightweight tasks. Use it. |
-| "I'll plan it in my head" | Plans in your head die with context. Write them down. |
-| "The user said 'just do it'" | Route through `/maxsim:quick` — it is fast and still tracked. |
-
-## Red Flags — STOP If You Catch Yourself:
+## Common Pitfalls
 
 - Writing implementation code without a PLAN.md
 - Skipping `/maxsim:init` because "the project is simple"
@@ -99,22 +86,22 @@ Agents are specialized subagent prompts spawned by MAXSIM commands:
 - Making architectural decisions without documenting them in STATE.md
 - Finishing work without running verification
 
-**If any red flag triggers: STOP. Check the routing table. Follow the workflow.**
+**If any of these occur: stop, check the routing table, follow the workflow.**
 
-## Verification Checklist
+## Verification
 
 Before ending any work session:
 
 - [ ] All work was routed through MAXSIM commands (not ad-hoc)
 - [ ] STATE.md reflects current progress and decisions
-- [ ] Any bugs encountered were debugged systematically (not guessed)
+- [ ] Any bugs encountered were debugged systematically
 - [ ] Tests were written before implementation (TDD)
 - [ ] Completion claims have verification evidence
 - [ ] Recurring patterns or errors were saved to memory
 
-## Integration with CLAUDE.md
+## MAXSIM Integration
 
 When a project has a `CLAUDE.md`, both apply:
 - `CLAUDE.md` defines project-specific conventions (language, tools, style)
 - MAXSIM skills define workflow rules (how work is structured and verified)
-- If they conflict, `CLAUDE.md` project conventions take priority for code style; MAXSIM takes priority for workflow structure
+- If they conflict, `CLAUDE.md` takes priority for code style; MAXSIM takes priority for workflow structure

package/dist/assets/templates/skills/verification-before-completion/SKILL.md

@@ -1,36 +1,28 @@
 ---
 name: verification-before-completion
-description: Use before claiming any work is complete, fixed, or passing — requires running verification commands and reading output before making success claims
+description: >-
+  Requires running verification commands and reading actual output before making
+  any completion claims. Use when claiming work is done, tests pass, builds
+  succeed, or bugs are fixed. Prevents false completion claims.
 ---
 
 # Verification Before Completion
 
-Claiming work is complete without verification is dishonesty, not efficiency.
+Evidence before claims, always.
 
-**Evidence before claims, always.**
+**HARD GATE -- No completion claims without fresh verification evidence. If you have not run the verification command in this turn, you cannot claim it passes. "Should work" is not evidence. "I'm confident" is not evidence.**
 
-## The Iron Law
+## Process
 
-<HARD-GATE>
-NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
-If you have not run the verification command in this turn, you CANNOT claim it passes.
-"Should work" is not evidence. "I'm confident" is not evidence.
-Violating this rule is a violation — not a special case.
-</HARD-GATE>
+Before claiming any status or marking a task done:
 
-## The Gate Function
-
-BEFORE claiming any status, expressing satisfaction, or marking a task done:
-
-1. **IDENTIFY:** What command proves this claim?
-2. **RUN:** Execute the FULL command (fresh, in this turn — not a previous run)
-3. **READ:** Read the FULL output. Check the exit code. Count failures.
-4. **VERIFY:** Does the output actually confirm the claim?
-   - If NO: State the actual status with evidence
-   - If YES: State the claim WITH the evidence
-5. **CLAIM:** Only now may you assert completion
-
-**Skip any step = lying, not verifying.**
+1. **IDENTIFY** -- What command proves this claim?
+2. **RUN** -- Execute the full command fresh in this turn (not a previous run)
+3. **READ** -- Read the full output, check the exit code, count failures
+4. **VERIFY** -- Does the output actually confirm the claim?
+   - If NO: state the actual status with evidence
+   - If YES: state the claim with the evidence
+5. **CLAIM** -- Only now may you assert completion
 
 ### Evidence Block Format
 
@@ -43,35 +35,11 @@ OUTPUT: [relevant excerpt of actual output]
 VERDICT: PASS | FAIL
 ```
 
-This format is required for task completion claims in MAXSIM plan execution. It is NOT required for intermediate status updates like "I have read the file" or "here is the plan."
-
-## Common Rationalizations — REJECT THESE
-
-| Excuse | Why It Violates the Rule |
-|--------|--------------------------|
-| "Should work now" | "Should" is not evidence. RUN the command. |
-| "I'm confident in the logic" | Confidence is not evidence. Run it. |
-| "The linter passed" | Linter passing does not mean tests pass or build succeeds. |
-| "Just this once" | NO EXCEPTIONS. This is the rule, not a guideline. |
-| "I only changed one line" | One line can break everything. Verify. |
-| "The subagent reported success" | Trust test output and VCS diffs, not agent reports. |
-| "Partial check is enough" | Partial proves nothing about the unchecked parts. |
-
-## Red Flags — STOP If You Catch Yourself:
+This format is required for task completion claims in MAXSIM plan execution. It is not required for intermediate status updates.
 
-- Using "should", "probably", "seems to", or "looks good" about unverified work
-- Expressing satisfaction ("Great!", "Perfect!", "Done!") before running verification
-- About to commit or push without running the test/build command in THIS turn
-- Trusting a subagent's completion report without independent verification
-- Thinking "the last run was clean, I only changed one line"
-- About to mark a MAXSIM task as done without running the `<verify>` block
-- Relying on a previous turn's test output as current evidence
+### What Counts as Verification
 
-**If any red flag triggers: STOP. Run the command. Read the output. THEN make the claim.**
-
-## What Counts as Verification
-
-| Claim | Requires | NOT Sufficient |
+| Claim | Requires | Not Sufficient |
 |-------|----------|----------------|
 | "Tests pass" | Test command output showing 0 failures | Previous run, "should pass", partial run |
 | "Build succeeds" | Build command with exit code 0 | Linter passing, "logs look clean" |
@@ -79,7 +47,19 @@ This format is required for task completion claims in MAXSIM plan execution. It
 | "Task is complete" | All done criteria checked with evidence | "I implemented everything in the plan" |
 | "No regressions" | Full test suite passing | "I only changed one file" |
 
-## Verification Checklist
+## Common Pitfalls
+
+| Excuse | Why It Fails |
+|--------|-------------|
+| "Should work now" | "Should" is not evidence. Run the command. |
+| "I'm confident in the logic" | Confidence is not evidence. Run it. |
+| "The linter passed" | Linter passing does not mean tests pass or build succeeds. |
+| "I only changed one line" | One line can break everything. Verify. |
+| "The subagent reported success" | Trust test output and VCS diffs, not agent reports. |
+
+Stop if you catch yourself using "should", "probably", or "looks good" about unverified work, or expressing satisfaction before running verification.
+
+## Verification
 
 Before marking any work as complete:
 
@@ -91,12 +71,13 @@ Before marking any work as complete:
 - [ ] No "should", "probably", or "seems to" in your completion statement
 - [ ] Evidence block produced for the task completion claim
 
-## In MAXSIM Plan Execution
+## MAXSIM Integration
+
+The executor's task commit protocol requires verification before committing:
 
-The executor's task commit protocol requires verification BEFORE committing:
-1. Run the task's `<verify>` block (automated checks)
-2. Confirm the `<done>` criteria are met with evidence
+1. Run the task's verify block (automated checks)
+2. Confirm the done criteria are met with evidence
 3. Produce an evidence block for the task completion
 4. Only then: stage files and commit
 
-The verifier agent independently re-checks all claims — do not assume the verifier will catch what you missed.
+The verifier agent independently re-checks all claims -- do not assume the verifier will catch what you missed.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "maxsimcli",
-  "version": "4.0.1",
+  "version": "4.0.2",
   "private": false,
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code, OpenCode, Gemini and Codex by MayStudios.",
   "bin": {