mindforge-cc 2.1.4 → 2.3.0

package/.agent/CLAUDE.md

@@ -569,3 +569,17 @@ After every phase that passes all gates:
 - /mindforge:marketplace — discover and install community skills
 
 ---
+
+
+## 🧠 Knowledge Context (Auto-loaded)
+🧠 Knowledge Base — 5 relevant memories loaded:
+  Preferences  : 1
+  Code patterns: 1
+  Domain       : 3
+### Team Preferences
+- [90% confidence] Use Tailwind: Always use Tailwind for CSS.
+
+### Domain Knowledge
+- Auth with JWT: Secure JWT with httpOnly cookies.
+- Global Tip: Always fix lints.
+- Database SQL: Use indexed columns for fast queries.

package/.agent/forge/help.md

@@ -1,3 +1,7 @@
+---
+description: Show all available FORGE commands and what they do.
+---
+
 Show all available FORGE commands and what they do.
 
 List every .md file in .claude/commands/forge/ and display:

package/.agent/forge/init-project.md

@@ -1,3 +1,7 @@
+---
+description: Initialize a new project under the FORGE framework.
+---
+
 Initialize a new project under the FORGE framework.
 
 Follow these steps in order:

package/.agent/forge/plan-phase.md

@@ -1,3 +1,7 @@
+---
+description: Plan a phase of the project. Usage: /forge:plan-phase [N]
+---
+
 Plan a phase of the project. Usage: /forge:plan-phase [N]
 
 If N is not provided, check STATE.md for the current phase and use that.

package/.agent/mindforge/approve.md

@@ -1,3 +1,7 @@
+---
+description: Process pending approvals and emergency overrides. Usage:
+---
+
 Process pending approvals and emergency overrides. Usage:
 `/mindforge:approve [approval-id] [--approve|--reject] [--reason "..."] [--emergency]`
 

package/.agent/mindforge/audit.md

@@ -1,3 +1,7 @@
+---
+description: Query .planning/AUDIT.jsonl by phase, event, date, severity, integration, or
+---
+
 Query `.planning/AUDIT.jsonl` by phase, event, date, severity, integration, or
  agent. Usage: `/mindforge:audit [filters]`
 

package/.agent/mindforge/auto.md

@@ -1,3 +1,7 @@
+---
+description: Starts the MindForge Autonomous Execution Engine for the
+---
+
 # /mindforge:auto [Phase N]
 
 **Purpose**: Starts the MindForge Autonomous Execution Engine for the

package/.agent/mindforge/benchmark.md

@@ -1,3 +1,7 @@
+---
+description: Measure skill effectiveness over time.
+---
+
 # MindForge — Benchmark Command
 # Usage: /mindforge:benchmark [--skill skill-name] [--compare skill-a skill-b]
 

package/.agent/mindforge/browse.md

@@ -1,3 +1,7 @@
+---
+description: @mindforge browse <url | action>
+---
+
 # /mindforge:browse
 
 ## Usage

package/.agent/mindforge/complete-milestone.md

@@ -1,3 +1,7 @@
+---
+description: Archive a completed milestone, generate a release report, and prepare the next
+---
+
 Archive a completed milestone, generate a release report, and prepare the next
  milestone. Usage: `/mindforge:complete-milestone <name> <version>`
 

package/.agent/mindforge/costs.md

@@ -1,3 +1,7 @@
+---
+description: Real-time cost tracking for all AI model usage.
+---
+
 # MindForge v2 — Costs Command
 # Usage: /mindforge:costs [--phase N] [--session ID] [--window 7d]
 

package/.agent/mindforge/cross-review.md

@@ -1,3 +1,7 @@
+---
+description: Get the same code diff reviewed by multiple AI models simultaneously.
+---
+
 # MindForge v2 — Cross-Review Command
 # Usage: /mindforge:cross-review [--phase N] [--models list] [--focus area]
 

package/.agent/mindforge/dashboard.md

@@ -1,3 +1,7 @@
+---
+description: Start the MindForge real-time web dashboard — a live observability UI for the
+---
+
 # MindForge v2 — Dashboard Command
 # Usage: /mindforge:dashboard [--port 7339] [--open] [--stop] [--status]
 # Version: v2.0.0-alpha.5

package/.agent/mindforge/debug.md

@@ -1,3 +1,7 @@
+---
+description: Systematic debugging using the Debug Specialist persona with full RCA protocol.
+---
+
 # MindForge — Debug Command
 # Usage: /mindforge:debug [description]
 

package/.agent/mindforge/discuss-phase.md

@@ -1,3 +1,7 @@
+---
+description: Planning without discussion produces generic plans.
+---
+
 # MindForge — Discuss Phase Command
 # Usage: /mindforge:discuss-phase [N] [--batch] [--auto]
 # Captures implementation decisions before planning begins.

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

@@ -1,3 +1,7 @@
+---
+description: 1. Read STATE.md — confirm phase [N] is in "planned" status.
+---
+
 # MindForge — Execute Phase Command
 # Usage: /mindforge:execute-phase [N]
 

package/.agent/mindforge/health.md

@@ -1,3 +1,7 @@
+---
+description: Run all seven health-engine categories from .mindforge/intelligence/health-engine.md.
+---
+
 # MindForge — Health Command
 # Usage: /mindforge:health [--repair] [--category C] [--verbose]
 

package/.agent/mindforge/help.md

@@ -1,3 +1,7 @@
+---
+description: Show all available MindForge commands.
+---
+
 Show all available MindForge commands.
 
 ## Pre-check

package/.agent/mindforge/init-org.md

@@ -1,3 +1,7 @@
+---
+description: Set up MindForge at the organisation level — create standardised org-level
+---
+
 # MindForge — Init Org Command
 # Usage: /mindforge:init-org [--org-name "Name"] [--update]
 

package/.agent/mindforge/init-project.md

@@ -1,3 +1,7 @@
+---
+description: Initialise a new project under the MindForge framework.
+---
+
 Initialise a new project under the MindForge framework.
 
 ## Pre-check

package/.agent/mindforge/install-skill.md

@@ -1,3 +1,7 @@
+---
+description: Follow the full installation protocol from .mindforge/distribution/registry-client.md.
+---
+
 Follow the full installation protocol from `.mindforge/distribution/registry-client.md`.
 
 Steps:

package/.agent/mindforge/learn.md

@@ -1,3 +1,7 @@
+---
+description: Convert any knowledge source into a reusable, validated, committed MindForge SKILL.md.
+---
+
 # MindForge v2 — Learn Command
 # Usage: /mindforge:learn [url|path|--session|npm:package] [--name skill-name] [--tier project|org|core]
 # Version: v2.0.0-alpha.6

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

@@ -1,3 +1,7 @@
+---
+description: - Joining an existing project that has no MindForge context files
+---
+
 # MindForge — Map Codebase Command
 # Usage: /mindforge:map-codebase [area]
 # Onboards MindForge to an existing (brownfield) codebase.

package/.agent/mindforge/marketplace.md

@@ -1,3 +1,7 @@
+---
+description: Discover, evaluate, and install community-published MindForge skills from the
+---
+
 # MindForge v2 — Marketplace Command
 # Usage: /mindforge:marketplace [search|featured|trending|install|publish]
 # Version: v2.0.0-alpha.6

package/.agent/mindforge/metrics.md

@@ -1,3 +1,7 @@
+---
+description: Display session and phase quality trends with early warning signals.
+---
+
 # MindForge — Metrics Command
 # Usage: /mindforge:metrics [--phase N] [--window short|medium|long] [--export path]
 

package/.agent/mindforge/migrate.md

@@ -1,3 +1,7 @@
+---
+description: Run explicit schema migrations for .planning/ files.
+---
+
 # MindForge — Migrate Command
 # Usage: /mindforge:migrate [--from X.Y.Z] [--to X.Y.Z] [--dry-run] [--force]
 

package/.agent/mindforge/milestone.md

@@ -1,3 +1,7 @@
+---
+description: Create or update a milestone definition in .planning/milestones/ and track the
+---
+
 Create or update a milestone definition in `.planning/milestones/` and track the
  health of grouped phases. Usage: `/mindforge:milestone <name> [phase list]`
 

package/.agent/mindforge/new-runtime.md

@@ -1,3 +1,7 @@
+---
+description: Scaffold support for a new AI coding runtime.
+---
+
 # /mindforge:new-runtime
 
 Scaffold support for a new AI coding runtime.

package/.agent/mindforge/next.md

@@ -1,3 +1,7 @@
+---
+description: Auto-detect the current project state and execute the appropriate next step.
+---
+
 # MindForge — Next Command
 # Usage: /mindforge:next
 

package/.agent/mindforge/plan-phase.md

@@ -1,3 +1,7 @@
+---
+description: Plan a project phase. Usage: /mindforge:plan-phase [N]
+---
+
 Plan a project phase. Usage: /mindforge:plan-phase [N]
 
 ## Pre-check

package/.agent/mindforge/plugins.md

@@ -1,3 +1,7 @@
+---
+description: Read PLUGINS-MANIFEST.md. Display installed plugins with version and permissions.
+---
+
 # MindForge — Plugins Command
 # Usage: /mindforge:plugins [list|install|uninstall|info|validate|create] [name]
 

package/.agent/mindforge/pr-review.md

@@ -1,3 +1,7 @@
+---
+description: Run the AI PR review engine on a pull request diff.
+---
+
 # MindForge — PR Review Command
 # Usage: /mindforge:pr-review [--diff path] [--sha base..head] [--output github|json|markdown]
 

package/.agent/mindforge/profile-team.md

@@ -1,3 +1,7 @@
+---
+description: Generate and maintain team/developer profiles for response personalization.
+---
+
 # MindForge — Profile Team Command
 # Usage: /mindforge:profile-team [--refresh] [--developer email] [--questionnaire]
 

package/.agent/mindforge/publish-skill.md

@@ -1,3 +1,7 @@
+---
+description: Publish a skill to the npm registry (or private registry).
+---
+
 # MindForge — Publish Skill Command
 # Usage: /mindforge:publish-skill [skill-dir] [--registry URL] [--dry-run]
 

package/.agent/mindforge/qa.md

@@ -1,3 +1,7 @@
+---
+description: @mindforge qa [--phase N] [--auto]
+---
+
 # /mindforge:qa
 
 ## Usage

package/.agent/mindforge/quick.md

@@ -1,3 +1,7 @@
+---
+description: Use QUICK for:
+---
+
 # MindForge — Quick Command
 # Usage: /mindforge:quick [--research] [--review] [--full]
 # For ad-hoc tasks that don't need full lifecycle management.

package/.agent/mindforge/release.md

@@ -1,3 +1,7 @@
+---
+description: Execute the complete MindForge v1.0.0 (or any version) release pipeline.
+---
+
 # MindForge — Release Command
 # Usage: /mindforge:release [--version X.Y.Z] [--dry-run] [--checklist-only]
 # ⚠️  This command is for releasing the MindForge framework itself.

package/.agent/mindforge/remember.md

@@ -1,3 +1,7 @@
+---
+description: Manage the MindForge long-term memory (knowledge graph).
+---
+
 # /mindforge:remember
 
 Manage the MindForge long-term memory (knowledge graph).

package/.agent/mindforge/research.md

@@ -1,3 +1,7 @@
+---
+description: Deep research using Gemini 1.5 Pro's 1-million-token context window.
+---
+
 # MindForge v2 — Research Command
 # Usage: /mindforge:research [topic] [--type general|library|codebase|compliance] [--url URL]
 

package/.agent/mindforge/retrospective.md

@@ -1,3 +1,7 @@
+---
+description: Facilitate a structured retrospective with objective metrics + qualitative insights.
+---
+
 # MindForge — Retrospective Command
 # Usage: /mindforge:retrospective [phase N|milestone M] [--template agile|4ls|starfish]
 

package/.agent/mindforge/review.md

@@ -1,3 +1,7 @@
+---
+description: - /mindforge:review (no args) → review all uncommitted changes (git diff)
+---
+
 # MindForge — Review Command
 # Usage: /mindforge:review [path|phase N|--staged|--last-commit]
 # Performs a comprehensive code review using code-quality and security skills.

package/.agent/mindforge/security-scan.md

@@ -1,3 +1,7 @@
+---
+description: - Default: OWASP Top 10 review on the changed files or specified path
+---
+
 # MindForge — Security Scan Command
 # Usage: /mindforge:security-scan [path] [--deep] [--deps] [--secrets]
 # Standalone security scan. Can be run independently of the phase lifecycle.

package/.agent/mindforge/ship.md

@@ -1,3 +1,7 @@
+---
+description: Create a release PR for a verified phase. Usage: /mindforge:ship [N]
+---
+
 Create a release PR for a verified phase. Usage: /mindforge:ship [N]
 
 ## Pre-check

package/.agent/mindforge/skills.md

@@ -1,3 +1,7 @@
+---
+description: /mindforge:skills list
+---
+
 # MindForge — Skills Command
 # Usage: /mindforge:skills [subcommand] [args]
 # Subcommands: list | add | update | validate | info | search

package/.agent/mindforge/status.md

@@ -1,3 +1,7 @@
+---
+description: Display a rich dashboard of the current project state.
+---
+
 # MindForge — Status Command
 # Usage: /mindforge:status
 

package/.agent/mindforge/steer.md

@@ -1,3 +1,7 @@
+---
+description: Injects mid-execution guidance into the running autonomous engine.
+---
+
 # /mindforge:steer "[instruction]"
 
 **Purpose**: Injects mid-execution guidance into the running autonomous engine.

package/.agent/mindforge/sync-confluence.md

@@ -1,3 +1,7 @@
+---
+description: Publish approved planning artifacts to Confluence. Usage:
+---
+
 Publish approved planning artifacts to Confluence. Usage:
 `/mindforge:sync-confluence [--architecture] [--phase N] [--milestone name]`
 

package/.agent/mindforge/sync-jira.md

@@ -1,3 +1,7 @@
+---
+description: Synchronise MindForge phase and plan metadata to Jira. Usage:
+---
+
 Synchronise MindForge phase and plan metadata to Jira. Usage:
 `/mindforge:sync-jira [--phase N] [--plan M]`
 

package/.agent/mindforge/tokens.md

@@ -1,3 +1,7 @@
+---
+description: Display token consumption profile and efficiency analysis.
+---
+
 # MindForge — Token Usage Command
 # Usage: /mindforge:tokens [--phase N] [--session ID] [--window short|medium|long] [--optimise]
 

package/.agent/mindforge/update.md

@@ -1,3 +1,7 @@
+---
+description: Check for and apply MindForge framework updates in a safe, scope-preserving way.
+---
+
 # MindForge — Update Command
 # Usage: /mindforge:update [--apply] [--force] [--check] [--skip-changelog]
 

package/.agent/mindforge/verify-phase.md

@@ -1,3 +1,7 @@
+---
+description: Human acceptance testing for a completed phase. Usage: /mindforge:verify-phase [N]
+---
+
 Human acceptance testing for a completed phase. Usage: /mindforge:verify-phase [N]
 
 ## Pre-check

package/.agent/mindforge/workspace.md

@@ -1,3 +1,7 @@
+---
+description: Monorepo workspace management.
+---
+
 # MindForge — Workspace Command
 # Usage: /mindforge:workspace [detect|list|plan phase N|test]
 

package/.agent/workflows/forge:help.md

@@ -0,0 +1,10 @@
+---
+description: Show all available FORGE commands and what they do.
+---
+Show all available FORGE commands and what they do.
+
+List every .md file in .claude/commands/forge/ and display:
+- Command name (filename without extension)
+- First line of the file as its description
+
+Format as a clean table. Also remind the user to read CLAUDE.md if they haven't yet.

package/.agent/workflows/forge:init-project.md

@@ -0,0 +1,35 @@
+---
+description: Initialize a new project under the FORGE framework.
+---
+Initialize a new project under the FORGE framework.
+
+Follow these steps in order:
+
+1. Ask the user these questions one at a time (wait for each answer before asking the next):
+   - What is this project? (1-2 sentence description)
+   - Who is the target user?
+   - What is the core problem it solves?
+   - What tech stack do you want to use? (or "help me decide")
+   - What is absolutely NOT in scope for v1?
+   - What does success look like at the end of v1?
+
+2. If the user said "help me decide" on tech stack, ask 3 clarifying questions then recommend a stack with brief reasoning.
+
+3. Create `.planning/PROJECT.md` with:
+   - Project name and one-line description
+   - Problem statement
+   - Target user
+   - Tech stack (with brief rationale for each choice)
+   - v1 scope (what's in)
+   - Out of scope (what's explicitly not in v1)
+   - Success criteria
+
+4. Create `.planning/STATE.md` with:
+   - Status: Project initialized
+   - Current phase: None (not started)
+   - Last action: Project initialization
+   - Next step: Run /forge:plan-phase 1
+
+5. Create `.planning/REQUIREMENTS.md` (blank template with sections)
+
+6. Tell the user: "Project initialized. Run /forge:plan-phase 1 to begin planning your first phase."

package/.agent/workflows/forge:plan-phase.md

@@ -0,0 +1,33 @@
+---
+description: Plan a phase of the project. Usage: /forge:plan-phase [N]
+---
+Plan a phase of the project. Usage: /forge:plan-phase [N]
+
+If N is not provided, check STATE.md for the current phase and use that.
+
+Steps:
+1. Read PROJECT.md, REQUIREMENTS.md, and STATE.md.
+2. Ask the user: "Describe what phase [N] should accomplish in 2-3 sentences."
+3. Ask: "Are there any specific implementation decisions you've already made for this phase?"
+4. Spawn a research subagent: Read the project's tech stack from PROJECT.md and research the best patterns, libraries, and pitfalls for implementing this phase. Write findings to `.planning/phases/phase-[N]/RESEARCH.md`.
+5. Create 3-6 atomic task plans in `.planning/phases/phase-[N]/`. Each PLAN file must use this XML format:
+```xml
+<plan>
+  <task>Task name</task>
+  <files>
+    specific/file/paths/to/touch.ts
+  </files>
+  <instructions>
+    Precise implementation instructions. Include:
+    - Which library to use and why (mention specific version if relevant)
+    - Any gotchas or anti-patterns to avoid
+    - The exact approach, not just "implement X"
+  </instructions>
+  <verify>Specific command or check that confirms this task is done</verify>
+  <done>One sentence definition of done for this task</done>
+</plan>
+```
+
+6. Check each plan against REQUIREMENTS.md. If a plan implements something out of scope, revise it.
+7. Update STATE.md: current phase = N, status = "Phase [N] planned, ready to execute"
+8. Tell the user: "Phase [N] has [X] task plans ready. Run /forge:execute-phase [N] to begin execution."

package/.agent/workflows/mindforge:add-backlog.md

@@ -0,0 +1,24 @@
+---
+description: Capture ideas in a "parking lot" to keep them out of the active phase sequence
+---
+<objective>
+Capture an idea, task, or feature request in a "parking lot" section of the ROADMAP.md to prevent it from cluttering the active development phases.
+</objective>
+
+<execution_context>
+.claude/commands/mindforge/add-backlog.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (The description of the backlog item)
+Target File: ROADMAP.md
+State: Uses 999.x numbering scheme for backlog items.
+</context>
+
+<process>
+1. **Read ROADMAP.md**: Locate the `## Backlog` or `## Future Milestones` section.
+2. **Initialize if missing**: If no backlog section exists, create `## Backlog` at the end of the file.
+3. **Determine numbering**: Find the last `999.x` item. If none, start with `999.1`.
+4. **Append item**: Add the new backlog item with the determined number and the provided description.
+5. **Confirm**: Notify the user that the item has been parked in the backlog.
+</process>

package/.agent/workflows/mindforge:agent.md

@@ -0,0 +1,25 @@
+---
+description: Spawn or invoke a specialized enterprise persona from the MindForge library
+---
+<objective>
+Provide an on-demand mechanism to "spawn" any of the 13+ standardized MindForge personas. This allows the user to switch the AI assistant's context, role, and process to a specific specialized mode (e.g., Roadmapper, Security Reviewer, Analyst).
+</objective>
+
+<execution_context>
+.claude/commands/mindforge/agent.md
+</execution_context>
+
+<context>
+Personas Directory: `.mindforge/personas/`
+State: Loads the persona's XML-tagged structure into the active system context.
+</context>
+
+<process>
+1. **List Personas**: If no arguments are provided, list all available `.md` files in `.mindforge/personas/` with their name and description (parsed from YAML).
+2. **Load Persona**: If a name is provided:
+    - Locate `.mindforge/personas/[name].md`.
+    - Read the file content.
+    - Present the persona's role and success criteria to the user.
+3. **Switch Mode**: Instruct the AI (through the current session context) to adopt the role, philosophy, and process defined in the loaded file.
+4. **Initial Task**: If a prompt is provided as the second argument, immediately execute that prompt using the newly adopted persona.
+</process>

package/.agent/workflows/mindforge:approve.md

@@ -0,0 +1,21 @@
+---
+description: Process pending approvals and emergency overrides. Usage:
+---
+Process pending approvals and emergency overrides. Usage:
+`/mindforge:approve [approval-id] [--approve|--reject] [--reason "..."] [--emergency]`
+
+## Listing approvals
+Scan `.planning/approvals/` and show only files with `status: pending` unless
+ the user explicitly asks for historical records.
+
+## Standard approval flow
+1. Read the approval file
+2. Confirm current identity from `git config user.email` or `$USER`
+3. Validate approver eligibility from `INTEGRATIONS-CONFIG.md`
+4. Record approval or rejection with timestamp and reason
+
+## Emergency overrides
+Emergency override requires the `--emergency` flag.
+Read `EMERGENCY_APPROVERS` from `INTEGRATIONS-CONFIG.md` and deny the request if
+ the current identity is not listed. Document that git-config-based identity is
+ a convenience layer, not a high-assurance identity proof.