mindsystem-cc 3.2.2 → 3.3.0

package/mindsystem/workflows/complete-milestone.md

@@ -22,12 +22,14 @@ This is the ritual that separates "development" from "shipped."
 
 When a milestone completes, this workflow:
 
-1. Extracts full milestone details to `.planning/milestones/v[X.Y]-ROADMAP.md`
-2. Archives requirements to `.planning/milestones/v[X.Y]-REQUIREMENTS.md`
-3. Updates ROADMAP.md to replace milestone details with one-line summary
-4. Deletes REQUIREMENTS.md (fresh one created for next milestone)
-5. Performs full PROJECT.md evolution review
-6. Offers to create next milestone inline
+1. Consolidates phase decisions into `.planning/milestones/v[X.Y]-DECISIONS.md`
+2. Cleans up phase artifacts (PLAN, CONTEXT, RESEARCH, DESIGN files deleted)
+3. Extracts full milestone details to `.planning/milestones/v[X.Y]-ROADMAP.md`
+4. Archives requirements to `.planning/milestones/v[X.Y]-REQUIREMENTS.md`
+5. Updates ROADMAP.md to replace milestone details with one-line summary
+6. Deletes REQUIREMENTS.md (fresh one created for next milestone)
+7. Performs full PROJECT.md evolution review
+8. Routes to `/ms:new-milestone` for next milestone
 
 **Context Efficiency:**
 
@@ -90,8 +92,6 @@ cat .planning/config.json 2>/dev/null
 
 </config-check>
 
-<if mode="yolo">
-
 ```
 ⚡ Auto-approved: Milestone scope verification
 
@@ -100,23 +100,50 @@ cat .planning/config.json 2>/dev/null
 Proceeding to stats gathering...
 ```
 
-Proceed directly to gather_stats step.
+Proceed directly to consolidate_decisions step.
+
+</step>
+
+<step name="consolidate_decisions">
 
-</if>
+Consolidate phase decisions before archiving.
 
-<if mode="interactive" OR="custom with gates.confirm_milestone_scope true">
+**Spawn ms-consolidator agent:**
 
 ```
-Ready to mark this milestone as shipped?
-(yes / wait / adjust scope)
+Task(
+  prompt="Consolidate decisions from milestone v[X.Y] [Name].
+
+Phase range: [PHASE_START]-[PHASE_END]
+Phase directories:
+- .planning/phases/01-foundation
+- .planning/phases/02-auth
+- [etc. for all phases in milestone]
+
+Extract decisions from PLAN, CONTEXT, RESEARCH, DESIGN files.
+Create v[X.Y]-DECISIONS.md in .planning/milestones/.
+Delete source files (preserve SUMMARY, VERIFICATION, UAT).",
+  subagent_type="ms-consolidator"
+)
+```
+
+**Wait for completion and verify:**
+
+```bash
+ls .planning/milestones/v[X.Y]-DECISIONS.md
 ```
 
-Wait for confirmation.
+**Present consolidation summary:**
+
+```
+✓ Decisions consolidated: [N] decisions in [M] categories
+✓ Source files cleaned: PLAN, CONTEXT, RESEARCH, DESIGN deleted
+✓ Preserved: SUMMARY, VERIFICATION, UAT files
 
-If "adjust scope": Ask which phases should be included.
-If "wait": Stop, user will return when ready.
+Report: .planning/milestones/v[X.Y]-DECISIONS.md
+```
 
-</if>
+Continue to gather_stats step.
 
 </step>
 
@@ -622,6 +649,7 @@ Commit milestone completion including archive files and deletions.
 
 ```bash
 # Stage archive files (new)
+git add .planning/milestones/v[X.Y]-DECISIONS.md
 git add .planning/milestones/v[X.Y]-ROADMAP.md
 git add .planning/milestones/v[X.Y]-REQUIREMENTS.md
 git add .planning/milestones/v[X.Y]-MILESTONE-AUDIT.md 2>/dev/null || true
@@ -639,10 +667,14 @@ git commit -m "$(cat <<'EOF'
 chore: complete v[X.Y] milestone
 
 Archived:
+- milestones/v[X.Y]-DECISIONS.md (consolidated decisions)
 - milestones/v[X.Y]-ROADMAP.md
 - milestones/v[X.Y]-REQUIREMENTS.md
 - milestones/v[X.Y]-MILESTONE-AUDIT.md (if audit was run)
 
+Cleaned:
+- Phase PLAN, CONTEXT, RESEARCH, DESIGN files (consolidated into DECISIONS.md)
+
 Deleted (fresh for next milestone):
 - ROADMAP.md
 - REQUIREMENTS.md
@@ -681,20 +713,19 @@ Tag: v[X.Y]
 
 ## ▶ Next Up
 
-**Discuss Next Milestone** — figure out what to build next
+**Start Next Milestone** — define goals and requirements
 
-`/ms:discuss-milestone`
+`/ms:new-milestone`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Next milestone flow:**
-1. `/ms:discuss-milestone` — thinking partner, creates context file
-2. `/ms:new-milestone` — update PROJECT.md with new goals
-3. `/ms:research-project` — (optional) research ecosystem
-4. `/ms:define-requirements` — scope what to build
-5. `/ms:create-roadmap` — plan how to build it
+1. `/ms:new-milestone` — discover what to build, update PROJECT.md with goals
+2. `/ms:research-project` — (optional) research ecosystem
+3. `/ms:define-requirements` — scope what to build
+4. `/ms:create-roadmap` — plan how to build it
 
 ---
 ```
@@ -743,6 +774,8 @@ If yes → milestone. If no → keep working.
 
 Milestone completion is successful when:
 
+- [ ] Decisions consolidated (milestones/v[X.Y]-DECISIONS.md created)
+- [ ] Phase artifacts cleaned (PLAN, CONTEXT, RESEARCH, DESIGN deleted)
 - [ ] MILESTONES.md entry created with stats and accomplishments
 - [ ] PROJECT.md full evolution review completed
 - [ ] All shipped requirements moved to Validated in PROJECT.md
@@ -754,6 +787,6 @@ Milestone completion is successful when:
 - [ ] STATE.md updated with fresh project reference
 - [ ] Git tag created (v[X.Y])
 - [ ] Milestone commit made (includes archive files and deletion)
-- [ ] User knows next steps (starting with /ms:define-requirements)
+- [ ] User knows next steps (starting with /ms:new-milestone)
 
 </success_criteria>

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

@@ -83,7 +83,6 @@ cat .planning/config.json 2>/dev/null
 ```
 </config-check>
 
-<if mode="yolo">
 ```
 ⚡ Auto-approved: Execute {phase}-{plan}-PLAN.md
 [Plan X of Y for Phase Z]
@@ -92,20 +91,6 @@ Starting execution...
 ```
 
 Proceed directly to parse_segments step.
-</if>
-
-<if mode="interactive" OR="custom with gates.execute_next_plan true">
-Present:
-
-```
-Found plan to execute: {phase}-{plan}-PLAN.md
-[Plan X of Y for Phase Z]
-
-Proceed with execution?
-```
-
-Wait for confirmation before proceeding.
-</if>
 </step>
 
 <step name="record_start_time">
@@ -1465,21 +1450,15 @@ Before proceeding, check SUMMARY.md content.
 
 If "Issues Encountered" is NOT "None":
 
-<if mode="yolo">
 ```
 ⚡ Auto-approved: Issues acknowledgment
 ⚠️ Note: Issues were encountered during execution:
 - [Issue 1]
 - [Issue 2]
-(Logged - continuing in yolo mode)
+(Logged - continuing)
 ```
 
 Continue without waiting.
-</if>
-
-<if mode="interactive" OR="custom with gates.issues_review true">
-Present issues and wait for acknowledgment before proceeding.
-</if>
 </step>
 
 <step name="update_roadmap">
@@ -1670,7 +1649,6 @@ Identify the next unexecuted plan:
 - Find the first PLAN.md file that has no matching SUMMARY.md
 - Read its `<objective>` section
 
-<if mode="yolo">
 ```
 Plan {phase}-{plan} complete.
 Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
@@ -1681,36 +1659,6 @@ Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
 ```
 
 Loop back to identify_plan step automatically.
-</if>
-
-<if mode="interactive" OR="custom with gates.execute_next_plan true">
-```
-Plan {phase}-{plan} complete.
-Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
-
-{Y} of {X} plans complete for Phase {Z}.
-
----
-
-## ▶ Next Up
-
-**Phase {X}: [Phase Name]** — [goal from ROADMAP.md]
-
-`/ms:execute-phase {phase-number}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/ms:verify-work {phase}` — manual acceptance testing before continuing
-- Review what was built before continuing
-
----
-```
-
-Wait for user to clear and run next command.
-</if>
 
 **STOP here if Route A applies. Do not continue to Step 3.**
 

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

@@ -629,46 +629,7 @@ See ~/.claude/mindsystem/references/scope-estimation.md for complete guidance.
 </step>
 
 <step name="confirm_breakdown">
-<if mode="yolo">
 Auto-approve and proceed to write_phase_prompt.
-</if>
-
-<if mode="interactive">
-Present breakdown with wave structure:
-
-```
-Phase [X] breakdown:
-
-## Execution Waves
-
-**Wave 1 (parallel):**
-  {phase}-01: [Plan Name] [autonomous]
-    - Task: [brief]
-    - Task: [brief]
-
-  {phase}-02: [Plan Name] [autonomous]
-    - Task: [brief]
-    - Task: [brief]
-
-**Wave 2 (parallel):**
-  {phase}-03: [Plan Name] (depends: 01, 02) [autonomous]
-    - Task: [brief]
-
-**Wave 3:**
-  {phase}-04: [Plan Name] (depends: 03) [has checkpoint]
-    - Task: [brief]
-    - Checkpoint: [type]
-
----
-Total: [N] plans in [M] waves
-Parallel plans: [X]
-Sequential plans: [Y]
-
-Does this look right? (yes / adjust / start over)
-```
-
-Wait for confirmation. If "adjust": revise. If "start over": return to gather_phase_context.
-</if>
 </step>
 
 <step name="write_phase_prompt">