mindforge-cc 2.0.0-alpha.9 → 2.1.0

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

@@ -0,0 +1,36 @@
+---
+name: mindforge:ui-review
+description: Perform a retroactive visual audit of implemented UI against the DESIGN_SYSTEM.md and UI-SPEC.md
+argument-hint: [N]
+allowed-tools:
+  - view_file
+  - write_to_file
+  - read_browser_page
+  - open_browser_url
+---
+
+<objective>
+Perform a retroactive, multi-pillar visual audit of implemented UI features against the defined Design System and UI-SPEC.md to ensure pixel-perfect fidelity and accessibility compliance.
+</objective>
+
+<execution_context>
+.claude/commands/mindforge/ui-review.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (The phase number [N], optional)
+Sources: `DESIGN_SYSTEM.md`, `UI-SPEC.md`, and the live application UI.
+</context>
+
+<process>
+1. **Identify Target**: Determine the phase to review.
+2. **Audit Application**:
+    - Use the browser tool to inspect the implemented features.
+    - Compare against the `UI-SPEC.md` for spacing, colors, and layout.
+    - Audit for accessibility (ARIA labels, contrast, keyboard navigation).
+3. **Generate UI-REVIEW.md**:
+    - Grade each pillar (Layout, Color, Typography, etc.).
+    - List specific "Needs Work" items.
+    - Provide "Approved" status if all criteria are met.
+4. **Finalize**: Notify the user of the audit results.
+</process>

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

@@ -0,0 +1,31 @@
+---
+name: mindforge:validate-phase
+description: Audit the current phase for requirement coverage and test gaps
+argument-hint: [N]
+allowed-tools:
+  - view_file
+  - list_dir
+---
+
+<objective>
+Audit a completed project phase to ensure every requirement has been addressed and that corresponding automated tests have been implemented and are passing.
+</objective>
+
+<execution_context>
+.claude/commands/mindforge/validate-phase.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (The phase number [N], optional)
+Knowledge: `STATE.md`, `REQUIREMENTS.md`, and the codebase test suite.
+</context>
+
+<process>
+1. **Identify Phase**: Resolve the targeted phase.
+2. **Cross-reference**:
+    - List all requirements in `REQUIREMENTS.md` marked for this phase.
+    - Verify implementation of each requirement in the code.
+    - Check for the existence of passing tests for each requirement.
+3. **Analyze Gaps**: Identify any "orphaned" requirements or features missing tests.
+4. **Report Findings**: Summarize coverage and call out specific gaps to the user.
+</process>

package/.agent/mindforge/workstreams.md

@@ -0,0 +1,35 @@
+---
+name: mindforge:workstreams
+description: Manage parallel feature tracks with isolated state
+argument-hint: [list|create|switch|status|complete]
+allowed-tools:
+  - list_dir
+  - view_file
+  - write_to_file
+  - run_command
+---
+
+<objective>
+Enable developers to work on multiple features or bugs concurrently within the same codebase without state collision. Provides isolated tracking for each "workstream".
+</objective>
+
+<execution_context>
+.claude/commands/mindforge/workstreams.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS (Switch subcommand)
+Storage: .planning/workstreams/
+State: Each workstream maintains its own subset of `STATE.md` or a local context file.
+</context>
+
+<process>
+1. **Route Subcommand**:
+    - `list`: Show all active and archived workstreams in `.planning/workstreams/`.
+    - `create <name>`: Initialize a new workstream directory and baseline state.
+    - `switch <name>`: Update the global pointer in `STATE.md` to the targeted workstream.
+    - `status`: Show the current active workstream and its progress.
+2. **Manage Isolation**:
+    - When switching, ensure current work is saved or stashed if necessary.
+3. **Confirm**: Success/Failure status message to user.
+</process>

package/.claude/CLAUDE.md

@@ -543,3 +543,29 @@ preferences while keeping governance and quality gates intact.
 - `/mindforge:metrics`
 
 ---
+
+## SELF-BUILDING SKILLS PLATFORM (v2.0.0 — Day 13)
+
+### When to suggest /mindforge:learn
+- After a productive phase that introduced a new technology
+- When the user mentions struggling with a specific library
+- After `/mindforge:research` produces findings worth capturing as skills
+- When debug sessions uncover patterns worth remembering
+
+### Auto-capture hook
+When AUTO_CAPTURE_SKILLS=true in MINDFORGE.md:
+After every phase that passes all gates:
+  Run `bin/skills-builder/pattern-detector.js` on the phase SUMMARY files.
+  If patterns found (frequency ≥ 2): present for user approval.
+  If approved: run the full learn pipeline to create a skill.
+
+### AUDIT events for skill learning
+- skill_learned: source_type, source, skill_name, quality_score, tier, cost_usd
+- auto_capture_skipped: phase, patterns_found (0 = no patterns, N = user declined)
+- marketplace_action: action, query/skill_name, quality_score
+
+### New commands (Day 13)
+- /mindforge:learn — convert any documentation into a reusable skill
+- /mindforge:marketplace — discover and install community skills
+
+---

package/.claude/commands/mindforge/add-backlog.md

@@ -0,0 +1,32 @@
+---
+name: mindforge:add-backlog
+description: Capture ideas in a "parking lot" to keep them out of the active phase sequence
+argument-hint: <description>
+allowed-tools:
+  - view_file
+  - write_to_file
+  - replace_file_content
+  - multi_replace_file_content
+---
+
+<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/.claude/commands/mindforge/agent.md

@@ -0,0 +1,31 @@
+---
+name: mindforge:agent
+description: Spawn or invoke a specialized enterprise persona from the MindForge library
+argument-hint: "[persona-name] [prompt]"
+allowed-tools:
+  - list_dir
+  - view_file
+---
+
+<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/.claude/commands/mindforge/approve.md

@@ -1,18 +1,30 @@
-Process pending approvals and emergency overrides. Usage:
-`/mindforge:approve [approval-id] [--approve|--reject] [--reason "..."] [--emergency]`
+---
+name: mindforge:approve
+description: Process pending approvals and emergency overrides
+argument-hint: [approval-id] [--approve|--reject] [--reason "..."] [--emergency]
+allowed-tools:
+  - list_dir
+  - view_file
+  - write_to_file
+---
 
-## Listing approvals
-Scan `.planning/approvals/` and show only files with `status: pending` unless
- the user explicitly asks for historical records.
+<objective>
+Manage the governance layer by reviewing and confirming high-tier architectural or security changes, ensuring all sensitive operations have explicit human authorization.
+</objective>
 
-## 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
+<execution_context>
+.claude/commands/mindforge/approve.md
+</execution_context>
 
-## 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.
+<context>
+Storage: .planning/approvals/
+Governance Config: INTEGRATIONS-CONFIG.md
+</context>
+
+<process>
+1. **List**: Scan for pending approval requests and present them to the user.
+2. **Identity Verification**: Confirm the user's identity via git config or environment.
+3. **Audit Eligibility**: Verify the user has sufficient permissions for the requested tier.
+4. **Record Verdict**: Update the approval file with status, timestamp, and the provided reason.
+5. **Emergency Override**: If `--emergency` is used, bypass standard checks if the identity matches the pre-defined emergency approver list.
+</process>

package/.claude/commands/mindforge/audit.md

@@ -1,30 +1,34 @@
-Query `.planning/AUDIT.jsonl` by phase, event, date, severity, integration, or
- agent. Usage: `/mindforge:audit [filters]`
+---
+name: mindforge:audit
+description: Query the .planning/AUDIT.jsonl log by phase, event, date, or severity
+argument-hint: [filters]
+allowed-tools:
+  - run_command
+  - view_file
+  - list_dir
+---
 
-## Supported options
-- `--phase N`
-- `--event NAME`
-- `--agent NAME`
-- `--severity LEVEL`
-- `--date YYYY-MM-DD`
-- `--summary`
-- `--verify`
-- `--export PATH`
+<objective>
+Provide a structured interface to query and validate the project's audit logs, ensuring accountability and traceability of all agent actions and system events.
+</objective>
 
-## Summary mode
-Summarise counts by event, severity, integration, and phase.
-Entries with `"phase": null` are reported as `project-level`, not dropped.
+<execution_context>
+.claude/commands/mindforge/audit.md
+</execution_context>
 
-## Verify mode
-Validate JSONL shape and chronological ordering.
-Timestamp comparison may use string comparison because ISO-8601 UTC timestamps
- with a `Z` suffix sort lexicographically.
+<context>
+Storage: .planning/AUDIT.jsonl
+Archive: .planning/audit-archive/
+Filters: --phase, --event, --agent, --severity, --date, --summary, --verify, --export
+</context>
 
-## Archive rotation
-If the active audit log exceeds 10,000 lines, rotate it into
- `.planning/audit-archive/` before continuing heavy writes. Rotation must never
- delete history; it archives then resets the active file.
-
-## Export safety
-Validate export paths stay inside the project directory. If a path traversal or
- unsafe destination is requested, export into `.planning/` instead.
+<process>
+1. **Parse Filters**: Identify the search criteria (phase, event, severity, etc.).
+2. **Execute Query**:
+    - Use `grep` or `jq` (if available via bash) to filter the JSONL file.
+    - If `--summary`: Aggregate counts by event and severity.
+    - If `--verify`: Check for JSON validity and chronological integrity.
+3. **Handle Large Logs**: If the log exceeds 10,000 lines, rotate it to the archive directory.
+4. **Export (Optional)**: If `--export` is used, write filtered results to the target path (ensuring project boundary safety).
+5. **Display**: Present the filtered log or summary to the user.
+</process>

package/.claude/commands/mindforge/auto.md

@@ -1,22 +1,33 @@
-# /mindforge:auto [Phase N]
+---
+name: mindforge:auto
+description: Start the MindForge Autonomous Execution Engine
+argument-hint: [Phase N] [--resume] [--headless] [--dry-run]
+allowed-tools:
+  - run_command
+  - list_dir
+  - view_file
+  - write_to_file
+---
 
-**Purpose**: Starts the MindForge Autonomous Execution Engine for the
-specified phase. The agent will execute all waves, handle repairs, and
-perform compliance gates without requiring human confirmation.
+<objective>
+Execute a planned phase entirely unattended, coordinating wave fulfillment, self-repair of minor failures, and compliance gating while maintaining a persistent state checkpoint.
+</objective>
 
-## Usage
-- `/mindforge:auto --phase 3` (Standard unattended mode)
-- `/mindforge:auto --resume` (Resumes from last checkpoint)
-- `/mindforge:auto --headless` (CI/CD optimized output)
-- `/mindforge:auto --dry-run` (Show the wave DAG and plan without executing)
+<execution_context>
+.claude/commands/mindforge/auto.md
+</execution_context>
 
-## Behavior
-- **Zero-Interaction**: Auto-approves Tier 1/2 changes if gates pass.
-- **Self-Repair**: Tries RETRY/DECOMPOSE before asking for help.
-- **Checkpointing**: Constant state persistence in `HANDOFF.json`.
-- **Governance**: ESCALATES on Tier 3 changes (Auth/Payment/PII).
+<context>
+Storage: HANDOFF.json checkpoints.
+Governance: Auto-approves Tier 1/2; Escalates Tier 3.
+Notifications: Requires Slack/Discord webhooks for mission-critical alerts.
+</context>
 
-## Environment Variables
-- `AUTO_MODE_TIMEOUT_MINUTES`: Default 120.
-- `AUTO_PUSH_ON_WAVE_COMPLETE`: Default false.
-- `SLACK_WEBHOOK_URL`: Required for notifications.
+<process>
+1. **Boot**: Load the specifies phase or resume from the last known checkpoint in `HANDOFF.json`.
+2. **Wave Engine**: Execute the DAG of tasks sequentially or in parallel based on dependencies.
+3. **Self-Repair**: Automatically attempt to retry or decompose tasks that encounter recoverable errors.
+4. **Gating**: Evaluate compliance gates between waves. Escalates to human for Tier 3 changes.
+5. **Persistence**: Save state after every successful tool call or task completion.
+6. **Finalize**: Shift status to "Verify Pending" once all waves are complete.
+</process>

package/.claude/commands/mindforge/benchmark.md

@@ -1,33 +1,30 @@
-# MindForge — Benchmark Command
-# Usage: /mindforge:benchmark [--skill skill-name] [--compare skill-a skill-b]
+---
+name: mindforge:benchmark
+description: Measure skill effectiveness and project metrics over time
+argument-hint: [--skill skill-name] [--compare skill-a skill-b]
+allowed-tools:
+  - view_file
+  - list_dir
+---
 
-Measure skill effectiveness over time.
+<objective>
+Analyze command and skill performance by correlating usage data with verify pass rates and project quality scores, facilitating data-driven decisions on tool improvements.
+</objective>
 
-## Single skill benchmark
-For a named skill, analyse AUDIT.jsonl and skill-usage.jsonl:
-- How many times was the skill loaded this month?
-- What is the verify pass rate for tasks where this skill was loaded?
-- Are there anti-patterns less common after this skill is loaded?
-- What is the average session quality score when this skill is active?
+<execution_context>
+.claude/commands/mindforge/benchmark.md
+</execution_context>
 
-Report:
-```
-Skill Benchmark: security-review v1.0.0
-────────────────────────────────────────
-Usage (last 30 days): 47 task loads
-Trigger distribution: text match 68%, file-path 22%, file-name 10%
-Verify pass rate:     91% (vs. 84% baseline without this skill)
-Security findings:    8 HIGH caught (0 CRITICAL missed in tasks using this skill)
-Session quality lift: +6.2 points average when loaded
+<context>
+Sources: AUDIT.jsonl, skill-usage.jsonl
+Metrics: Pass rate, load frequency, anti-pattern reduction, quality lift.
+</context>
 
-Assessment: HIGH VALUE — clear quality improvement signal
-```
-
-## Skill comparison
-Compare two skills head-to-head:
-- Load frequency
-- Verify pass rate improvement
-- Anti-pattern detection rate
-- Context budget cost (token estimate)
-
-Helps decide: should you keep both skills, or deprecate the lower-performer?
+<process>
+1. **Gather Data**: Extract usage and outcome logs for the target skill(s).
+2. **Calculate Trends**: Determine pass rate vs baseline and session quality improvement.
+3. **Generate Assessment**:
+    - For single skill: Provide a usage distribution and quality lift report.
+    - For comparison: Provide a head-to-head comparison on cost and effectiveness.
+4. **Recommendation**: Advise on whether to keep, improve, or deprecate the targeted skills.
+</process>

package/.claude/commands/mindforge/browse.md

@@ -1,26 +1,28 @@
-# /mindforge:browse
+---
+name: mindforge:browse
+description: Control the persistent MindForge browser daemon for visual verification
+argument-hint: <url | action>
+allowed-tools:
+  - open_browser_url
+  - run_command
+---
 
-## Usage
-`@mindforge browse <url | action>`
+<objective>
+Enable the agent to interact with web interfaces, maintain persistent sessions, and perform visual audits of UI changes using an automated browser daemon.
+</objective>
 
-## Description
-Controls the persistent MindForge browser daemon. 
-Maintains session state (cookies/localStorage) for the AI.
+<execution_context>
+.claude/commands/mindforge/browse.md
+</execution_context>
 
-## Actions
-| Action | Description |
-|---|---|
-| `--start` | Initialize browser daemon |
-| `--stop` | Kill browser daemon |
-| `--status` | Show daemon health and active sessions |
-| `--session <name>` | Switch browser context |
-| `--import-session <name> --from <browser>` | Import cookies from host browser (chrome, arc, etc) |
-| `<url>` | Navigate the current page to URL |
-| `click <selector>` | Trigger click event |
-| `type <sel> <text>` | Fill input field |
-| `screenshot` | Capture current viewport |
+<context>
+Security: Daemon binds to 127.0.0.1. Sessions are gitignored.
+State: Supports cookie/localStorage persistence via named sessions.
+</context>
 
-## Security
-- Daemon binds to `127.0.0.1` only.
-- Session files are gitignored.
-- Use only for debugging and visual verification.
+<process>
+1. **Control Daemon**: Start, stop, or query the health/active sessions of the browser daemon.
+2. **Session Management**: Switch between browser contexts or import sessions from the host (Chrome/Arc).
+3. **Navigate & Interact**: Load URLs, click selectors, and type text into input fields.
+4. **Verify**: Capture screenshots of the current viewport for visual confirmation.
+</process>

package/.claude/commands/mindforge/complete-milestone.md

@@ -1,18 +1,32 @@
-Archive a completed milestone, generate a release report, and prepare the next
- milestone. Usage: `/mindforge:complete-milestone <name> <version>`
+---
+name: mindforge:complete-milestone
+description: Archive a completed milestone and prepare the next version
+argument-hint: <name> <version>
+allowed-tools:
+  - list_dir
+  - view_file
+  - write_to_file
+  - run_command
+---
 
-## Step 1 — Validate milestone completion
-Ensure every included phase is verified and has no pending blocking approvals.
+<objective>
+Finalize a project milestone by summarizing shipped value, archiving phase artifacts, and preparing the environment for the next development cycle.
+</objective>
 
-## Step 2 — Generate milestone report
-Summarise shipped phases, notable changes, risks, approvals, and unresolved
- follow-ups.
+<execution_context>
+.claude/commands/mindforge/complete-milestone.md
+</execution_context>
 
-## Step 3 — Archive milestone artifacts
-Archive only the phases included in the milestone, not the entire
- `.planning/phases/` directory. Preserve history in the archive while keeping
- active planning files available in place.
+<context>
+Validation: Ensures all included phases are verified and have no pending approvals.
+Storage: Moves phase files to a milestone-specific archive.
+</context>
 
-## Step 4 — Release metadata
-Create the release tag, update `STATE.md` with milestone summary, and mark the
- project ready for the next version.
+<process>
+1. **Validate**: Confirm every phase in the milestone is signed off and verified.
+2. **Summarize**: Generate a MILESTONE-REPORT with shipped functionality, risks, and follow-ups.
+3. **Archive**: Move the included `.planning/phases/` directories to a persistent milestone archive.
+4. **Tag**: Create a git release tag for the milestone.
+5. **State Reset**: Update `STATE.md` to reflect the milestone completion and target the next version.
+6. **Audit**: Log `milestone_completed` event.
+</process>

package/.claude/commands/mindforge/costs.md

@@ -1,11 +1,28 @@
-# MindForge v2 — Costs Command
-# Usage: /mindforge:costs [--phase N] [--session ID] [--window 7d]
+---
+name: mindforge:costs
+description: Real-time cost tracking for AI model usage
+argument-hint: [--phase N] [--session ID] [--window 7d]
+allowed-tools:
+  - view_file
+  - run_command
+---
 
-## Purpose
-Real-time cost tracking for all AI model usage.
-Enforce daily budgets and see per-model spend.
+<objective>
+Monitor and control project expenses related to AI model usage, enforcing budget guardrails and providing granular spend analysis.
+</objective>
 
-## Metrics
-- Total spend: $X.XX
-- Daily limit usage: XX%
-- Per-model breakdown (Tokens/Cost)
+<execution_context>
+.claude/commands/mindforge/costs.md
+</execution_context>
+
+<context>
+Metrics: Total spend, daily limit usage, per-model breakdown.
+Sources: AUDIT.jsonl and local token logs.
+</context>
+
+<process>
+1. **Gather Usage Data**: Parse logs for the specified phase, session, or time window.
+2. **Calculate Spend**: Apply pricing models to the detected token counts per model.
+3. **Enforce Budgets**: Compare current spend against configured daily and project limits.
+4. **Display Report**: Present the total spend and limit usage as a percentage.
+</process>

package/.claude/commands/mindforge/cross-review.md

@@ -1,17 +1,31 @@
-# MindForge v2 — Cross-Review Command
-# Usage: /mindforge:cross-review [--phase N] [--models list] [--focus area]
+---
+name: mindforge:cross-review
+description: Get code reviewed by multiple AI models simultaneously for consensus validation
+argument-hint: [--phase N] [--models list] [--focus area]
+allowed-tools:
+  - run_command
+  - view_file
+  - write_to_file
+---
 
-## Purpose
-Get the same code diff reviewed by multiple AI models simultaneously.
-Claude finds what Claude finds. GPT-4o finds what GPT-4o finds.
-Consensus findings = high confidence issues.
+<objective>
+Increase review confidence by aggregating findings from multiple diverse AI models, identifying consensus issues and providing a multi-perspective quality assessment.
+</objective>
 
-## Round 1: Primary (Claude)
-Senior architect review.
+<execution_context>
+.claude/commands/mindforge/cross-review.md
+</execution_context>
 
-## Round 2: Adversarial (GPT-4o)
-Critical security and edge case review.
+<context>
+Models: Claude (Primary/Architectural), GPT-4o (Adversarial/Security).
+Focus: Specific area like "security", "performance", or "consistency".
+Pre-check: Models must be available via existing API integrations.
+</context>
 
-## Synthesis
-Consensus detector filters findings.
-Verdict is gating for `/mindforge:ship`.
+<process>
+1. **Round 1 (Primary)**: Execute architectural review using the primary model.
+2. **Round 2 (Adversarial)**: Execute security-focused review using the secondary model.
+3. **Synthesis**: Compare findings from both rounds. Identify consensus "high confidence" issues.
+4. **Final Verdict**: Issue a gating verdict that must be resolved for `/mindforge:ship`.
+5. **Log**: Record the multi-model review results in the audit trail.
+</process>