mindforge-cc 9.0.0 → 10.0.0

package/.agent/workflows/mindforge-check-todos.md

@@ -1,177 +0,0 @@
-<purpose>
-List all pending todos, allow selection, load full context for the selected todo, and route to appropriate action.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="init_context">
-Load todo context:
-
-```bash
-INIT=$(node ".agent/bin/mindforge-tools.cjs" init todos)
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Extract from init JSON: `todo_count`, `todos`, `pending_dir`.
-
-If `todo_count` is 0:
-```
-No pending todos.
-
-Todos are captured during work sessions with /mindforge-add-todo.
-
----
-
-Would you like to:
-
-1. Continue with current phase (/mindforge-progress)
-2. Add a todo now (/mindforge-add-todo)
-```
-
-Exit.
-</step>
-
-<step name="parse_filter">
-Check for area filter in arguments:
-- `/mindforge-check-todos` → show all
-- `/mindforge-check-todos api` → filter to area:api only
-</step>
-
-<step name="list_todos">
-Use the `todos` array from init context (already filtered by area if specified).
-
-Parse and display as numbered list:
-
-```
-Pending Todos:
-
-1. Add auth token refresh (api, 2d ago)
-2. Fix modal z-index issue (ui, 1d ago)
-3. Refactor database connection pool (database, 5h ago)
-
----
-
-Reply with a number to view details, or:
-- `/mindforge-check-todos [area]` to filter by area
-- `q` to exit
-```
-
-Format age as relative time from created timestamp.
-</step>
-
-<step name="handle_selection">
-Wait for user to reply with a number.
-
-If valid: load selected todo, proceed.
-If invalid: "Invalid selection. Reply with a number (1-[N]) or `q` to exit."
-</step>
-
-<step name="load_context">
-Read the todo file completely. Display:
-
-```
-## [title]
-
-**Area:** [area]
-**Created:** [date] ([relative time] ago)
-**Files:** [list or "None"]
-
-### Problem
-[problem section content]
-
-### Solution
-[solution section content]
-```
-
-If `files` field has entries, read and briefly summarize each.
-</step>
-
-<step name="check_roadmap">
-Check for roadmap (can use init progress or directly check file existence):
-
-If `.planning/ROADMAP.md` exists:
-1. Check if todo's area matches an upcoming phase
-2. Check if todo's files overlap with a phase's scope
-3. Note any match for action options
-</step>
-
-<step name="offer_actions">
-**If todo maps to a roadmap phase:**
-
-Use AskUserQuestion:
-- header: "Action"
-- question: "This todo relates to Phase [N]: [name]. What would you like to do?"
-- options:
-  - "Work on it now" — move to done, start working
-  - "Add to phase plan" — include when planning Phase [N]
-  - "Brainstorm approach" — think through before deciding
-  - "Put it back" — return to list
-
-**If no roadmap match:**
-
-Use AskUserQuestion:
-- header: "Action"
-- question: "What would you like to do with this todo?"
-- options:
-  - "Work on it now" — move to done, start working
-  - "Create a phase" — /mindforge-add-phase with this scope
-  - "Brainstorm approach" — think through before deciding
-  - "Put it back" — return to list
-</step>
-
-<step name="execute_action">
-**Work on it now:**
-```bash
-mv ".planning/todos/pending/[filename]" ".planning/todos/done/"
-```
-Update STATE.md todo count. Present problem/solution context. Begin work or ask how to proceed.
-
-**Add to phase plan:**
-Note todo reference in phase planning notes. Keep in pending. Return to list or exit.
-
-**Create a phase:**
-Display: `/mindforge-add-phase [description from todo]`
-Keep in pending. User runs command in fresh context.
-
-**Brainstorm approach:**
-Keep in pending. Start discussion about problem and approaches.
-
-**Put it back:**
-Return to list_todos step.
-</step>
-
-<step name="update_state">
-After any action that changes todo count:
-
-Re-run `init todos` to get updated count, then update STATE.md "### Pending Todos" section if exists.
-</step>
-
-<step name="git_commit">
-If todo was moved to done/, commit the change:
-
-```bash
-git rm --cached .planning/todos/pending/[filename] 2>/dev/null || true
-node ".agent/bin/mindforge-tools.cjs" commit "docs: start work on todo - [title]" --files .planning/todos/done/[filename] .planning/STATE.md
-```
-
-Tool respects `commit_docs` config and gitignore automatically.
-
-Confirm: "Committed: docs: start work on todo - [title]"
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] All pending todos listed with title, area, age
-- [ ] Area filter applied if specified
-- [ ] Selected todo's full context loaded
-- [ ] Roadmap context checked for phase match
-- [ ] Appropriate actions offered
-- [ ] Selected action executed
-- [ ] STATE.md updated if todo count changed
-- [ ] Changes committed to git (if todo moved to done/)
-</success_criteria>

package/.agent/workflows/mindforge-cleanup.md

@@ -1,152 +0,0 @@
-<purpose>
-
-Archive accumulated phase directories from completed milestones into `.planning/milestones/v{X.Y}-phases/`. Identifies which phases belong to each completed milestone, shows a dry-run summary, and moves directories on confirmation.
-
-</purpose>
-
-<required_reading>
-
-1. `.planning/MILESTONES.md`
-2. `.planning/milestones/` directory listing
-3. `.planning/phases/` directory listing
-
-</required_reading>
-
-<process>
-
-<step name="identify_completed_milestones">
-
-Read `.planning/MILESTONES.md` to identify completed milestones and their versions.
-
-```bash
-cat .planning/MILESTONES.md
-```
-
-Extract each milestone version (e.g., v1.0, v1.1, v2.0).
-
-Check which milestone archive dirs already exist:
-
-```bash
-ls -d .planning/milestones/v*-phases 2>/dev/null
-```
-
-Filter to milestones that do NOT already have a `-phases` archive directory.
-
-If all milestones already have phase archives:
-
-```
-All completed milestones already have phase directories archived. Nothing to clean up.
-```
-
-Stop here.
-
-</step>
-
-<step name="determine_phase_membership">
-
-For each completed milestone without a `-phases` archive, read the archived ROADMAP snapshot to determine which phases belong to it:
-
-```bash
-cat .planning/milestones/v{X.Y}-ROADMAP.md
-```
-
-Extract phase numbers and names from the archived roadmap (e.g., Phase 1: Foundation, Phase 2: Auth).
-
-Check which of those phase directories still exist in `.planning/phases/`:
-
-```bash
-ls -d .planning/phases/*/ 2>/dev/null
-```
-
-Match phase directories to milestone membership. Only include directories that still exist in `.planning/phases/`.
-
-</step>
-
-<step name="show_dry_run">
-
-Present a dry-run summary for each milestone:
-
-```
-## Cleanup Summary
-
-### v{X.Y} — {Milestone Name}
-These phase directories will be archived:
-- 01-foundation/
-- 02-auth/
-- 03-core-features/
-
-Destination: .planning/milestones/v{X.Y}-phases/
-
-### v{X.Z} — {Milestone Name}
-These phase directories will be archived:
-- 04-security/
-- 05-hardening/
-
-Destination: .planning/milestones/v{X.Z}-phases/
-```
-
-If no phase directories remain to archive (all already moved or deleted):
-
-```
-No phase directories found to archive. Phases may have been removed or archived previously.
-```
-
-Stop here.
-
-AskUserQuestion: "Proceed with archiving?" with options: "Yes — archive listed phases" | "Cancel"
-
-If "Cancel": Stop.
-
-</step>
-
-<step name="archive_phases">
-
-For each milestone, move phase directories:
-
-```bash
-mkdir -p .planning/milestones/v{X.Y}-phases
-```
-
-For each phase directory belonging to this milestone:
-
-```bash
-mv .planning/phases/{dir} .planning/milestones/v{X.Y}-phases/
-```
-
-Repeat for all milestones in the cleanup set.
-
-</step>
-
-<step name="commit">
-
-Commit the changes:
-
-```bash
-node ".agent/bin/mindforge-tools.cjs" commit "chore: archive phase directories from completed milestones" --files .planning/milestones/ .planning/phases/
-```
-
-</step>
-
-<step name="report">
-
-```
-Archived:
-{For each milestone}
-- v{X.Y}: {N} phase directories → .planning/milestones/v{X.Y}-phases/
-
-.planning/phases/ cleaned up.
-```
-
-</step>
-
-</process>
-
-<success_criteria>
-
-- [ ] All completed milestones without existing phase archives identified
-- [ ] Phase membership determined from archived ROADMAP snapshots
-- [ ] Dry-run summary shown and user confirmed
-- [ ] Phase directories moved to `.planning/milestones/v{X.Y}-phases/`
-- [ ] Changes committed
-
-</success_criteria>