mindforge-cc 9.0.0 → 10.0.1

package/.agent/workflows/mindforge-remove-phase.md

@@ -1,155 +0,0 @@
-<purpose>
-Remove an unstarted future phase from the project roadmap, delete its directory, renumber all subsequent phases to maintain a clean linear sequence, and commit the change. The git commit serves as the historical record of removal.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="parse_arguments">
-Parse the command arguments:
-- Argument is the phase number to remove (integer or decimal)
-- Example: `/mindforge-remove-phase 17` → phase = 17
-- Example: `/mindforge-remove-phase 16.1` → phase = 16.1
-
-If no argument provided:
-
-```
-ERROR: Phase number required
-Usage: /mindforge-remove-phase <phase-number>
-Example: /mindforge-remove-phase 17
-```
-
-Exit.
-</step>
-
-<step name="init_context">
-Load phase operation context:
-
-```bash
-INIT=$(node ".agent/bin/mindforge-tools.cjs" init phase-op "${target}")
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Extract: `phase_found`, `phase_dir`, `phase_number`, `commit_docs`, `roadmap_exists`.
-
-Also read STATE.md and ROADMAP.md content for parsing current position.
-</step>
-
-<step name="validate_future_phase">
-Verify the phase is a future phase (not started):
-
-1. Compare target phase to current phase from STATE.md
-2. Target must be > current phase number
-
-If target <= current phase:
-
-```
-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 /mindforge-pause-work instead.
-```
-
-Exit.
-</step>
-
-<step name="confirm_removal">
-Present removal summary and confirm:
-
-```
-Removing Phase {target}: {Name}
-
-This will:
-- Delete: .planning/phases/{target}-{slug}/
-- Renumber all subsequent phases
-- Update: ROADMAP.md, STATE.md
-
-Proceed? (y/n)
-```
-
-Wait for confirmation.
-</step>
-
-<step name="execute_removal">
-**Delegate the entire removal operation to mindforge-tools:**
-
-```bash
-RESULT=$(node ".agent/bin/mindforge-tools.cjs" phase remove "${target}")
-```
-
-If the phase has executed plans (SUMMARY.md files), mindforge-tools will error. Use `--force` only if the user confirms:
-
-```bash
-RESULT=$(node ".agent/bin/mindforge-tools.cjs" phase remove "${target}" --force)
-```
-
-The CLI handles:
-- Deleting the phase directory
-- Renumbering all subsequent directories (in reverse order to avoid conflicts)
-- Renaming all files inside renumbered directories (PLAN.md, SUMMARY.md, etc.)
-- Updating ROADMAP.md (removing section, renumbering all phase references, updating dependencies)
-- Updating STATE.md (decrementing phase count)
-
-Extract from result: `removed`, `directory_deleted`, `renamed_directories`, `renamed_files`, `roadmap_updated`, `state_updated`.
-</step>
-
-<step name="commit">
-Stage and commit the removal:
-
-```bash
-node ".agent/bin/mindforge-tools.cjs" commit "chore: remove phase {target} ({original-phase-name})" --files .planning/
-```
-
-The commit message preserves the historical record of what was removed.
-</step>
-
-<step name="completion">
-Present completion summary:
-
-```
-Phase {target} ({original-name}) removed.
-
-Changes:
-- Deleted: .planning/phases/{target}-{slug}/
-- Renumbered: {N} directories and {M} files
-- Updated: ROADMAP.md, STATE.md
-- Committed: chore: remove phase {target} ({original-name})
-
----
-
-## What's Next
-
-Would you like to:
-- `/mindforge-progress` — see updated roadmap status
-- Continue with current phase
-- Review roadmap
-
----
-```
-</step>
-
-</process>
-
-<anti_patterns>
-
-- Don't remove completed phases (have SUMMARY.md files) without --force
-- Don't remove current or past phases
-- Don't manually renumber — use `mindforge-tools phase remove` which handles all renumbering
-- Don't add "removed phase" notes to STATE.md — git commit is the record
-- Don't modify completed phase directories
-</anti_patterns>
-
-<success_criteria>
-Phase removal is complete when:
-
-- [ ] Target phase validated as future/unstarted
-- [ ] `mindforge-tools phase remove` executed successfully
-- [ ] Changes committed with descriptive message
-- [ ] User informed of changes
-</success_criteria>

package/.agent/workflows/mindforge-remove-workspace.md

@@ -1,90 +0,0 @@
-<purpose>
-Remove a MindForge workspace, cleaning up git worktrees and deleting the workspace directory.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-## 1. Setup
-
-Extract workspace name from $ARGUMENTS.
-
-```bash
-INIT=$(node ".agent/bin/mindforge-tools.cjs" init remove-workspace "$WORKSPACE_NAME")
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Parse JSON for: `workspace_name`, `workspace_path`, `has_manifest`, `strategy`, `repos`, `repo_count`, `dirty_repos`, `has_dirty_repos`.
-
-**If no workspace name provided:**
-
-First run `/mindforge-list-workspaces` to show available workspaces, then ask:
-
-Use AskUserQuestion:
-- header: "Remove Workspace"
-- question: "Which workspace do you want to remove?"
-- requireAnswer: true
-
-Re-run init with the provided name.
-
-## 2. Safety Checks
-
-**If `has_dirty_repos` is true:**
-
-```
-Cannot remove workspace "$WORKSPACE_NAME" — the following repos have uncommitted changes:
-
-  - repo1
-  - repo2
-
-Commit or stash changes in these repos before removing the workspace:
-  cd $WORKSPACE_PATH/repo1
-  git stash   # or git commit
-```
-
-Exit. Do NOT proceed.
-
-## 3. Confirm Removal
-
-Use AskUserQuestion:
-- header: "Confirm Removal"
-- question: "Remove workspace '$WORKSPACE_NAME' at $WORKSPACE_PATH? This will delete all files in the workspace directory. Type the workspace name to confirm:"
-- requireAnswer: true
-
-**If answer does not match `$WORKSPACE_NAME`:** Exit with "Removal cancelled."
-
-## 4. Clean Up Worktrees
-
-**If strategy is `worktree`:**
-
-For each repo in the workspace:
-
-```bash
-cd "$SOURCE_REPO_PATH"
-git worktree remove "$WORKSPACE_PATH/$REPO_NAME" 2>&1 || true
-```
-
-If `git worktree remove` fails, warn but continue:
-```
-Warning: Could not remove worktree for $REPO_NAME — source repo may have been moved or deleted.
-```
-
-## 5. Delete Workspace Directory
-
-```bash
-rm -rf "$WORKSPACE_PATH"
-```
-
-## 6. Report
-
-```
-Workspace "$WORKSPACE_NAME" removed.
-
-  Path: $WORKSPACE_PATH (deleted)
-  Repos: $REPO_COUNT worktrees cleaned up
-```
-
-</process>

package/.agent/workflows/mindforge-research-phase.md

@@ -1,74 +0,0 @@
-<purpose>
-Research how to implement a phase. Spawns mindforge-phase-researcher with phase context.
-
-Standalone research command. For most workflows, use `/mindforge-plan-phase` which integrates research automatically.
-</purpose>
-
-<process>
-
-## Step 0: Resolve Model Profile
-
-@.agent/references/model-profile-resolution.md
-
-Resolve model for:
-- `mindforge-phase-researcher`
-
-## Step 1: Normalize and Validate Phase
-
-@.agent/references/phase-argument-parsing.md
-
-```bash
-PHASE_INFO=$(node ".agent/bin/mindforge-tools.cjs" roadmap get-phase "${PHASE}")
-```
-
-If `found` is false: Error and exit.
-
-## Step 2: Check Existing Research
-
-```bash
-ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
-```
-
-If exists: Offer update/view/skip options.
-
-## Step 3: Gather Phase Context
-
-```bash
-INIT=$(node ".agent/bin/mindforge-tools.cjs" init phase-op "${PHASE}")
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-# Extract: phase_dir, padded_phase, phase_number, state_path, requirements_path, context_path
-```
-
-## Step 4: Spawn Researcher
-
-```
-Task(
-  prompt="<objective>
-Research implementation approach for Phase {phase}: {name}
-</objective>
-
-<files_to_read>
-- {context_path} (USER DECISIONS from /mindforge-discuss-phase)
-- {requirements_path} (Project requirements)
-- {state_path} (Project decisions and history)
-</files_to_read>
-
-<additional_context>
-Phase description: {description}
-</additional_context>
-
-<output>
-Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
-</output>",
-  subagent_type="mindforge-phase-researcher",
-  model="{researcher_model}"
-)
-```
-
-## Step 5: Handle Return
-
-- `## RESEARCH COMPLETE` — Display summary, offer: Plan/Dig deeper/Review/Done
-- `## CHECKPOINT REACHED` — Present to user, spawn continuation
-- `## RESEARCH INCONCLUSIVE` — Show attempts, offer: Add context/Try different mode/Manual
-
-</process>

package/.agent/workflows/mindforge-resume-project.md

@@ -1,325 +0,0 @@
-<trigger>
-Use this workflow when:
-- Starting a new session on an existing project
-- User says "continue", "what's next", "where were we", "resume"
-- Any planning operation when .planning/ already exists
-- User returns after time away from project
-</trigger>
-
-<purpose>
-Instantly restore full project context so "Where were we?" has an immediate, complete answer.
-</purpose>
-
-<required_reading>
-@.agent/references/continuation-format.md
-</required_reading>
-
-<process>
-
-<step name="initialize">
-Load all context in one call:
-
-```bash
-INIT=$(node ".agent/bin/mindforge-tools.cjs" init resume)
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Parse JSON for: `state_exists`, `roadmap_exists`, `project_exists`, `planning_exists`, `has_interrupted_agent`, `interrupted_agent_id`, `commit_docs`.
-
-**If `state_exists` is true:** Proceed to load_state
-**If `state_exists` is false but `roadmap_exists` or `project_exists` is true:** Offer to reconstruct STATE.md
-**If `planning_exists` is false:** This is a new project - route to /mindforge-new-project
-</step>
-
-<step name="load_state">
-
-Read and parse STATE.md, then PROJECT.md:
-
-```bash
-cat .planning/STATE.md
-cat .planning/PROJECT.md
-```
-
-**From STATE.md extract:**
-
-- **Project Reference**: Core value and current focus
-- **Current Position**: Phase X of Y, Plan A of B, Status
-- **Progress**: Visual progress bar
-- **Recent Decisions**: Key decisions affecting current work
-- **Pending Todos**: Ideas captured during sessions
-- **Blockers/Concerns**: Issues carried forward
-- **Session Continuity**: Where we left off, any resume files
-
-**From PROJECT.md extract:**
-
-- **What This Is**: Current accurate description
-- **Requirements**: Validated, Active, Out of Scope
-- **Key Decisions**: Full decision log with outcomes
-- **Constraints**: Hard limits on implementation
-
-</step>
-
-<step name="check_incomplete_work">
-Look for incomplete work that needs attention:
-
-```bash
-# Check for structured handoff (preferred — machine-readable)
-cat .planning/HANDOFF.json 2>/dev/null
-
-# Check for continue-here files (mid-plan resumption)
-ls .planning/phases/*/.continue-here*.md 2>/dev/null
-
-# Check for plans without summaries (incomplete execution)
-for plan in .planning/phases/*/*-PLAN.md; do
-  summary="${plan/PLAN/SUMMARY}"
-  [ ! -f "$summary" ] && echo "Incomplete: $plan"
-done 2>/dev/null
-
-# Check for interrupted agents (use has_interrupted_agent and interrupted_agent_id from init)
-if [ "$has_interrupted_agent" = "true" ]; then
-  echo "Interrupted agent: $interrupted_agent_id"
-fi
-```
-
-**If HANDOFF.json exists:**
-
-- This is the primary resumption source — structured data from `/mindforge-pause-work`
-- Parse `status`, `phase`, `plan`, `task`, `total_tasks`, `next_action`
-- Check `blockers` and `human_actions_pending` — surface these immediately
-- Check `completed_tasks` for `in_progress` items — these need attention first
-- Validate `uncommitted_files` against `git status` — flag divergence
-- Use `context_notes` to restore mental model
-- Flag: "Found structured handoff — resuming from task {task}/{total_tasks}"
-- **After successful resumption, delete HANDOFF.json** (it's a one-shot artifact)
-
-**If .continue-here file exists (fallback):**
-
-- This is a mid-plan resumption point
-- Read the file for specific resumption context
-- Flag: "Found mid-plan checkpoint"
-
-**If PLAN without SUMMARY exists:**
-
-- Execution was started but not completed
-- Flag: "Found incomplete plan execution"
-
-**If interrupted agent found:**
-
-- Subagent was spawned but session ended before completion
-- Read agent-history.json for task details
-- Flag: "Found interrupted agent"
-  </step>
-
-<step name="present_status">
-Present complete project status to user:
-
-```
-╔══════════════════════════════════════════════════════════════╗
-║  PROJECT STATUS                                               ║
-╠══════════════════════════════════════════════════════════════╣
-║  Building: [one-liner from PROJECT.md "What This Is"]         ║
-║                                                               ║
-║  Phase: [X] of [Y] - [Phase name]                            ║
-║  Plan:  [A] of [B] - [Status]                                ║
-║  Progress: [██████░░░░] XX%                                  ║
-║                                                               ║
-║  Last activity: [date] - [what happened]                     ║
-╚══════════════════════════════════════════════════════════════╝
-
-[If incomplete work found:]
-⚠️  Incomplete work detected:
-    - [.continue-here file or incomplete plan]
-
-[If interrupted agent found:]
-⚠️  Interrupted agent detected:
-    Agent ID: [id]
-    Task: [task description from agent-history.json]
-    Interrupted: [timestamp]
-
-    Resume with: Task tool (resume parameter with agent ID)
-
-[If pending todos exist:]
-📋 [N] pending todos — /mindforge-check-todos to review
-
-[If blockers exist:]
-⚠️  Carried concerns:
-    - [blocker 1]
-    - [blocker 2]
-
-[If alignment is not ✓:]
-⚠️  Brief alignment: [status] - [assessment]
-```
-
-</step>
-
-<step name="determine_next_action">
-Based on project state, determine the most logical next action:
-
-**If interrupted agent exists:**
-→ Primary: Resume interrupted agent (Task tool with resume parameter)
-→ Option: Start fresh (abandon agent work)
-
-**If HANDOFF.json exists:**
-→ Primary: Resume from structured handoff (highest priority — specific task/blocker context)
-→ Option: Discard handoff and reassess from files
-
-**If .continue-here file exists:**
-→ Fallback: Resume from checkpoint
-→ Option: Start fresh on current plan
-
-**If incomplete plan (PLAN without SUMMARY):**
-→ Primary: Complete the incomplete plan
-→ Option: Abandon and move on
-
-**If phase in progress, all plans complete:**
-→ Primary: Advance to next phase (via internal transition workflow)
-→ Option: Review completed work
-
-**If phase ready to plan:**
-→ Check if CONTEXT.md exists for this phase:
-
-- If CONTEXT.md missing:
-  → Primary: Discuss phase vision (how user imagines it working)
-  → Secondary: Plan directly (skip context gathering)
-- If CONTEXT.md exists:
-  → Primary: Plan the phase
-  → Option: Review roadmap
-
-**If phase ready to execute:**
-→ Primary: Execute next plan
-→ Option: Review the plan first
-</step>
-
-<step name="offer_options">
-Present contextual options based on project state:
-
-```
-What would you like to do?
-
-[Primary action based on state - e.g.:]
-1. Resume interrupted agent [if interrupted agent found]
-   OR
-1. Execute phase (/mindforge-execute-phase {phase} ${MindForge_WS})
-   OR
-1. Discuss Phase 3 context (/mindforge-discuss-phase 3 ${MindForge_WS}) [if CONTEXT.md missing]
-   OR
-1. Plan Phase 3 (/mindforge-plan-phase 3 ${MindForge_WS}) [if CONTEXT.md exists or discuss option declined]
-
-[Secondary options:]
-2. Review current phase status
-3. Check pending todos ([N] pending)
-4. Review brief alignment
-5. Something else
-```
-
-**Note:** When offering phase planning, check for CONTEXT.md existence first:
-
-```bash
-ls .planning/phases/XX-name/*-CONTEXT.md 2>/dev/null
-```
-
-If missing, suggest discuss-phase before plan. If exists, offer plan directly.
-
-Wait for user selection.
-</step>
-
-<step name="route_to_workflow">
-Based on user selection, route to appropriate workflow:
-
-- **Execute plan** → Show command for user to run after clearing:
-  ```
-  ---
-
-  ## ▶ Next Up
-
-  **{phase}-{plan}: [Plan Name]** — [objective from PLAN.md]
-
-  `/mindforge-execute-phase {phase} ${MindForge_WS}`
-
-  <sub>`/clear` first → fresh context window</sub>
-
-  ---
-  ```
-- **Plan phase** → Show command for user to run after clearing:
-  ```
-  ---
-
-  ## ▶ Next Up
-
-  **Phase [N]: [Name]** — [Goal from ROADMAP.md]
-
-  `/mindforge-plan-phase [phase-number] ${MindForge_WS}`
-
-  <sub>`/clear` first → fresh context window</sub>
-
-  ---
-
-  **Also available:**
-  - `/mindforge-discuss-phase [N] ${MindForge_WS}` — gather context first
-  - `/mindforge-research-phase [N] ${MindForge_WS}` — investigate unknowns
-
-  ---
-  ```
-- **Advance to next phase** → ./transition.md (internal workflow, invoked inline — NOT a user command)
-- **Check todos** → Read .planning/todos/pending/, present summary
-- **Review alignment** → Read PROJECT.md, compare to current state
-- **Something else** → Ask what they need
-</step>
-
-<step name="update_session">
-Before proceeding to routed workflow, update session continuity:
-
-Update STATE.md:
-
-```markdown
-## Session Continuity
-
-Last session: [now]
-Stopped at: Session resumed, proceeding to [action]
-Resume file: [updated if applicable]
-```
-
-This ensures if session ends unexpectedly, next resume knows the state.
-</step>
-
-</process>
-
-<reconstruction>
-If STATE.md is missing but other artifacts exist:
-
-"STATE.md missing. Reconstructing 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 decisions, concerns
-4. Count pending todos in .planning/todos/pending/
-5. Check for .continue-here files → Session continuity
-
-Reconstruct and write STATE.md, then proceed normally.
-
-This handles cases where:
-
-- Project predates STATE.md introduction
-- File was accidentally deleted
-- Cloning repo without full .planning/ state
-  </reconstruction>
-
-<quick_resume>
-If user says "continue" or "go":
-- Load state silently
-- Determine primary action
-- Execute immediately without presenting options
-
-"Continuing from [state]... [action]"
-</quick_resume>
-
-<success_criteria>
-Resume is complete when:
-
-- [ ] STATE.md loaded (or reconstructed)
-- [ ] Incomplete work detected and flagged
-- [ ] Clear status presented to user
-- [ ] Contextual next actions offered
-- [ ] User knows exactly where project stands
-- [ ] Session continuity updated
-      </success_criteria>