mindsystem-cc 3.0.0 → 3.1.0

package/agents/ms-executor.md

@@ -691,7 +691,6 @@ Progress: [progress bar]
 ```markdown
 Last session: [current date and time]
 Stopped at: Completed {phase}-{plan}-PLAN.md
-Resume file: [path to .continue-here if exists, else "None"]
 ```
 
 </state_updates>

package/agents/ms-roadmapper.md

@@ -303,7 +303,6 @@ Key sections:
 - Current Position (phase, plan, status, progress bar)
 - Performance Metrics
 - Accumulated Context (decisions, todos, blockers)
-- Session Continuity
 
 ## Draft Presentation Format
 

package/commands/ms/help.md

@@ -337,28 +337,6 @@ Check project status and intelligently route to next action.
 
 Usage: `/ms:progress`
 
-### Session Management
-
-**`/ms:resume-work`**
-Resume work from previous session with full context restoration.
-
-- Use when: you paused mid-phase and want to restore context and continue.
-- Reads STATE.md for project context
-- Shows current position and recent progress
-- Offers next actions based on project state
-
-Usage: `/ms:resume-work`
-
-**`/ms:pause-work`**
-Create context handoff when pausing work mid-phase.
-
-- Use when: you need to stop mid-stream and want a reliable handoff pointer for next time.
-- Creates `.continue-here` file with current state
-- Updates STATE.md session continuity section
-- Captures in-progress work context
-
-Usage: `/ms:pause-work`
-
 ### Debugging
 
 **`/ms:debug [issue description]`**
@@ -606,14 +584,6 @@ Common options:
 /ms:check-todos api             # Filter by area
 ```
 
-**Pausing and resuming mid-phase:**
-
-```
-/ms:pause-work                # Creates a handoff pointer
-# later...
-/ms:resume-work               # Restore context and continue
-```
-
 ## Getting Help
 
 - Read `.planning/PROJECT.md` for project vision

package/commands/ms/progress.md

@@ -31,7 +31,22 @@ Run /ms:new-project to start a new project.
 
 Exit.
 
-If missing STATE.md: suggest `/ms:new-project`.
+**If missing STATE.md but PROJECT.md or ROADMAP.md exist:**
+
+Reconstruct STATE.md 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 recent decisions, concerns
+4. Count pending todos in .planning/todos/pending/
+
+Write reconstructed STATE.md, then proceed to "load" step.
+
+```
+"STATE.md missing. Reconstructing from artifacts..."
+```
+
+If missing both STATE.md and PROJECT.md/ROADMAP.md: suggest `/ms:new-project`.
 
 **If ROADMAP.md missing but PROJECT.md exists:**
 
@@ -354,7 +369,6 @@ Ready to plan the next milestone.
 - Phase complete but next phase not planned → offer `/ms:plan-phase [next]`
 - All work complete → offer milestone completion
 - Blockers present → highlight before offering to continue
-- Handoff file exists → mention it, offer `/ms:resume-work`
   </step>
 
 </process>

package/commands/ms/remove-phase.md

@@ -79,8 +79,6 @@ ERROR: Cannot remove Phase {target}
 Only future phases can be removed:
 - Current phase: {current}
 - Phase {target} is current or completed
-
-To abandon current work, use /ms:pause-work instead.
 ```
 
 Exit.

package/mindsystem/templates/state.md

@@ -73,12 +73,6 @@ None yet.
 [Issues that affect future work]
 
 None yet.
-
-## Session Continuity
-
-Last session: [YYYY-MM-DD HH:MM]
-Stopped at: [Description of last completed action]
-Resume file: [Path to .continue-here*.md if exists, otherwise "None"]
 ```
 
 <purpose>
@@ -172,12 +166,6 @@ Updated after each plan completion.
 - Prefix with originating phase
 - Cleared when addressed
 
-### Session Continuity
-Enables instant resumption:
-- When was last session
-- What was last completed
-- Is there a .continue-here file to resume from
-
 </sections>
 
 <size_constraint>
@@ -219,6 +207,5 @@ The goal is "read once, know where we are" — if it's too long, that fails.
 - Current Position: Where we are now (phase, plan, status)
 - Performance Metrics: Velocity tracking
 - Accumulated Context: Recent decisions, pending todos, adhoc work, blockers
-- Session Continuity: Resume information
 
 </guidelines>

package/mindsystem/workflows/execute-plan.md

@@ -1455,7 +1455,6 @@ Update Session Continuity section in STATE.md to enable resumption in future ses
 ```markdown
 Last session: [current date and time]
 Stopped at: Completed {phase}-{plan}-PLAN.md
-Resume file: [path to .continue-here if exists, else "None"]
 ```
 
 **Size constraint note:** Keep STATE.md under 150 lines total.

package/mindsystem/workflows/transition.md

@@ -106,18 +106,6 @@ Wait for user decision.
 
 </step>
 
-<step name="cleanup_handoff">
-
-Check for lingering handoffs:
-
-```bash
-ls .planning/phases/XX-current/.continue-here*.md 2>/dev/null
-```
-
-If found, delete them — phase is complete, handoffs are stale.
-
-</step>
-
 <step name="update_roadmap">
 
 Update the roadmap file:
@@ -379,14 +367,12 @@ Update Session Continuity section in STATE.md to reflect transition completion.
 ```markdown
 Last session: [today]
 Stopped at: Phase [X] complete, ready to plan Phase [X+1]
-Resume file: None
 ```
 
 **Step complete when:**
 
 - [ ] Last session timestamp updated to current date and time
 - [ ] Stopped at describes phase completion and next phase
-- [ ] Resume file confirmed as None (transitions don't use resume files)
 
 </step>
 

package/package.json

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

package/commands/ms/pause-work.md

@@ -1,123 +0,0 @@
----
-name: ms:pause-work
-description: Create context handoff when pausing work mid-phase
-allowed-tools:
-  - Read
-  - Write
-  - Bash
----
-
-<objective>
-Create `.continue-here.md` handoff file to preserve complete work state across sessions.
-
-Enables seamless resumption in fresh session with full context restoration.
-</objective>
-
-<context>
-@.planning/STATE.md
-</context>
-
-<process>
-
-<step name="detect">
-Find current phase directory from most recently modified files.
-</step>
-
-<step name="gather">
-**Collect complete state for handoff:**
-
-1. **Current position**: Which phase, which plan, which task
-2. **Work completed**: What got done this session
-3. **Work remaining**: What's left in current plan/phase
-4. **Decisions made**: Key decisions and rationale
-5. **Blockers/issues**: Anything stuck
-6. **Mental context**: The approach, next steps, "vibe"
-7. **Files modified**: What's changed but not committed
-
-Ask user for clarifications if needed.
-</step>
-
-<step name="write">
-**Write handoff to `.planning/phases/XX-name/.continue-here.md`:**
-
-```markdown
----
-phase: XX-name
-task: 3
-total_tasks: 7
-status: in_progress
-last_updated: [timestamp]
----
-
-<current_state>
-[Where exactly are we? Immediate context]
-</current_state>
-
-<completed_work>
-
-- Task 1: [name] - Done
-- Task 2: [name] - Done
-- Task 3: [name] - In progress, [what's done]
-  </completed_work>
-
-<remaining_work>
-
-- Task 3: [what's left]
-- Task 4: Not started
-- Task 5: Not started
-  </remaining_work>
-
-<decisions_made>
-
-- Decided to use [X] because [reason]
-- Chose [approach] over [alternative] because [reason]
-  </decisions_made>
-
-<blockers>
-- [Blocker 1]: [status/workaround]
-</blockers>
-
-<context>
-[Mental state, what were you thinking, the plan]
-</context>
-
-<next_action>
-Start with: [specific first action when resuming]
-</next_action>
-```
-
-Be specific enough for a fresh Claude to understand immediately.
-</step>
-
-<step name="commit">
-```bash
-git add .planning/phases/*/.continue-here.md
-git commit -m "wip: [phase-name] paused at task [X]/[Y]"
-```
-</step>
-
-<step name="confirm">
-```
-✓ Handoff created: .planning/phases/[XX-name]/.continue-here.md
-
-Current state:
-
-- Phase: [XX-name]
-- Task: [X] of [Y]
-- Status: [in_progress/blocked]
-- Committed as WIP
-
-To resume: /ms:resume-work
-
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] .continue-here.md created in correct phase directory
-- [ ] All sections filled with specific content
-- [ ] Committed as WIP
-- [ ] User knows location and how to resume
-</success_criteria>
-```

package/commands/ms/resume-work.md

@@ -1,40 +0,0 @@
----
-name: ms:resume-work
-description: Resume work from previous session with full context restoration
-allowed-tools:
-  - Read
-  - Bash
-  - Write
-  - AskUserQuestion
-  - SlashCommand
----
-
-<objective>
-Restore complete project context and resume work seamlessly from previous session.
-
-Routes to the resume-project workflow which handles:
-
-- STATE.md loading (or reconstruction if missing)
-- Checkpoint detection (.continue-here files)
-- Incomplete work detection (PLAN without SUMMARY)
-- Status presentation
-- Context-aware next action routing
-  </objective>
-
-<execution_context>
-@~/.claude/mindsystem/workflows/resume-project.md
-</execution_context>
-
-<process>
-**Follow the resume-project workflow** from `@~/.claude/mindsystem/workflows/resume-project.md`.
-
-The workflow handles all resumption logic including:
-
-1. Project existence verification
-2. STATE.md loading or reconstruction
-3. Checkpoint and incomplete work detection
-4. Visual status presentation
-5. Context-aware option offering (checks CONTEXT.md before suggesting plan vs discuss)
-6. Routing to appropriate next command
-7. Session continuity updates
-   </process>

package/mindsystem/templates/continue-here.md

@@ -1,78 +0,0 @@
-# Continue-Here Template
-
-Copy and fill this structure for `.planning/phases/XX-name/.continue-here.md`:
-
-```yaml
----
-phase: XX-name
-task: 3
-total_tasks: 7
-status: in_progress
-last_updated: 2025-01-15T14:30:00Z
----
-```
-
-```markdown
-<current_state>
-[Where exactly are we? What's the immediate context?]
-</current_state>
-
-<completed_work>
-[What got done this session - be specific]
-
-- Task 1: [name] - Done
-- Task 2: [name] - Done
-- Task 3: [name] - In progress, [what's done on it]
-</completed_work>
-
-<remaining_work>
-[What's left in this phase]
-
-- Task 3: [name] - [what's left to do]
-- Task 4: [name] - Not started
-- Task 5: [name] - Not started
-</remaining_work>
-
-<decisions_made>
-[Key decisions and why - so next session doesn't re-debate]
-
-- Decided to use [X] because [reason]
-- Chose [approach] over [alternative] because [reason]
-</decisions_made>
-
-<blockers>
-[Anything stuck or waiting on external factors]
-
-- [Blocker 1]: [status/workaround]
-</blockers>
-
-<context>
-[Mental state, "vibe", anything that helps resume smoothly]
-
-[What were you thinking about? What was the plan?
-This is the "pick up exactly where you left off" context.]
-</context>
-
-<next_action>
-[The very first thing to do when resuming]
-
-Start with: [specific action]
-</next_action>
-```
-
-<yaml_fields>
-Required YAML frontmatter:
-
-- `phase`: Directory name (e.g., `02-authentication`)
-- `task`: Current task number
-- `total_tasks`: How many tasks in phase
-- `status`: `in_progress`, `blocked`, `almost_done`
-- `last_updated`: ISO timestamp
-</yaml_fields>
-
-<guidelines>
-- Be specific enough that a fresh Claude instance understands immediately
-- Include WHY decisions were made, not just what
-- The `<next_action>` should be actionable without reading anything else
-- This file gets DELETED after resume - it's not permanent storage
-</guidelines>