mindforge-cc 9.0.0 → 10.0.0

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

@@ -1,49 +0,0 @@
----
-name: mindforge-execute-phase
-description: Execute all plans in a phase with wave-based parallelization
----
-
-<objective>
-Execute all plans in a phase using wave-based parallel execution.
-
-Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
-
-Optional wave filter:
-- `--wave N` executes only Wave `N` for pacing, quota management, or staged rollout
-- phase verification/completion still only happens when no incomplete plans remain after the selected wave finishes
-
-Flag handling rule:
-- The optional flags documented below are available behaviors, not implied active behaviors
-- A flag is active only when its literal token appears in `$ARGUMENTS`
-- If a documented flag is absent from `$ARGUMENTS`, treat it as inactive
-
-Context budget: ~15% orchestrator, 100% fresh per subagent.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-execute-phase.md
-@.agent/references/ui-brand.md
-</execution_context>
-
-<context>
-Phase: $ARGUMENTS
-
-**Available optional flags (documentation only — not automatically active):**
-- `--wave N` — Execute only Wave `N` in the phase. Use when you want to pace execution or stay inside usage limits.
-- `--gaps-only` — Execute only gap closure plans (plans with `gap_closure: true` in frontmatter). Use after verify-work creates fix plans.
-- `--interactive` — Execute plans sequentially inline (no subagents) with user checkpoints between tasks. Lower token usage, pair-programming style. Best for small phases, bug fixes, and verification gaps.
-
-**Active flags must be derived from `$ARGUMENTS`:**
-- `--wave N` is active only if the literal `--wave` token is present in `$ARGUMENTS`
-- `--gaps-only` is active only if the literal `--gaps-only` token is present in `$ARGUMENTS`
-- `--interactive` is active only if the literal `--interactive` token is present in `$ARGUMENTS`
-- If none of these tokens appear, run the standard full-phase execution flow with no flag-specific filtering
-- Do not infer that a flag is active just because it is documented in this prompt
-
-Context files are resolved inside the workflow via `mindforge-tools init execute-phase` and per-subagent `<files_to_read>` blocks.
-</context>
-
-<process>
-Execute the execute-phase workflow from @.agent/workflows/mindforge-execute-phase.md end-to-end.
-Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing).
-</process>

package/.agent/skills/mindforge-execute-phase_extended/SKILL.md

@@ -1,70 +0,0 @@
----
-name: mindforge-execute-phase_extended
-description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
----
-
-# Executing Plans
-
-## Overview
-
-Load plan, review critically, execute all tasks, report when complete.
-
-**Announce at start:** "I'm using the mindforge-execute-phase_extended skill to implement this plan."
-
-**Note:** Tell your human partner that mindforge works much better with access to subagents. The quality of its work will be significantly higher if run on a platform with subagent support (such as Claude Code or Codex). If subagents are available, use mindforge:swarm-execution instead of this skill.
-
-## The Process
-
-### Step 1: Load and Review Plan
-1. Read plan file
-2. Review critically - identify any questions or concerns about the plan
-3. If concerns: Raise them with your human partner before starting
-4. If no concerns: Create TodoWrite and proceed
-
-### Step 2: Execute Tasks
-
-For each task:
-1. Mark as in_progress
-2. Follow each step exactly (plan has bite-sized steps)
-3. Run verifications as specified
-4. Mark as completed
-
-### Step 3: Complete Development
-
-After all tasks complete and verified:
-- Announce: "I'm using the mindforge-ship_extended skill to complete this work."
-- **REQUIRED SUB-SKILL:** Use mindforge:ship_extended
-- Follow that skill to verify tests, present options, execute choice
-
-## When to Stop and Ask for Help
-
-**STOP executing immediately when:**
-- Hit a blocker (missing dependency, test fails, instruction unclear)
-- Plan has critical gaps preventing starting
-- You don't understand an instruction
-- Verification fails repeatedly
-
-**Ask for clarification rather than guessing.**
-
-## When to Revisit Earlier Steps
-
-**Return to Review (Step 1) when:**
-- Partner updates the plan based on your feedback
-- Fundamental approach needs rethinking
-
-**Don't force through blockers** - stop and ask.
-
-## Remember
-- Review plan critically first
-- Follow plan steps exactly
-- Don't skip verifications
-- Reference skills when plan says to
-- Stop when blocked, don't guess
-- Never start implementation on main/master branch without explicit user consent
-
-## Integration
-
-**Required workflow skills:**
-- **mindforge:using-git-worktrees** - REQUIRED: Set up isolated workspace before starting
-- **mindforge:plan-phase_extended** - Creates the plan this skill executes
-- **mindforge:ship_extended** - Complete development after all tasks

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

@@ -1,23 +0,0 @@
----
-name: mindforge-fast
-description: Execute a trivial task inline — no subagents, no planning overhead
----
-
-
-<objective>
-Execute a trivial task directly in the current context without spawning subagents
-or generating PLAN.md files. For tasks too small to justify planning overhead:
-typo fixes, config changes, small refactors, forgotten commits, simple additions.
-
-This is NOT a replacement for /mindforge-quick — use /mindforge-quick for anything that
-needs research, multi-step planning, or verification. /mindforge-fast is for tasks
-you could describe in one sentence and execute in under 2 minutes.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-fast.md
-</execution_context>
-
-<process>
-Execute the fast workflow from @.agent/workflows/mindforge-fast.md end-to-end.
-</process>

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

@@ -1,49 +0,0 @@
----
-name: mindforge-forensics
-description: Post-mortem investigation for failed MindForge workflows — analyzes git history, artifacts, and state to diagnose what went wrong
----
-
-
-<objective>
-Investigate what went wrong during a MindForge workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.
-
-Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action.
-Output: Forensic report saved to `.planning/forensics/`, presented inline, with optional issue creation.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-forensics.md
-</execution_context>
-
-<context>
-**Data sources:**
-- `git log` (recent commits, patterns, time gaps)
-- `git status` / `git diff` (uncommitted work, conflicts)
-- `.planning/STATE.md` (current position, session history)
-- `.planning/ROADMAP.md` (phase scope and progress)
-- `.planning/phases/*/` (PLAN.md, SUMMARY.md, VERIFICATION.md, CONTEXT.md)
-- `.planning/reports/SESSION_REPORT.md` (last session outcomes)
-
-**User input:**
-- Problem description: $ARGUMENTS (optional — will ask if not provided)
-</context>
-
-<process>
-Read and execute the forensics workflow from @.agent/workflows/mindforge-forensics.md end-to-end.
-</process>
-
-<success_criteria>
-- Evidence gathered from all available data sources
-- At least 4 anomaly types checked (stuck loop, missing artifacts, abandoned work, crash/interruption)
-- Structured forensic report written to `.planning/forensics/report-{timestamp}.md`
-- Report presented inline with findings, anomalies, and recommendations
-- Interactive investigation offered for deeper analysis
-- GitHub issue creation offered if actionable findings exist
-</success_criteria>
-
-<critical_rules>
-- **Read-only investigation:** Do not modify project source files during forensics. Only write the forensic report and update STATE.md session tracking.
-- **Redact sensitive data:** Strip absolute paths, API keys, tokens from reports and issues.
-- **Ground findings in evidence:** Every anomaly must cite specific commits, files, or state data.
-- **No speculation without evidence:** If data is insufficient, say so — do not fabricate root causes.
-</critical_rules>

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

@@ -1,17 +0,0 @@
----
-name: mindforge-health
-description: Diagnose planning directory health and optionally repair issues
----
-
-<objective>
-Validate `.planning/` directory integrity and report actionable issues. Checks for missing files, invalid configurations, inconsistent state, and orphaned plans.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-health.md
-</execution_context>
-
-<process>
-Execute the health workflow from @.agent/workflows/mindforge-health.md end-to-end.
-Parse --repair flag from arguments and pass to workflow.
-</process>

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

@@ -1,23 +0,0 @@
----
-name: mindforge-help
-description: Show available MindForge commands and usage guide
----
-
-<objective>
-Display the complete MindForge command reference.
-
-Output ONLY the reference content below. Do NOT add:
-- Project-specific analysis
-- Git status or file context
-- Next-step suggestions
-- Any commentary beyond the reference
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-help.md
-</execution_context>
-
-<process>
-Output the complete MindForge command reference from @.agent/workflows/mindforge-help.md.
-Display the reference content directly — no additions or modifications.
-</process>

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

@@ -1,28 +0,0 @@
----
-name: mindforge-insert-phase
-description: Insert urgent work as decimal phase (e.g., 72.1) between existing phases
----
-
-
-<objective>
-Insert a decimal phase for urgent work discovered mid-milestone that must be completed between existing integer phases.
-
-Uses decimal numbering (72.1, 72.2, etc.) to preserve the logical sequence of planned phases while accommodating urgent insertions.
-
-Purpose: Handle urgent work discovered during execution without renumbering entire roadmap.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-insert-phase.md
-</execution_context>
-
-<context>
-Arguments: $ARGUMENTS (format: <after-phase-number> <description>)
-
-Roadmap and state are resolved in-workflow via `init phase-op` and targeted tool calls.
-</context>
-
-<process>
-Execute the insert-phase workflow from @.agent/workflows/mindforge-insert-phase.md end-to-end.
-Preserve all validation gates (argument parsing, phase verification, decimal calculation, roadmap updates).
-</process>

package/.agent/skills/mindforge-join-discord/SKILL.md

@@ -1,19 +0,0 @@
----
-name: mindforge-join-discord
-description: Join the MindForge Discord community
----
-
-
-<objective>
-Display the Discord invite link for the MindForge community server.
-</objective>
-
-<output>
-# Join the MindForge Discord
-
-Connect with other MindForge users, get help, share what you're building, and stay updated.
-
-**Invite link:** https://discord.gg/mindforge
-
-Click the link or paste it into your browser to join.
-</output>

package/.agent/skills/mindforge-list-phase-assumptions/SKILL.md

@@ -1,41 +0,0 @@
----
-name: mindforge-list-phase-assumptions
-description: Surface the agent's assumptions about a phase approach before planning
----
-
-
-<objective>
-Analyze a phase and present the agent's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.
-
-Purpose: Help users see what the agent 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>
-@.agent/workflows/mindforge-list-phase-assumptions.md
-</execution_context>
-
-<context>
-Phase number: $ARGUMENTS (required)
-
-Project state and roadmap are loaded in-workflow using targeted reads.
-</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/.agent/skills/mindforge-list-workspaces/SKILL.md

@@ -1,17 +0,0 @@
----
-name: mindforge-list-workspaces
-description: List active MindForge workspaces and their status
----
-
-<objective>
-Scan `~/mindforge-workspaces/` for workspace directories containing `WORKSPACE.md` manifests. Display a summary table with name, path, repo count, strategy, and MindForge project status.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-list-workspaces.md
-@.agent/references/ui-brand.md
-</execution_context>
-
-<process>
-Execute the list-workspaces workflow from @.agent/workflows/mindforge-list-workspaces.md end-to-end.
-</process>

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

@@ -1,32 +0,0 @@
----
-name: mindforge-manager
-description: Interactive command center for managing multiple phases from one terminal
----
-
-<objective>
-Single-terminal command center for managing a milestone. Shows a dashboard of all phases with visual status indicators, recommends optimal next actions, and dispatches work — discuss runs inline, plan/execute run as background agents.
-
-Designed for power users who want to parallelize work across phases from one terminal: discuss a phase while another plans or executes in the background.
-
-**Creates/Updates:**
-- No files created directly — dispatches to existing MindForge commands via Skill() and background Task agents.
-- Reads `.planning/STATE.md`, `.planning/ROADMAP.md`, phase directories for status.
-
-**After:** User exits when done managing, or all phases complete and milestone lifecycle is suggested.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-manager.md
-@.agent/references/ui-brand.md
-</execution_context>
-
-<context>
-No arguments required. Requires an active milestone with ROADMAP.md and STATE.md.
-
-Project context, phase list, dependencies, and recommendations are resolved inside the workflow using `mindforge-tools.cjs init manager`. No upfront context loading needed.
-</context>
-
-<process>
-Execute the manager workflow from @.agent/workflows/mindforge-manager.md end-to-end.
-Maintain the dashboard refresh loop until the user exits or all phases complete.
-</process>

package/.agent/skills/mindforge-map-codebase/SKILL.md

@@ -1,64 +0,0 @@
----
-name: mindforge-map-codebase
-description: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
----
-
-
-<objective>
-Analyze existing codebase using parallel mindforge-codebase-mapper agents to produce structured codebase documents.
-
-Each mapper agent explores a focus area and **writes documents directly** to `.planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.
-
-Output: .planning/codebase/ folder with 7 structured documents about the codebase state.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-map-codebase.md
-</execution_context>
-
-<context>
-Focus area: $ARGUMENTS (optional - if provided, tells agents to focus on specific subsystem)
-
-**Load project state if exists:**
-Check for .planning/STATE.md - loads context if project already initialized
-
-**This command can run:**
-- Before /mindforge-new-project (brownfield codebases) - creates codebase map first
-- After /mindforge-new-project (greenfield codebases) - updates codebase map as code evolves
-- Anytime to refresh codebase understanding
-</context>
-
-<when_to_use>
-**Use map-codebase for:**
-- Brownfield projects before initialization (understand existing code first)
-- Refreshing codebase map after significant changes
-- Onboarding to an unfamiliar codebase
-- Before major refactoring (understand current state)
-- When STATE.md references outdated codebase info
-
-**Skip map-codebase for:**
-- Greenfield projects with no code yet (nothing to map)
-- Trivial codebases (<5 files)
-</when_to_use>
-
-<process>
-1. Check if .planning/codebase/ already exists (offer to refresh or skip)
-2. Create .planning/codebase/ directory structure
-3. Spawn 4 parallel mindforge-codebase-mapper agents:
-   - Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md
-   - Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md
-   - Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md
-   - Agent 4: concerns focus → writes CONCERNS.md
-4. Wait for agents to complete, collect confirmations (NOT document contents)
-5. Verify all 7 documents exist with line counts
-6. Commit codebase map
-7. Offer next steps (typically: /mindforge-new-project or /mindforge-plan-phase)
-</process>
-
-<success_criteria>
-- [ ] .planning/codebase/ directory created
-- [ ] All 7 codebase documents written by mapper agents
-- [ ] Documents follow template structure
-- [ ] Parallel agents completed without errors
-- [ ] User knows next steps
-</success_criteria>

package/.agent/skills/mindforge-milestone-summary/SKILL.md

@@ -1,44 +0,0 @@
----
-name: mindforge-milestone-summary
-description: Generate a comprehensive project summary from milestone artifacts for team onboarding and review
----
-
-
-<objective>
-Generate a structured milestone summary for team onboarding and project review. Reads completed milestone artifacts (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION files) and produces a human-friendly overview of what was built, how, and why.
-
-Purpose: Enable new team members to understand a completed project by reading one document and asking follow-up questions.
-Output: MILESTONE_SUMMARY written to `.planning/reports/`, presented inline, optional interactive Q&A.
-</objective>
-
-<execution_context>
-@.agent/workflows/mindforge-milestone-summary.md
-</execution_context>
-
-<context>
-**Project files:**
-- `.planning/ROADMAP.md`
-- `.planning/PROJECT.md`
-- `.planning/STATE.md`
-- `.planning/RETROSPECTIVE.md`
-- `.planning/milestones/v{version}-ROADMAP.md` (if archived)
-- `.planning/milestones/v{version}-REQUIREMENTS.md` (if archived)
-- `.planning/phases/*-*/` (SUMMARY.md, VERIFICATION.md, CONTEXT.md, RESEARCH.md)
-
-**User input:**
-- Version: $ARGUMENTS (optional — defaults to current/latest milestone)
-</context>
-
-<process>
-Read and execute the milestone-summary workflow from @.agent/workflows/mindforge-milestone-summary.md end-to-end.
-</process>
-
-<success_criteria>
-- Milestone version resolved (from args, STATE.md, or archive scan)
-- All available artifacts read (ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, VERIFICATION, RESEARCH, RETROSPECTIVE)
-- Summary document written to `.planning/reports/MILESTONE_SUMMARY-v{version}.md`
-- All 7 sections generated (Overview, Architecture, Phases, Decisions, Requirements, Tech Debt, Getting Started)
-- Summary presented inline to user
-- Interactive Q&A offered
-- STATE.md updated
-</success_criteria>

package/.agent/skills/mindforge-neural-orchestrator/SKILL.md

@@ -1,115 +0,0 @@
----
-name: using-mindforge
-description: Use when starting any conversation - establishes how to find and use skills, requiring MindForge Skill tool invocation before ANY response including clarifying questions
----
-
-<SUBAGENT-STOP>
-If you were dispatched as a subagent to execute a specific task, skip this skill.
-</SUBAGENT-STOP>
-
-<EXTREMELY-IMPORTANT>
-If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
-
-IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
-
-This is not negotiable. This is not optional. You cannot rationalize your way out of this.
-</EXTREMELY-IMPORTANT>
-
-## Instruction Priority
-
-mindforge skills override default system prompt behavior, but **user instructions always take precedence**:
-
-1. **User's explicit instructions** (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
-2. **mindforge skills** — override default system behavior where they conflict
-3. **Default system prompt** — lowest priority
-
-If CLAUDE.md, GEMINI.md, or AGENTS.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions. The user is in control.
-
-## How to Access Skills
-
-**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.
-
-**In Gemini CLI:** Skills activate via the `activate_skill` tool. Gemini loads skill metadata at session start and activates the full content on demand.
-
-**In other environments:** Check your platform's documentation for how skills are loaded.
-
-## Platform Adaptation
-
-Skills use Claude Code tool names. Non-CC platforms: see `references/mindforge-tools.md` (Codex) for tool equivalents. Gemini CLI users get the tool mapping loaded automatically via GEMINI.md.
-
-# Using Skills
-
-## The Rule
-
-**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
-
-```dot
-digraph skill_flow {
-    "User message received" [shape=doublecircle];
-    "About to EnterPlanMode?" [shape=doublecircle];
-    "Already brainstormed?" [shape=diamond];
-    "Invoke brainstorming skill" [shape=box];
-    "Might any skill apply?" [shape=diamond];
-    "Invoke MindForge Skill tool" [shape=box];
-    "Announce: 'Using [skill] to [purpose]'" [shape=box];
-    "Has checklist?" [shape=diamond];
-    "Create TodoWrite todo per item" [shape=box];
-    "Follow skill exactly" [shape=box];
-    "Respond (including clarifications)" [shape=doublecircle];
-
-    "About to EnterPlanMode?" -> "Already brainstormed?";
-    "Already brainstormed?" -> "Invoke brainstorming skill" [label="no"];
-    "Already brainstormed?" -> "Might any skill apply?" [label="yes"];
-    "Invoke brainstorming skill" -> "Might any skill apply?";
-
-    "User message received" -> "Might any skill apply?";
-    "Might any skill apply?" -> "Invoke MindForge Skill tool" [label="yes, even 1%"];
-    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
-    "Invoke MindForge Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
-    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
-    "Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
-    "Has checklist?" -> "Follow skill exactly" [label="no"];
-    "Create TodoWrite todo per item" -> "Follow skill exactly";
-}
-```
-
-## Red Flags
-
-These thoughts mean STOP—you're rationalizing:
-
-| Thought | Reality |
-|---------|---------|
-| "This is just a simple question" | Questions are tasks. Check for skills. |
-| "I need more context first" | Skill check comes BEFORE clarifying questions. |
-| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
-| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
-| "Let me gather information first" | Skills tell you HOW to gather information. |
-| "This doesn't need a formal skill" | If a skill exists, use it. |
-| "I remember this skill" | Skills evolve. Read current version. |
-| "This doesn't count as a task" | Action = task. Check for skills. |
-| "The skill is overkill" | Simple things become complex. Use it. |
-| "I'll just do this one thing first" | Check BEFORE doing anything. |
-| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
-| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
-
-## Skill Priority
-
-When multiple skills could apply, use this order:
-
-1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task
-2. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution
-
-"Let's build X" → brainstorming first, then implementation skills.
-"Fix this bug" → debugging first, then domain-specific skills.
-
-## Skill Types
-
-**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.
-
-**Flexible** (patterns): Adapt principles to context.
-
-The skill itself tells you which.
-
-## User Instructions
-
-Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.