mindsystem-cc 3.19.0 → 3.21.0

package/commands/ms/list-phase-assumptions.md

@@ -1,56 +0,0 @@
----
-name: ms:list-phase-assumptions
-description: Surface Claude's assumptions about a phase approach before planning
-argument-hint: "[phase]"
-allowed-tools:
-  - Read
-  - Bash
-  - Grep
-  - Glob
----
-
-<objective>
-Analyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.
-
-Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong.
-Output: Conversational output only (no file creation) - ends with "What do you think?" prompt
-</objective>
-
-<execution_context>
-@~/.claude/mindsystem/workflows/list-phase-assumptions.md
-</execution_context>
-
-<context>
-Phase number: $ARGUMENTS (required)
-
-**Normalize phase number:**
-```bash
-PHASE_ARG="$ARGUMENTS"
-PHASE=$(printf "%02d" "$PHASE_ARG" 2>/dev/null || echo "$PHASE_ARG")
-```
-
-**Load project state first:**
-@.planning/STATE.md
-
-**Load roadmap:**
-@.planning/ROADMAP.md
-</context>
-
-<process>
-1. Validate phase number argument (error if missing or invalid)
-2. Check if phase exists in roadmap
-3. Follow list-phase-assumptions.md workflow:
-   - Analyze roadmap description
-   - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies
-   - Present assumptions clearly
-   - Prompt "What do you think?"
-4. Gather feedback and offer next steps
-</process>
-
-<success_criteria>
-
-- Phase validated against roadmap
-- Assumptions surfaced across five areas
-- User prompted for feedback
-- User knows next steps (discuss context, plan phase, or correct assumptions)
-  </success_criteria>

package/mindsystem/workflows/list-phase-assumptions.md

@@ -1,178 +0,0 @@
-<purpose>
-Surface Claude's assumptions about a phase before planning, enabling users to correct misconceptions early.
-
-Key difference from discuss-phase: This is ANALYSIS of what Claude thinks, not INTAKE of what user knows. No file output - purely conversational to prompt discussion.
-</purpose>
-
-<process>
-
-<step name="validate_phase" priority="first">
-Phase number: $ARGUMENTS (required)
-
-**If argument missing:**
-
-```
-Error: Phase number required.
-
-Usage: /ms:list-phase-assumptions [phase-number]
-Example: /ms:list-phase-assumptions 3
-```
-
-Exit workflow.
-
-**If argument provided:**
-Validate phase exists in roadmap:
-
-```bash
-cat .planning/ROADMAP.md | grep -i "Phase ${PHASE}"
-```
-
-**If phase not found:**
-
-```
-Error: Phase ${PHASE} not found in roadmap.
-
-Available phases:
-[list phases from roadmap]
-```
-
-Exit workflow.
-
-**If phase found:**
-Parse phase details from roadmap:
-
-- Phase number
-- Phase name
-- Phase description/goal
-- Any scope details mentioned
-
-Continue to analyze_phase.
-</step>
-
-<step name="analyze_phase">
-Based on roadmap description and project context, identify assumptions across five areas:
-
-**1. Technical Approach:**
-What libraries, frameworks, patterns, or tools would Claude use?
-- "I'd use X library because..."
-- "I'd follow Y pattern because..."
-- "I'd structure this as Z because..."
-
-**2. Implementation Order:**
-What would Claude build first, second, third?
-- "I'd start with X because it's foundational"
-- "Then Y because it depends on X"
-- "Finally Z because..."
-
-**3. Scope Boundaries:**
-What's included vs excluded in Claude's interpretation?
-- "This phase includes: A, B, C"
-- "This phase does NOT include: D, E, F"
-- "Boundary ambiguities: G could go either way"
-
-**4. Risk Areas:**
-Where does Claude expect complexity or challenges?
-- "The tricky part is X because..."
-- "Potential issues: Y, Z"
-- "I'd watch out for..."
-
-**5. Dependencies:**
-What does Claude assume exists or needs to be in place?
-- "This assumes X from previous phases"
-- "External dependencies: Y, Z"
-- "This will be consumed by..."
-
-Be honest about uncertainty. Mark assumptions with confidence levels:
-- "Fairly confident: ..." (clear from roadmap)
-- "Assuming: ..." (reasonable inference)
-- "Unclear: ..." (could go multiple ways)
-</step>
-
-<step name="present_assumptions">
-Present assumptions in a clear, scannable format:
-
-```
-## My Assumptions for Phase ${PHASE}: ${PHASE_NAME}
-
-### Technical Approach
-[List assumptions about how to implement]
-
-### Implementation Order
-[List assumptions about sequencing]
-
-### Scope Boundaries
-**In scope:** [what's included]
-**Out of scope:** [what's excluded]
-**Ambiguous:** [what could go either way]
-
-### Risk Areas
-[List anticipated challenges]
-
-### Dependencies
-**From prior phases:** [what's needed]
-**External:** [third-party needs]
-**Feeds into:** [what future phases need from this]
-
----
-
-**What do you think?**
-
-Are these assumptions accurate? Let me know:
-- What I got right
-- What I got wrong
-- What I'm missing
-```
-
-Wait for user response.
-</step>
-
-<step name="gather_feedback">
-**If user provides corrections:**
-
-Acknowledge the corrections:
-
-```
-Got it. Key corrections:
-- [correction 1]
-- [correction 2]
-
-This changes my understanding significantly. [Summarize new understanding]
-```
-
-**If user confirms assumptions:**
-
-```
-Great, assumptions validated.
-```
-
-Continue to offer_next.
-</step>
-
-<step name="offer_next">
-Present next steps:
-
-```
-What's next?
-1. Discuss context (/ms:discuss-phase ${PHASE}) - Let me ask you questions to build comprehensive context
-2. Plan this phase (/ms:plan-phase ${PHASE}) - Create detailed execution plans
-3. Re-examine assumptions - I'll analyze again with your corrections
-4. Done for now
-```
-
-Wait for user selection.
-
-If "Discuss context": Note that CONTEXT.md will incorporate any corrections discussed here
-If "Plan this phase": Proceed knowing assumptions are understood
-If "Re-examine": Return to analyze_phase with updated understanding
-</step>
-
-</process>
-
-<success_criteria>
-- Phase number validated against roadmap
-- Assumptions surfaced across five areas: technical approach, implementation order, scope, risks, dependencies
-- Confidence levels marked where appropriate
-- "What do you think?" prompt presented
-- User feedback acknowledged
-- Clear next steps offered
-</success_criteria>

package/scripts/archive-milestone-files.sh

@@ -1,68 +0,0 @@
-#!/bin/bash
-#
-# archive-milestone-files.sh
-# Moves optional milestone files (audit, context, research) to the
-# milestone archive directory. Skips silently if files don't exist.
-#
-# Usage: ./scripts/archive-milestone-files.sh <version>
-# Example: ./scripts/archive-milestone-files.sh v1.0
-
-set -e
-
-# --- Validation ---
-if [ -z "$1" ]; then
-  echo "Error: Version argument required"
-  echo "Usage: $0 <version>"
-  exit 1
-fi
-
-VERSION="$1"
-
-# --- Find .planning from 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
-
-PLANNING_DIR="$GIT_ROOT/.planning"
-MILESTONE_DIR="$PLANNING_DIR/milestones/$VERSION"
-
-if [ ! -d "$MILESTONE_DIR" ]; then
-  echo "Error: Milestone directory not found at $MILESTONE_DIR"
-  echo "Run archive_milestone step first to create it"
-  exit 1
-fi
-
-# --- Move files ---
-ARCHIVED=0
-
-# Milestone audit
-if [ -f "$PLANNING_DIR/${VERSION}-MILESTONE-AUDIT.md" ]; then
-  mv "$PLANNING_DIR/${VERSION}-MILESTONE-AUDIT.md" "$MILESTONE_DIR/MILESTONE-AUDIT.md"
-  echo "Archived: ${VERSION}-MILESTONE-AUDIT.md → MILESTONE-AUDIT.md"
-  ARCHIVED=$((ARCHIVED + 1))
-fi
-
-# Milestone context
-if [ -f "$PLANNING_DIR/MILESTONE-CONTEXT.md" ]; then
-  mv "$PLANNING_DIR/MILESTONE-CONTEXT.md" "$MILESTONE_DIR/CONTEXT.md"
-  echo "Archived: MILESTONE-CONTEXT.md → CONTEXT.md"
-  ARCHIVED=$((ARCHIVED + 1))
-fi
-
-# Research directory
-if [ -d "$PLANNING_DIR/research" ]; then
-  mv "$PLANNING_DIR/research" "$MILESTONE_DIR/research"
-  echo "Archived: research/ → research/"
-  ARCHIVED=$((ARCHIVED + 1))
-fi
-
-if [ "$ARCHIVED" -eq 0 ]; then
-  echo "No optional files to archive (audit, context, research all absent)"
-else
-  echo ""
-  echo "Archived $ARCHIVED item(s) to milestones/$VERSION/"
-fi
-
-exit 0

package/scripts/archive-milestone-phases.sh

@@ -1,138 +0,0 @@
-#!/bin/bash
-#
-# archive-milestone-phases.sh
-# Consolidates phase summaries, deletes raw artifacts, and moves phase
-# directories to the milestone archive.
-#
-# Usage: ./scripts/archive-milestone-phases.sh <start_phase> <end_phase> <version>
-# Example: ./scripts/archive-milestone-phases.sh 1 6 v1.0
-
-set -e
-
-# --- Validation ---
-if [ -z "$1" ] || [ -z "$2" ] || [ -z "$3" ]; then
-  echo "Error: Three arguments required"
-  echo "Usage: $0 <start_phase> <end_phase> <version>"
-  exit 1
-fi
-
-START="$1"
-END="$2"
-VERSION="$3"
-
-if ! [[ "$START" =~ ^[0-9]+$ ]] || ! [[ "$END" =~ ^[0-9]+$ ]]; then
-  echo "Error: start_phase and end_phase must be numeric"
-  echo "Usage: $0 <start_phase> <end_phase> <version>"
-  exit 1
-fi
-
-if [ "$START" -gt "$END" ]; then
-  echo "Error: Start phase ($START) cannot exceed end phase ($END)"
-  exit 1
-fi
-
-# --- Find .planning from 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
-
-PHASES_DIR="$GIT_ROOT/.planning/phases"
-if [ ! -d "$PHASES_DIR" ]; then
-  echo "Error: Phases directory not found at $PHASES_DIR"
-  exit 1
-fi
-
-MILESTONE_DIR="$GIT_ROOT/.planning/milestones/$VERSION"
-if [ ! -d "$MILESTONE_DIR" ]; then
-  echo "Error: Milestone directory not found at $MILESTONE_DIR"
-  echo "Run archive_milestone step first to create it"
-  exit 1
-fi
-
-# --- Helper: check if phase number is in range (supports decimals like 02.1) ---
-in_range() {
-  local phase_num="$1"
-  echo "$phase_num" | awk -v s="$START" -v e="$END" '{
-    # Strip leading zeros for comparison
-    val = $1 + 0
-    if (val >= s && val <= e + 0.999) exit 0
-    else exit 1
-  }'
-}
-
-# --- Stage 1: Consolidate summaries ---
-SUMMARIES_FILE="$MILESTONE_DIR/PHASE-SUMMARIES.md"
-SUMMARY_COUNT=0
-
-echo "# Phase Summaries: $VERSION" > "$SUMMARIES_FILE"
-echo "" >> "$SUMMARIES_FILE"
-
-for dir in "$PHASES_DIR"/*/; do
-  [ -d "$dir" ] || continue
-  dirname=$(basename "$dir")
-  phase_num="${dirname%%-*}"
-  phase_name="${dirname#*-}"
-
-  if in_range "$phase_num"; then
-    has_summaries=false
-    for f in "$dir"/*-SUMMARY.md; do
-      [ -f "$f" ] || continue
-      if [ "$has_summaries" = false ]; then
-        echo "## Phase $phase_num: $phase_name" >> "$SUMMARIES_FILE"
-        echo "" >> "$SUMMARIES_FILE"
-        has_summaries=true
-      fi
-      plan_file=$(basename "$f")
-      plan_id="${plan_file%-SUMMARY.md}"
-      echo "### $plan_id" >> "$SUMMARIES_FILE"
-      echo "" >> "$SUMMARIES_FILE"
-      cat "$f" >> "$SUMMARIES_FILE"
-      echo "" >> "$SUMMARIES_FILE"
-      SUMMARY_COUNT=$((SUMMARY_COUNT + 1))
-    done
-  fi
-done
-
-echo "Stage 1: Consolidated $SUMMARY_COUNT summaries to PHASE-SUMMARIES.md"
-
-# --- Stage 2: Delete artifacts ---
-DELETED=0
-for dir in "$PHASES_DIR"/*/; do
-  [ -d "$dir" ] || continue
-  dirname=$(basename "$dir")
-  phase_num="${dirname%%-*}"
-
-  if in_range "$phase_num"; then
-    for f in "$dir"/*-CONTEXT.md "$dir"/*-DESIGN.md "$dir"/*-RESEARCH.md \
-             "$dir"/*-SUMMARY.md "$dir"/*-UAT.md "$dir"/*-VERIFICATION.md \
-             "$dir"/*-EXECUTION-ORDER.md; do
-      if [ -f "$f" ]; then
-        rm -f "$f"
-        DELETED=$((DELETED + 1))
-      fi
-    done
-  fi
-done
-
-echo "Stage 2: Deleted $DELETED artifact files"
-
-# --- Stage 3: Move phase directories ---
-mkdir -p "$MILESTONE_DIR/phases"
-MOVED=0
-for dir in "$PHASES_DIR"/*/; do
-  [ -d "$dir" ] || continue
-  dirname=$(basename "$dir")
-  phase_num="${dirname%%-*}"
-
-  if in_range "$phase_num"; then
-    mv "$dir" "$MILESTONE_DIR/phases/$dirname"
-    MOVED=$((MOVED + 1))
-  fi
-done
-
-echo "Stage 3: Moved $MOVED phase directories to milestones/$VERSION/phases/"
-echo ""
-echo "Archive complete: $SUMMARY_COUNT summaries, $DELETED artifacts deleted, $MOVED dirs moved"
-exit 0