mindsystem-cc 3.2.3 → 3.3.1

package/mindsystem/workflows/create-milestone.md

@@ -25,7 +25,6 @@ Load project context:
 cat .planning/PROJECT.md
 cat .planning/MILESTONES.md 2>/dev/null || echo "No milestones file yet"
 cat .planning/STATE.md
-cat .planning/MILESTONE-CONTEXT.md 2>/dev/null || echo "No milestone context file"
 cat .planning/config.json 2>/dev/null
 ```
 
@@ -33,22 +32,21 @@ Extract:
 - What shipped previously (from MILESTONES.md)
 - Current Validated requirements (from PROJECT.md)
 - Pending todos and blockers (from STATE.md)
-- Any context from discuss-milestone (MILESTONE-CONTEXT.md)
 
 **Calculate next milestone version:**
 - Parse last version from MILESTONES.md
 - If v1.0 → suggest v1.1 (minor) or v2.0 (major)
 - If v1.3 → suggest v1.4 or v2.0
-</step>
 
-<step name="gather_goals">
-**If MILESTONE-CONTEXT.md exists (from /ms:discuss-milestone):**
-- Use features and scope already gathered
-- Present summary for confirmation
-- Skip to confirm_goals step
+**Calculate previous milestone for context:**
+- If v1.1 starting → previous is v1.0
+- Store previous version number for use in gather_goals step
+- Context files (DECISIONS.md, AUDIT.md) will be loaded on-demand based on user's choice
 
-**If no context file:**
+**Why only the last milestone?** Older decisions that remain important should already be in PROJECT.md or visible in the codebase. Older untested assumptions that weren't addressed are intentionally skipped. Loading all previous milestones would bloat context for diminishing returns.
+</step>
 
+<step name="gather_goals">
 Present what shipped:
 ```
 Last milestone: v[X.Y] [Name]
@@ -62,15 +60,65 @@ Pending todos:
 - [From STATE.md if any]
 ```
 
-Ask (freeform, not AskUserQuestion):
-"What do you want to build in the next milestone?"
+**Decision gate:**
+
+Use AskUserQuestion:
+```
+header: "New Milestone"
+question: "How do you want to start v[X.Y]?"
+options:
+  - "I know what to build" — proceed to goal gathering
+  - "Help me figure it out" — enter discovery mode with previous context
+  - "Show previous decisions first" — view DECISIONS.md and AUDIT.md, then decide
+```
+
+**If "I know what to build":**
+- Ask directly: "What do you want to build in the next milestone?"
+- Wait for response
+- Proceed to confirm_goals
+
+**If "Show previous decisions first":**
+- Using the previous version from load_context (e.g., "1.0"):
+  - Check for and read `.planning/milestones/v1.0-DECISIONS.md` if exists
+  - Check for and read `.planning/milestones/v1.0-MILESTONE-AUDIT.md` if exists
+- Present relevant context from these files
+- Then present decision gate again (without this option)
+
+**If "Help me figure it out" (Discovery Mode):**
+- Using the previous version from load_context:
+  - Check for and read `.planning/milestones/v{VERSION}-DECISIONS.md` if exists
+  - Check for and read `.planning/milestones/v{VERSION}-MILESTONE-AUDIT.md` if exists
+
+Surface untested assumptions (from AUDIT.md):
+```
+📋 Untested from v[previous]:
+- Error state displays (couldn't mock API errors)
+- Empty state handling (couldn't clear test data)
+- [etc. from assumptions section]
+
+These were skipped during UAT. Address them in this milestone?
+```
+
+Run AskUserQuestion-based feature discovery:
+```
+header: "What to build"
+question: "What do you want to add, improve, or fix?"
+options:
+  - "Address untested assumptions" — add test infrastructure or fix gaps
+  - "New features" — build something new
+  - "Improvements" — enhance existing features
+  - "Bug fixes" — fix known issues
+  - "Let me describe" — freeform input
+```
 
-Wait for response. Then use AskUserQuestion to explore:
+Continue with follow-up questions:
 - Probe specific features mentioned
 - Ask about priorities
 - Surface constraints or dependencies
 - Clarify scope boundaries
 
+Follow questioning.md patterns for AskUserQuestion-based discovery.
+
 Continue until you have clear milestone goals.
 </step>
 
@@ -138,13 +186,6 @@ Progress: ░░░░░░░░░░ 0%
 Keep Accumulated Context (decisions, blockers) from previous milestone.
 </step>
 
-<step name="cleanup">
-Delete temporary context file if it exists:
-
-```bash
-rm -f .planning/MILESTONE-CONTEXT.md
-```
-</step>
 
 <step name="git_commit">
 ```bash
@@ -197,7 +238,6 @@ PROJECT.md updated with:
 - PROJECT.md updated with Current Milestone section
 - Active requirements reflect new milestone goals
 - STATE.md reset for new milestone (keeps accumulated context)
-- MILESTONE-CONTEXT.md consumed and deleted (if existed)
 - Git commit made
 - User routed to define-requirements (or research-project)
 </success_criteria>

package/mindsystem/workflows/do-work.md

@@ -48,11 +48,11 @@ Validate description is actionable (not vague like "fix stuff" or "make it work"
 </step>
 
 <step name="validate_project">
-Verify active GSD project:
+Verify active Mindsystem project:
 
 ```bash
 if [ ! -f .planning/STATE.md ]; then
-  echo "ERROR: No active GSD project found (.planning/STATE.md missing)"
+  echo "ERROR: No active Mindsystem project found (.planning/STATE.md missing)"
   echo ""
   echo "Options:"
   echo "- Initialize project: /ms:new-project"
@@ -217,6 +217,56 @@ Verify the work is complete:
 Keep verification focused on the specific changes made.
 </step>
 
+<step name="simplify_code">
+Read simplifier from config:
+
+```bash
+SIMPLIFIER=$(cat .planning/config.json 2>/dev/null | jq -r '.simplifier // empty')
+```
+
+**If SIMPLIFIER = "skip":**
+Skip to create_adhoc_summary.
+
+**If SIMPLIFIER = empty/null:**
+Use default: `SIMPLIFIER="ms-code-simplifier"`
+
+**Otherwise:**
+Use SIMPLIFIER value directly as agent name.
+
+1. **Get modified files:**
+   ```bash
+   git diff --name-only HEAD | grep -E '\.(dart|ts|tsx|js|jsx|swift|kt|py|go|rs)$'
+   ```
+
+2. **Spawn simplifier with adhoc scope:**
+   ```
+   Task(
+     prompt="
+     <objective>
+     Simplify code modified in adhoc work.
+     Preserve all functionality. Improve clarity and consistency.
+     </objective>
+
+     <scope>
+     Files to analyze:
+     {MODIFIED_FILES}
+     </scope>
+
+     <output>
+     After simplifications, run static analysis and tests.
+     Report what was simplified and verification results.
+     </output>
+     ",
+     subagent_type="{SIMPLIFIER}"
+   )
+   ```
+
+3. **Track simplification changes:**
+   - If changes made: Set `SIMPLIFICATION_APPLIED=true`
+   - Simplified files will be included in the adhoc commit
+   - Note in SUMMARY.md that simplification was applied
+</step>
+
 <step name="create_adhoc_summary">
 Create SUMMARY.md (see @~/.claude/mindsystem/templates/adhoc-summary.md for full template):
 
@@ -286,11 +336,12 @@ If section doesn't exist, add after "### Pending Todos" section:
 </step>
 
 <step name="git_commit">
-Single commit for all changes:
+Single commit for all changes (including simplifications if applied):
 
 ```bash
-# Add all modified files
+# Add all modified files (code + simplified files)
 git add [code files modified]
+git add [simplified files if SIMPLIFICATION_APPLIED]
 git add "$plan_file"
 git add "$summary_file"
 git add .planning/STATE.md
@@ -300,10 +351,18 @@ git add .planning/STATE.md
 # fix: bug fix, correction
 commit_type="fix"  # or "feat" based on nature of work
 
+# Include simplification note if applied
+if [ "$SIMPLIFICATION_APPLIED" = "true" ]; then
+  simplification_note="Includes code simplification pass."
+else
+  simplification_note=""
+fi
+
 git commit -m "$(cat <<'EOF'
 ${commit_type}(adhoc): [description]
 
 Files: [count] modified
+${simplification_note}
 EOF
 )"
 
@@ -314,6 +373,22 @@ commit_hash=$(git rev-parse --short HEAD)
 Update SUMMARY.md with commit hash in frontmatter.
 </step>
 
+<step name="generate_adhoc_patch">
+Generate patch file from the adhoc commit:
+
+```bash
+patch_file=".planning/adhoc/${timestamp}-${slug}.patch"
+
+~/.claude/mindsystem/scripts/generate-adhoc-patch.sh "$commit_hash" "$patch_file"
+```
+
+If patch generated (file exists and non-empty):
+- Update SUMMARY.md frontmatter to include `patch_file: [path]`
+
+If skipped (no implementation changes outside exclusions):
+- Leave patch_file field empty or omit from SUMMARY.md
+</step>
+
 <step name="completion">
 Report completion:
 
@@ -327,6 +402,7 @@ Adhoc work complete: [description]
 Artifacts:
 - Plan: .planning/adhoc/[timestamp]-[slug]-PLAN.md
 - Summary: .planning/adhoc/[timestamp]-[slug]-SUMMARY.md
+- Patch: .planning/adhoc/[timestamp]-[slug].patch (if generated)
 
 STATE.md updated with adhoc entry.
 
@@ -354,6 +430,7 @@ Rule 4 is strict for adhoc work — architectural changes exceed adhoc scope by
 <output_artifacts>
 - `.planning/adhoc/{timestamp}-{slug}-PLAN.md` — lightweight plan
 - `.planning/adhoc/{timestamp}-{slug}-SUMMARY.md` — completion summary
+- `.planning/adhoc/{timestamp}-{slug}.patch` — implementation changes (if any)
 - Updated `.planning/STATE.md` — adhoc entry in accumulated context
 - Git commit with all changes
 </output_artifacts>

package/mindsystem/workflows/execute-phase.md

@@ -341,6 +341,72 @@ After all waves complete, aggregate results:
 ```
 </step>
 
+<step name="simplify_code">
+Read simplifier agent name from config:
+
+```bash
+SIMPLIFIER=$(cat .planning/config.json 2>/dev/null | jq -r '.simplifier // empty')
+```
+
+**If SIMPLIFIER = "skip":**
+Report: "Code simplification skipped (config: skip)"
+Proceed to verify_phase_goal.
+
+**If SIMPLIFIER = empty/null:**
+Use default: `SIMPLIFIER="ms-code-simplifier"`
+
+**Otherwise:**
+Use SIMPLIFIER value directly as agent name.
+
+1. **Gather changed files:**
+   ```bash
+   # Get all files changed in this phase's commits
+   PHASE_COMMITS=$(git log --oneline --grep="(${PHASE_NUMBER}-" --format="%H")
+   CHANGED_FILES=$(git diff --name-only $(echo "$PHASE_COMMITS" | tail -1)^..HEAD | grep -E '\.(dart|ts|tsx|js|jsx|swift|kt|py|go|rs)$')
+   ```
+
+2. **Spawn simplifier (agent name from config):**
+   ```
+   Task(
+     prompt="
+     <objective>
+     Simplify code modified in phase {phase_number}.
+     Preserve all functionality. Improve clarity and consistency.
+     </objective>
+
+     <scope>
+     Files to analyze:
+     {CHANGED_FILES}
+     </scope>
+
+     <output>
+     After simplifications, run static analysis and tests.
+     Report what was simplified and verification results.
+     </output>
+     ",
+     subagent_type="{SIMPLIFIER}"
+   )
+   ```
+
+3. **Handle result:**
+   - If changes made: Stage and commit
+   - If no changes: Report "No simplifications needed"
+
+4. **Commit simplifications (if any):**
+   ```bash
+   git add [simplified files]
+   git commit -m "$(cat <<'EOF'
+   refactor({phase}): simplify phase code
+
+   Simplifier: {agent_type}
+   Files simplified: {count}
+   EOF
+   )"
+   ```
+
+Report: "Code simplified. Proceeding to verification."
+</step>
+
 <step name="verify_phase_goal">
 Verify phase achieved its GOAL, not just completed its TASKS.
 

package/mindsystem/workflows/map-codebase.md

@@ -96,6 +96,14 @@ Write these documents to .planning/codebase/:
 - STACK.md - Languages, runtime, frameworks, dependencies, configuration
 - INTEGRATIONS.md - External APIs, databases, auth providers, webhooks
 
+After writing STACK.md, update config.json simplifier field with the appropriate agent name:
+1. Read STACK.md to detect primary framework
+2. Map framework to simplifier agent name:
+   - Flutter/Dart → "ms-flutter-simplifier"
+   - All others (React, Next.js, Node, Swift, Kotlin, etc.) → "ms-code-simplifier"
+3. If .planning/config.json exists: update the simplifier field
+   If not: note the recommended simplifier for later config creation
+
 Explore thoroughly. Write documents directly using templates. Return confirmation only.
 ```
 
@@ -285,5 +293,5 @@ End workflow.
 - TaskOutput used to collect confirmations only
 - All 7 codebase documents exist
 - Clear completion summary with line counts
-- User offered clear next steps in GSD style
+- User offered clear next steps in Mindsystem style
 </success_criteria>

package/mindsystem/workflows/verify-work.md

@@ -552,7 +552,7 @@ git stash push -m "mocks-batch-{N}"
 ```
 Task(
   prompt="""
-You are a GSD verify-fixer. Investigate this issue, find the root cause, implement a fix, and commit it.
+You are a Mindsystem verify-fixer. Investigate this issue, find the root cause, implement a fix, and commit it.
 
 ## Issue
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mindsystem-cc",
-  "version": "3.2.3",
+  "version": "3.3.1",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.",
   "bin": {
     "mindsystem-cc": "bin/install.js"

package/scripts/generate-adhoc-patch.sh

@@ -0,0 +1,79 @@
+#!/bin/bash
+#
+# generate-adhoc-patch.sh
+# Generates a patch file from an adhoc commit, excluding documentation and generated files.
+#
+# Usage: ./scripts/generate-adhoc-patch.sh <commit-hash> <output-path>
+# Example: ./scripts/generate-adhoc-patch.sh abc123f .planning/adhoc/2026-01-26-fix-bug.patch
+
+set -e
+
+# --- Configuration ---
+# Same exclusions as generate-phase-patch.sh
+EXCLUSIONS=(
+  # Documentation
+  '.planning'
+
+  # Flutter/Dart generated
+  '*.g.dart'
+  '*.freezed.dart'
+  '*.gr.dart'
+  'generated'
+  '.dart_tool'
+
+  # Next.js/TypeScript generated
+  'node_modules'
+  '.next'
+  'dist'
+  'build'
+  '*.d.ts'
+  '.turbo'
+
+  # Common build artifacts
+  '*.lock'
+)
+
+# --- Parse arguments ---
+COMMIT_HASH="$1"
+OUTPUT_PATH="$2"
+
+# --- Validation ---
+if [ -z "$COMMIT_HASH" ] || [ -z "$OUTPUT_PATH" ]; then
+  echo "Error: Commit hash and output path required"
+  echo "Usage: $0 <commit-hash> <output-path>"
+  exit 1
+fi
+
+# --- Find git root ---
+GIT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
+if [ -z "$GIT_ROOT" ]; then
+  echo "Error: Not in a git repository"
+  exit 1
+fi
+cd "$GIT_ROOT"
+
+# --- Verify commit exists ---
+if ! git rev-parse "$COMMIT_HASH" >/dev/null 2>&1; then
+  echo "Error: Commit $COMMIT_HASH not found"
+  exit 1
+fi
+
+# --- Build exclusion arguments ---
+EXCLUDE_ARGS=""
+for pattern in "${EXCLUSIONS[@]}"; do
+  EXCLUDE_ARGS="$EXCLUDE_ARGS ':!$pattern'"
+done
+
+# --- Generate diff from parent commit to specified commit ---
+eval "git diff \"${COMMIT_HASH}^\" \"$COMMIT_HASH\" -- . $EXCLUDE_ARGS" > "$OUTPUT_PATH"
+
+# --- Check result ---
+if [ ! -s "$OUTPUT_PATH" ]; then
+  rm -f "$OUTPUT_PATH"
+  echo "No implementation changes outside excluded patterns"
+  echo "Patch skipped"
+  exit 0
+fi
+
+PATCH_LINES=$(wc -l < "$OUTPUT_PATH" | tr -d ' ')
+echo "Generated: $OUTPUT_PATH ($PATCH_LINES lines)"

package/scripts/ms-lookup/uv.lock

@@ -67,23 +67,6 @@ wheels = [
     { url = "https://files.pythonhosted.org/packages/8a/0e/97c33bf5009bdbac74fd2beace167cab3f978feb69cc36f1ef79360d6c4e/exceptiongroup-1.3.1-py3-none-any.whl", hash = "sha256:a7a39a3bd276781e98394987d3a5701d0c4edffb633bb7a5144577f82c773598", size = 16740, upload-time = "2025-11-21T23:01:53.443Z" },
 ]
 
-[[package]]
-name = "gsd-lookup"
-version = "1.0.0"
-source = { editable = "." }
-dependencies = [
-    { name = "diskcache" },
-    { name = "httpx" },
-    { name = "typer" },
-]
-
-[package.metadata]
-requires-dist = [
-    { name = "diskcache", specifier = ">=5.6.0" },
-    { name = "httpx", specifier = ">=0.25.0" },
-    { name = "typer", specifier = ">=0.9.0" },
-]
-
 [[package]]
 name = "h11"
 version = "0.16.0"
@@ -151,6 +134,23 @@ wheels = [
     { url = "https://files.pythonhosted.org/packages/b3/38/89ba8ad64ae25be8de66a6d463314cf1eb366222074cfda9ee839c56a4b4/mdurl-0.1.2-py3-none-any.whl", hash = "sha256:84008a41e51615a49fc9966191ff91509e3c40b939176e643fd50a5c2196b8f8", size = 9979, upload-time = "2022-08-14T12:40:09.779Z" },
 ]
 
+[[package]]
+name = "ms-lookup"
+version = "1.0.0"
+source = { editable = "." }
+dependencies = [
+    { name = "diskcache" },
+    { name = "httpx" },
+    { name = "typer" },
+]
+
+[package.metadata]
+requires-dist = [
+    { name = "diskcache", specifier = ">=5.6.0" },
+    { name = "httpx", specifier = ">=0.25.0" },
+    { name = "typer", specifier = ">=0.9.0" },
+]
+
 [[package]]
 name = "pygments"
 version = "2.19.2"

package/commands/ms/discuss-milestone.md

@@ -1,48 +0,0 @@
----
-name: ms:discuss-milestone
-description: Gather context for next milestone through adaptive questioning
----
-
-<objective>
-Help you figure out what to build in the next milestone through collaborative thinking.
-
-Purpose: After completing a milestone, explore what features you want to add, improve, or fix. Features first — scope and phases derive from what you want to build.
-Output: Context gathered, then routes to /ms:new-milestone
-</objective>
-
-<execution_context>
-@~/.claude/mindsystem/references/principles.md
-@~/.claude/mindsystem/workflows/discuss-milestone.md
-</execution_context>
-
-<context>
-**Load project state first:**
-@.planning/STATE.md
-
-**Load project:**
-@.planning/PROJECT.md
-
-**Load milestones (if exists):**
-@.planning/MILESTONES.md
-</context>
-
-<process>
-1. Verify previous milestone complete (or acknowledge active milestone)
-2. Present context from previous milestone (accomplishments, phase count)
-3. Follow discuss-milestone.md workflow with **ALL questions using AskUserQuestion**:
-   - Use AskUserQuestion: "What do you want to add, improve, or fix?" with feature categories
-   - Use AskUserQuestion to dig into features they mention
-   - Use AskUserQuestion to help them articulate what matters most
-   - Use AskUserQuestion for decision gate (ready / ask more / let me add context)
-4. Hand off to /ms:new-milestone with gathered context
-
-**CRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.**
-</process>
-
-<success_criteria>
-
-- Project state loaded and presented
-- Previous milestone context summarized
-- Milestone scope gathered through adaptive questioning
-- Context handed off to /ms:new-milestone
-  </success_criteria>