mindforge-cc 2.0.0 → 2.1.1

package/.agent/skills/mindforge-review-backlog/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: mindforge-review-backlog
+description: Review and promote backlog items to active milestone
+---
+
+
+<objective>
+Review all 999.x backlog items and optionally promote them into the active
+milestone sequence or remove stale entries.
+</objective>
+
+<process>
+
+1. **List backlog items:**
+   ```bash
+   ls -d .planning/phases/999* 2>/dev/null || echo "No backlog items found"
+   ```
+
+2. **Read ROADMAP.md** and extract all 999.x phase entries:
+   ```bash
+   cat .planning/ROADMAP.md
+   ```
+   Show each backlog item with its description, any accumulated context (CONTEXT.md, RESEARCH.md), and creation date.
+
+3. **Present the list to the user** via AskUserQuestion:
+   - For each backlog item, show: phase number, description, accumulated artifacts
+   - Options per item: **Promote** (move to active), **Keep** (leave in backlog), **Remove** (delete)
+
+4. **For items to PROMOTE:**
+   - Find the next sequential phase number in the active milestone
+   - Rename the directory from `999.x-slug` to `{new_num}-slug`:
+     ```bash
+     NEW_NUM=$(node ".agent/bin/mindforge-tools.cjs" phase add "${DESCRIPTION}" --raw)
+     ```
+   - Move accumulated artifacts to the new phase directory
+   - Update ROADMAP.md: move the entry from `## Backlog` section to the active phase list
+   - Remove `(BACKLOG)` marker
+   - Add appropriate `**Depends on:**` field
+
+5. **For items to REMOVE:**
+   - Delete the phase directory
+   - Remove the entry from ROADMAP.md `## Backlog` section
+
+6. **Commit changes:**
+   ```bash
+   node ".agent/bin/mindforge-tools.cjs" commit "docs: review backlog — promoted N, removed M" --files .planning/ROADMAP.md
+   ```
+
+7. **Report summary:**
+   ```
+   ## 📋 Backlog Review Complete
+
+   Promoted: {list of promoted items with new phase numbers}
+   Kept: {list of items remaining in backlog}
+   Removed: {list of deleted items}
+   ```
+
+</process>

package/.agent/skills/mindforge-session-report/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: mindforge-session-report
+description: Generate a session report with token usage estimates, work summary, and outcomes
+---
+
+<objective>
+Generate a structured SESSION_REPORT.md document capturing session outcomes, work performed, and estimated resource usage. Provides a shareable artifact for post-session review.
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-session-report.md
+</execution_context>
+
+<process>
+Execute the session-report workflow from @.agent/workflows/mindforge-session-report.md end-to-end.
+</process>

package/.agent/skills/mindforge-set-profile/SKILL.md

@@ -0,0 +1,9 @@
+---
+name: mindforge-set-profile
+description: Switch model profile for MindForge agents (quality/balanced/budget/inherit)
+---
+
+
+Show the following output to the user verbatim, with no extra commentary:
+
+!`node ".agent/bin/mindforge-tools.cjs" config-set-model-profile $ARGUMENTS --raw`

package/.agent/skills/mindforge-settings/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: mindforge-settings
+description: Configure MindForge workflow toggles and model profile
+---
+
+
+<objective>
+Interactive configuration of MindForge workflow agents and model profile via multi-question prompt.
+
+Routes to the settings workflow which handles:
+- Config existence ensuring
+- Current settings reading and parsing
+- Interactive 5-question prompt (model, research, plan_check, verifier, branching)
+- Config merging and writing
+- Confirmation display with quick command references
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-settings.md
+</execution_context>
+
+<process>
+**Follow the settings workflow** from `@.agent/workflows/mindforge-settings.md`.
+
+The workflow handles all logic including:
+1. Config file creation with defaults if missing
+2. Current config reading
+3. Interactive settings presentation with pre-selection
+4. Answer parsing and config merging
+5. File writing
+6. Confirmation display
+</process>

package/.agent/skills/mindforge-ship/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: mindforge-ship
+description: Create PR, run review, and prepare for merge after verification passes
+---
+
+<objective>
+Bridge local completion → merged PR. After /mindforge-verify-work passes, ship the work: push branch, create PR with auto-generated body, optionally trigger review, and track the merge.
+
+Closes the plan → execute → verify → ship loop.
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-ship.md
+</execution_context>
+
+Execute the ship workflow from @.agent/workflows/mindforge-ship.md end-to-end.

package/.agent/skills/mindforge-stats/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: mindforge-stats
+description: Display project statistics — phases, plans, requirements, git metrics, and timeline
+---
+
+<objective>
+Display comprehensive project statistics including phase progress, plan execution metrics, requirements completion, git history stats, and project timeline.
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-stats.md
+</execution_context>
+
+<process>
+Execute the stats workflow from @.agent/workflows/mindforge-stats.md end-to-end.
+</process>

package/.agent/skills/mindforge-thread/SKILL.md

@@ -0,0 +1,123 @@
+---
+name: mindforge-thread
+description: Manage persistent context threads for cross-session work
+---
+
+
+<objective>
+Create, list, or resume persistent context threads. Threads are lightweight
+cross-session knowledge stores for work that spans multiple sessions but
+doesn't belong to any specific phase.
+</objective>
+
+<process>
+
+**Parse $ARGUMENTS to determine mode:**
+
+<mode_list>
+**If no arguments or $ARGUMENTS is empty:**
+
+List all threads:
+```bash
+ls .planning/threads/*.md 2>/dev/null
+```
+
+For each thread, read the first few lines to show title and status:
+```
+## Active Threads
+
+| Thread | Status | Last Updated |
+|--------|--------|-------------|
+| fix-deploy-key-auth | OPEN | 2026-03-15 |
+| pasta-tcp-timeout | RESOLVED | 2026-03-12 |
+| perf-investigation | IN PROGRESS | 2026-03-17 |
+```
+
+If no threads exist, show:
+```
+No threads found. Create one with: /mindforge-thread <description>
+```
+</mode_list>
+
+<mode_resume>
+**If $ARGUMENTS matches an existing thread name (file exists):**
+
+Resume the thread — load its context into the current session:
+```bash
+cat ".planning/threads/${THREAD_NAME}.md"
+```
+
+Display the thread content and ask what the user wants to work on next.
+Update the thread's status to `IN PROGRESS` if it was `OPEN`.
+</mode_resume>
+
+<mode_create>
+**If $ARGUMENTS is a new description (no matching thread file):**
+
+Create a new thread:
+
+1. Generate slug from description:
+   ```bash
+   SLUG=$(node ".agent/bin/mindforge-tools.cjs" generate-slug "$ARGUMENTS")
+   ```
+
+2. Create the threads directory if needed:
+   ```bash
+   mkdir -p .planning/threads
+   ```
+
+3. Write the thread file:
+   ```bash
+   cat > ".planning/threads/${SLUG}.md" << 'EOF'
+   # Thread: {description}
+
+   ## Status: OPEN
+
+   ## Goal
+
+   {description}
+
+   ## Context
+
+   *Created from conversation on {today's date}.*
+
+   ## References
+
+   - *(add links, file paths, or issue numbers)*
+
+   ## Next Steps
+
+   - *(what the next session should do first)*
+   EOF
+   ```
+
+4. If there's relevant context in the current conversation (code snippets,
+   error messages, investigation results), extract and add it to the Context
+   section.
+
+5. Commit:
+   ```bash
+   node ".agent/bin/mindforge-tools.cjs" commit "docs: create thread — ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"
+   ```
+
+6. Report:
+   ```
+   ## 🧵 Thread Created
+
+   Thread: {slug}
+   File: .planning/threads/{slug}.md
+
+   Resume anytime with: /mindforge-thread {slug}
+   ```
+</mode_create>
+
+</process>
+
+<notes>
+- Threads are NOT phase-scoped — they exist independently of the roadmap
+- Lighter weight than /mindforge-pause-work — no phase state, no plan context
+- The value is in Context and Next Steps — a cold-start session can pick up immediately
+- Threads can be promoted to phases or backlog items when they mature:
+  /mindforge-add-phase or /mindforge-add-backlog with context from the thread
+- Thread files live in .planning/threads/ — no collision with phases or other MindForge structures
+</notes>

package/.agent/skills/mindforge-ui-phase/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: mindforge-ui-phase
+description: Generate UI design contract (UI-SPEC.md) for frontend phases
+---
+
+<objective>
+Create a UI design contract (UI-SPEC.md) for a frontend phase.
+Orchestrates mindforge-ui-researcher and mindforge-ui-checker.
+Flow: Validate → Research UI → Verify UI-SPEC → Done
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-ui-phase.md
+@.agent/references/ui-brand.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS — optional, auto-detects next unplanned phase if omitted.
+</context>
+
+<process>
+Execute @.agent/workflows/mindforge-ui-phase.md end-to-end.
+Preserve all workflow gates.
+</process>

package/.agent/skills/mindforge-ui-review/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: mindforge-ui-review
+description: Retroactive 6-pillar visual audit of implemented frontend code
+---
+
+<objective>
+Conduct a retroactive 6-pillar visual audit. Produces UI-REVIEW.md with
+graded assessment (1-4 per pillar). Works on any project.
+Output: {phase_num}-UI-REVIEW.md
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-ui-review.md
+@.agent/references/ui-brand.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS — optional, defaults to last completed phase.
+</context>
+
+<process>
+Execute @.agent/workflows/mindforge-ui-review.md end-to-end.
+Preserve all workflow gates.
+</process>

package/.agent/skills/mindforge-update/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: mindforge-update
+description: Update MindForge to latest version with changelog display
+---
+
+
+<objective>
+Check for MindForge updates, install if available, and display what changed.
+
+Routes to the update workflow which handles:
+- Version detection (local vs global installation)
+- npm version checking
+- Changelog fetching and display
+- User confirmation with clean install warning
+- Update execution and cache clearing
+- Restart reminder
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-update.md
+</execution_context>
+
+<process>
+**Follow the update workflow** from `@.agent/workflows/mindforge-update.md`.
+
+The workflow handles all logic including:
+1. Installed version detection (local/global)
+2. Latest version checking via npm
+3. Version comparison
+4. Changelog fetching and extraction
+5. Clean install warning display
+6. User confirmation
+7. Update execution
+8. Cache clearing
+</process>

package/.agent/skills/mindforge-validate-phase/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: mindforge-validate-phase
+description: Retroactively audit and fill Nyquist validation gaps for a completed phase
+---
+
+<objective>
+Audit Nyquist validation coverage for a completed phase. Three states:
+- (A) VALIDATION.md exists — audit and fill gaps
+- (B) No VALIDATION.md, SUMMARY.md exists — reconstruct from artifacts
+- (C) Phase not executed — exit with guidance
+
+Output: updated VALIDATION.md + generated test files.
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-validate-phase.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS — optional, defaults to last completed phase.
+</context>
+
+<process>
+Execute @.agent/workflows/mindforge-validate-phase.md.
+Preserve all workflow gates.
+</process>

package/.agent/skills/mindforge-verify-work/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: mindforge-verify-work
+description: Validate built features through conversational UAT
+---
+
+<objective>
+Validate built features through conversational testing with persistent state.
+
+Purpose: Confirm what the agent built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.
+
+Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for /mindforge-execute-phase
+</objective>
+
+<execution_context>
+@.agent/workflows/mindforge-verify-work.md
+@.agent/templates/UAT.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS (optional)
+- If provided: Test specific phase (e.g., "4")
+- If not provided: Check for active sessions or prompt for phase
+
+Context files are resolved inside the workflow (`init verify-work`) and delegated via `<files_to_read>` blocks.
+</context>
+
+<process>
+Execute the verify-work workflow from @.agent/workflows/mindforge-verify-work.md end-to-end.
+Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).
+</process>

package/.agent/skills/mindforge-workstreams/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: mindforge-workstreams
+description: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
+---
+
+
+# /mindforge-workstreams
+
+Manage parallel workstreams for concurrent milestone work.
+
+## Usage
+
+`/mindforge-workstreams [subcommand] [args]`
+
+### Subcommands
+
+| Command | Description |
+|---------|-------------|
+| `list` | List all workstreams with status |
+| `create <name>` | Create a new workstream |
+| `status <name>` | Detailed status for one workstream |
+| `switch <name>` | Set active workstream |
+| `progress` | Progress summary across all workstreams |
+| `complete <name>` | Archive a completed workstream |
+| `resume <name>` | Resume work in a workstream |
+
+## Step 1: Parse Subcommand
+
+Parse the user's input to determine which workstream operation to perform.
+If no subcommand given, default to `list`.
+
+## Step 2: Execute Operation
+
+### list
+Run: `node "$MindForge_TOOLS" workstream list --raw --cwd "$CWD"`
+Display the workstreams in a table format showing name, status, current phase, and progress.
+
+### create
+Run: `node "$MindForge_TOOLS" workstream create <name> --raw --cwd "$CWD"`
+After creation, display the new workstream path and suggest next steps:
+- `/mindforge-new-milestone --ws <name>` to set up the milestone
+
+### status
+Run: `node "$MindForge_TOOLS" workstream status <name> --raw --cwd "$CWD"`
+Display detailed phase breakdown and state information.
+
+### switch
+Run: `node "$MindForge_TOOLS" workstream set <name> --raw --cwd "$CWD"`
+Also set `MindForge_WORKSTREAM` env var for the current session.
+
+### progress
+Run: `node "$MindForge_TOOLS" workstream progress --raw --cwd "$CWD"`
+Display a progress overview across all workstreams.
+
+### complete
+Run: `node "$MindForge_TOOLS" workstream complete <name> --raw --cwd "$CWD"`
+Archive the workstream to milestones/.
+
+### resume
+Set the workstream as active and suggest `/mindforge-resume-work --ws <name>`.
+
+## Step 3: Display Results
+
+Format the JSON output from mindforge-tools into a human-readable display.
+Include the `${MindForge_WS}` flag in any routing suggestions.

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

@@ -0,0 +1,112 @@
+<purpose>
+Add a new integer phase to the end of the current milestone in the roadmap. Automatically calculates next phase number, creates phase directory, and updates roadmap structure.
+</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:
+- All arguments become the phase description
+- Example: `/mindforge-add-phase Add authentication` → description = "Add authentication"
+- Example: `/mindforge-add-phase Fix critical performance issues` → description = "Fix critical performance issues"
+
+If no arguments provided:
+
+```
+ERROR: Phase description required
+Usage: /mindforge-add-phase <description>
+Example: /mindforge-add-phase Add authentication system
+```
+
+Exit.
+</step>
+
+<step name="init_context">
+Load phase operation context:
+
+```bash
+INIT=$(node ".agent/bin/mindforge-tools.cjs" init phase-op "0")
+if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
+```
+
+Check `roadmap_exists` from init JSON. If false:
+```
+ERROR: No roadmap found (.planning/ROADMAP.md)
+Run /mindforge-new-project to initialize.
+```
+Exit.
+</step>
+
+<step name="add_phase">
+**Delegate the phase addition to mindforge-tools:**
+
+```bash
+RESULT=$(node ".agent/bin/mindforge-tools.cjs" phase add "${description}")
+```
+
+The CLI handles:
+- Finding the highest existing integer phase number
+- Calculating next phase number (max + 1)
+- Generating slug from description
+- Creating the phase directory (`.planning/phases/{NN}-{slug}/`)
+- Inserting the phase entry into ROADMAP.md with Goal, Depends on, and Plans sections
+
+Extract from result: `phase_number`, `padded`, `name`, `slug`, `directory`.
+</step>
+
+<step name="update_project_state">
+Update STATE.md to reflect the new phase:
+
+1. Read `.planning/STATE.md`
+2. Under "## Accumulated Context" → "### Roadmap Evolution" add entry:
+   ```
+   - Phase {N} added: {description}
+   ```
+
+If "Roadmap Evolution" section doesn't exist, create it.
+</step>
+
+<step name="completion">
+Present completion summary:
+
+```
+Phase {N} added to current milestone:
+- Description: {description}
+- Directory: .planning/phases/{phase-num}-{slug}/
+- Status: Not planned yet
+
+Roadmap updated: .planning/ROADMAP.md
+
+---
+
+## ▶ Next Up
+
+**Phase {N}: {description}**
+
+`/mindforge-plan-phase {N}`
+
+<sub>`/clear` first → fresh context window</sub>
+
+---
+
+**Also available:**
+- `/mindforge-add-phase <description>` — add another phase
+- Review roadmap
+
+---
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] `mindforge-tools phase add` executed successfully
+- [ ] Phase directory created
+- [ ] Roadmap updated with new phase entry
+- [ ] STATE.md updated with roadmap evolution note
+- [ ] User informed of next steps
+</success_criteria>