mindforge-cc 11.3.1 → 11.5.0

package/.claude/commands/mindforge/orch-add-feature.md

@@ -0,0 +1,43 @@
+---
+description: Orchestrate building a brand-new feature end to end — research, plan, TDD, review, gated commit. Thin wrapper over the orch-pipeline skill.
+---
+
+# MindForge — Orch: Add Feature
+# Usage: /mindforge:orch-add-feature <what to add>
+
+Manually launch the **add-feature** orchestration: a gated
+Research → Plan → TDD → Review → Commit pipeline for net-new capability.
+
+## Usage
+
+```
+/mindforge:orch-add-feature <what to add>
+```
+
+Examples:
+
+```
+/mindforge:orch-add-feature add OAuth2 login to the auth service
+/mindforge:orch-add-feature support CSV export in the dashboard
+```
+
+## What It Does
+
+Activate the `orch-pipeline` skill (`.mindforge/skills/orch-pipeline/SKILL.md`)
+with `$ARGUMENTS` as the request and `operation = add-feature`. The engine will:
+
+1. **Step 0 — size classifier**: classify size on blast radius and state the tier
+   in one line (no floor; classify on the three signals). The user may override.
+2. Research existing libraries/patterns (Search-Before-Building), then plan a
+   MindForge XML `<action>` task_list under `.planning/` via
+   `/mindforge:plan-write`. → **GATE 1** (approve plan).
+3. TDD each task via `mindforge-tdd_extended` (new failing tests → green), then
+   `/mindforge:review` (+ the `quick.md` security auto-trigger / `security-reviewer`
+   if a security trigger is touched).
+4. Commit as conventional `feat(...)` commits, each writing a Merkle-linked
+   AUDIT.jsonl entry. → **GATE 2** (confirm before commit).
+
+Honor both gates — do not write implementation before Gate 1, do not commit
+before Gate 2.
+
+If `$ARGUMENTS` is empty, ask the user what capability to add.

package/.claude/commands/mindforge/orch-build-mvp.md

@@ -0,0 +1,48 @@
+---
+description: Orchestrate bootstrapping a working MVP from a design/spec doc — ingest, slice, scaffold, TDD, review, gated commit. Thin wrapper over the orch-pipeline skill (build loop delegates to the swarm; GAN harness deferred).
+---
+
+# MindForge — Orch: Build MVP
+# Usage: /mindforge:orch-build-mvp <path to design/spec doc>
+
+Manually launch the **build-mvp** orchestration: turn an SDD/PRD/system-design
+document into a running vertical slice.
+
+## Usage
+
+```
+/mindforge:orch-build-mvp <path to design/spec doc>
+```
+
+Examples:
+
+```
+/mindforge:orch-build-mvp docs/SDD-v0.6.md
+/mindforge:orch-build-mvp .planning/REQUIREMENTS.md
+```
+
+## What It Does
+
+Activate the `orch-pipeline` skill (`.mindforge/skills/orch-pipeline/SKILL.md`)
+with `$ARGUMENTS` as the doc path and `operation = build-mvp` (default floor:
+**large**, full pipeline incl. Scaffold). The engine will:
+
+1. **Step 0 — size classifier** (floor large). Read the spec; extract scope,
+   locked decisions, and a feature list ordered as **thin vertical slices** (one
+   end-to-end path first), written as MindForge XML under `.planning/` via
+   `/mindforge:plan-write`. → **GATE 1** (approve slice plan).
+2. Scaffold the first end-to-end slice.
+3. **Build loop — delegate to the swarm.** Drive each vertical slice through
+   `WaveExecutor` / the `mindforge-swarm-execution` protocol
+   (`.mindforge/engine/wave-executor.md`), with `SwarmController`
+   (`.mindforge/engine/swarm-controller.md`) selecting the cluster, gated by
+   `mindforge-tdd_extended` (Red-Green) and `/mindforge:cross-review`.
+   > **GAN harness is deferred** — the ECC GAN generate/evaluate inner loop
+   > (`/gan-build`, generator → evaluator) is NOT ported. See the DESCOPE note in
+   > the orch-pipeline skill.
+4. `/mindforge:review` (+ the `quick.md` security auto-trigger / `security-reviewer`
+   on any security-trigger slice), then commit the scaffold and each slice as
+   separate conventional `feat(...)` commits, each writing a Merkle-linked
+   AUDIT.jsonl entry. → **GATE 2**.
+
+If `$ARGUMENTS` is empty, ask the user for the path to the design/spec doc.

package/.claude/commands/mindforge/orch-change-feature.md

@@ -0,0 +1,45 @@
+---
+description: Orchestrate altering an existing, working feature to new desired behavior — update tests to the new spec, change impl, review, gated commit. Thin wrapper over the orch-pipeline skill.
+---
+
+# MindForge — Orch: Change Feature
+# Usage: /mindforge:orch-change-feature <the new desired behavior>
+
+Manually launch the **change-feature** orchestration: change behavior that
+already works to a new desired spec, tests-first.
+
+## Usage
+
+```
+/mindforge:orch-change-feature <the new desired behavior>
+```
+
+Examples:
+
+```
+/mindforge:orch-change-feature alert at 2 warnings instead of 3
+/mindforge:orch-change-feature instead of sorting by date, sort by priority
+```
+
+## What It Does
+
+Activate the `orch-pipeline` skill (`.mindforge/skills/orch-pipeline/SKILL.md`)
+with `$ARGUMENTS` as the request and `operation = change-feature`. The engine will:
+
+1. **Step 0 — size classifier**: classify size (default floor: **small**) and
+   state the tier in one line.
+2. Light plan only if the new behavior needs research, written as MindForge XML
+   under `.planning/` via `/mindforge:plan-write`. → **GATE 1** (approve
+   changed-test plan).
+3. **Update the existing tests** to express the new behavior, then change the
+   implementation until green via `mindforge-tdd_extended`. (Changing the tests
+   first is what makes this a tweak, not a fix.)
+4. `/mindforge:review` (+ the `quick.md` security auto-trigger / `security-reviewer`
+   on a security trigger), then commit as conventional `feat(...)` / `refactor(...)`
+   + Merkle-linked AUDIT.jsonl entry. → **GATE 2**.
+
+Use this only when the feature **works** but should behave differently — not for
+bugs (`/mindforge:orch-fix-defect`) or net-new capability
+(`/mindforge:orch-add-feature`).
+
+If `$ARGUMENTS` is empty, ask the user what behavior should change.

package/.claude/commands/mindforge/orch-fix-defect.md

@@ -0,0 +1,43 @@
+---
+description: Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, gated commit. Thin wrapper over the orch-pipeline skill.
+---
+
+# MindForge — Orch: Fix Defect
+# Usage: /mindforge:orch-fix-defect <what is broken>
+
+Manually launch the **fix-defect** orchestration: prove the bug with a red test,
+then fix to green.
+
+## Usage
+
+```
+/mindforge:orch-fix-defect <what is broken>
+```
+
+Examples:
+
+```
+/mindforge:orch-fix-defect poller crashes on empty upstream response
+/mindforge:orch-fix-defect login returns 500 when email has a plus sign
+```
+
+## What It Does
+
+Activate the `orch-pipeline` skill (`.mindforge/skills/orch-pipeline/SKILL.md`)
+with `$ARGUMENTS` as the request and `operation = fix-defect`. The engine will:
+
+1. **Step 0 — size classifier**: classify size (default floor: **small**, often
+   **tiny**); scope root cause with `/mindforge:map-codebase` if unclear.
+2. **Write a new failing regression test** reproducing the bug, then fix until it
+   goes green via `mindforge-tdd_extended`. (Proving the bug first is what makes
+   this a fix, not a tweak.)
+3. `/mindforge:review` (+ the `quick.md` security auto-trigger / `security-reviewer`
+   if the defect sits in a sensitive path).
+4. Commit as a conventional `fix(...)` commit + Merkle-linked AUDIT.jsonl entry.
+   → **GATE 2** (confirm before commit).
+
+Use this only when behavior is **broken/wrong** — not for intentional changes
+(`/mindforge:orch-change-feature`) or new capability
+(`/mindforge:orch-add-feature`).
+
+If `$ARGUMENTS` is empty, ask the user to describe the defect.

package/.claude/commands/mindforge/orch-refine-code.md

@@ -0,0 +1,43 @@
+---
+description: Orchestrate a behavior-preserving refactor — confirm tests green, restructure without changing behavior, keep green, review, gated commit. Thin wrapper over the orch-pipeline skill.
+---
+
+# MindForge — Orch: Refine Code
+# Usage: /mindforge:orch-refine-code <what to restructure>
+
+Manually launch the **refine-code** orchestration: improve structure while
+behavior stays identical, with the existing test suite as the safety net.
+
+## Usage
+
+```
+/mindforge:orch-refine-code <what to restructure>
+```
+
+Examples:
+
+```
+/mindforge:orch-refine-code extract the HTTP client out of poller.py
+/mindforge:orch-refine-code remove dead code and duplication in the dashboard module
+```
+
+## What It Does
+
+Activate the `orch-pipeline` skill (`.mindforge/skills/orch-pipeline/SKILL.md`)
+with `$ARGUMENTS` as the request and `operation = refine-code`. The engine will:
+
+1. **Step 0 — size classifier**: classify size (default floor: **medium** —
+   restructures touch multiple files).
+2. Confirm the relevant tests exist and are **green before** touching code; add
+   characterization tests first if coverage is thin. Plan the restructure as
+   MindForge XML under `.planning/` via `/mindforge:plan-write`. → **GATE 1**.
+3. Restructure in small steps, re-running tests after each (no new behavior tests
+   — the existing suite proves behavior is unchanged). Dead-code/dup sweeps
+   delegate to `/mindforge:de-slop`.
+4. `/mindforge:review`, then commit as `refactor(...)` (the diff must be
+   behavior-neutral) + Merkle-linked AUDIT.jsonl entry. → **GATE 2**.
+
+Use this only when behavior must **not** change. If behavior should change at
+all, use `/mindforge:orch-change-feature` or `/mindforge:orch-fix-defect`.
+
+If `$ARGUMENTS` is empty, ask the user what to refine.

package/.claude/commands/mindforge/plan-phase.md

@@ -1,5 +1,5 @@
 ---
-description: Plan a project phase. Usage: /mindforge:plan-phase [N]
+description: "Plan a project phase. Usage: /mindforge:plan-phase [N]"
 ---
 
 Plan a project phase. Usage: /mindforge:plan-phase [N]

package/.claude/commands/mindforge/plan-write.md

@@ -23,6 +23,17 @@ Knowledge: ARCHITECTURE.md, CONVENTIONS.md, current codebase structure, dependen
    - Identify constraints: performance, security, backward compatibility
    - Determine target step count (--steps N, default: auto-size based on complexity)
 
+1.5. **EXPLORE the codebase BEFORE decomposing** (per `writing-plans/SKILL.md` →
+   "EXPLORE — Structured Codebase Discovery"): run a structured discovery pass
+   across the 8 search categories — existing patterns, similar features,
+   conventions, dependencies, tests, configs, error handling, integration points.
+   - Capture **Patterns to Mirror** as real `file:line` snippet references (quote
+     the actual code; never invent a convention).
+   - Apply the **"No Prior Knowledge" gate**: the plan must be executable by
+     someone with zero repo knowledge — every convention the plan references must
+     be cited from the actual codebase. If you cannot cite it, explore more.
+   - Feed these mirrored snippets into each step's code/Details below.
+
 2. **Decompose into bite-sized steps**: Break the work into atomic steps where each step:
    - Changes 1-3 files maximum
    - Can be verified independently

package/.claude/commands/mindforge/plant-seed.md

@@ -1,6 +1,6 @@
 ---
-name: mindforge:plant-seed
-description: Capture speculative ideas with triggers that surface automatically when relevant
+name: "mindforge:plant-seed"
+description: "Capture speculative ideas with triggers that surface automatically when relevant"
 argument-hint: <idea>
 allowed-tools:
   - list_dir

package/.claude/commands/mindforge/platform.md

@@ -1,5 +1,5 @@
 ---
-name: mindforge:platform
+name: "mindforge:platform"
 description: "Design internal developer platform. Usage: /mindforge:platform [scope] [--tool backstage|custom] [--teams number]"
 argument-hint: "[scope] [--tool backstage|custom] [--teams number]"
 allowed-tools:

package/.claude/commands/mindforge/plugins.md

@@ -1,5 +1,5 @@
 ---
-description: Read PLUGINS-MANIFEST.md. Display installed plugins with version and permissions.
+description: "Read PLUGINS-MANIFEST.md. Display installed plugins with version and permissions."
 ---
 
 # MindForge — Plugins Command

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

@@ -1,5 +1,5 @@
 ---
-description: Run the AI PR review engine on a pull request diff.
+description: "Run the AI PR review engine on a pull request diff."
 ---
 
 # MindForge — PR Review Command

package/.claude/commands/mindforge/privacy-eng.md

@@ -1,5 +1,5 @@
 ---
-name: mindforge:privacy-eng
+name: "mindforge:privacy-eng"
 description: "Design data privacy engineering system. Usage: /mindforge:privacy-eng [system] [--regulation gdpr|ccpa|hipaa] [--technique anonymization|differential|encryption]"
 argument-hint: "[system] [--regulation gdpr|ccpa|hipaa] [--technique anonymization|differential|encryption]"
 allowed-tools:

package/.claude/commands/mindforge/product-spec.md

@@ -15,6 +15,41 @@ Arguments: $ARGUMENTS (feature name or description, optional --framework for pri
 Knowledge: PROJECT.md, existing BRDs, market research, competitive analysis, user feedback.
 </context>
 
+<gated_question_flow>
+> Adapted from the PRP-PRD interactive flow (PRPs-agentic-eng by Wirasm). This
+> question-flow runs BEFORE and AROUND the `<process>` below — it augments, it
+> does not replace, the personas / RICE / MoSCoW depth. Each gate is an explicit
+> STOP: present the questions, then WAIT FOR USER RESPONSE before proceeding.
+
+Flow: `INITIATE -> FOUNDATION -> GROUNDING -> DEEP DIVE -> GROUNDING (technical) -> DECISIONS -> GENERATE`
+
+1. **INITIATE** — If `$ARGUMENTS` is empty, ask "What do you want to build?" If
+   provided, restate your understanding and ask the user to confirm/adjust.
+   **GATE: wait for the user.**
+2. **FOUNDATION** — Ask (all at once): Who has the problem? What is the observable
+   pain? Why can't they solve it today (and why do alternatives fail)? Why now?
+   How will we know it's solved? **GATE: wait for the user.**
+3. **GROUNDING (market + codebase)** — Research market/competitor context; if a
+   codebase exists, explore relevant patterns. Summarize findings, ask "Does this
+   refine your thinking?" **GATE: brief pause for the user** (may be "continue").
+4. **DEEP DIVE** — Ask: one-sentence vision, primary user, Job-to-Be-Done, explicit
+   non-users, constraints. **GATE: wait for the user.**
+5. **GROUNDING (technical feasibility)** — Trace how similar features are built,
+   map integration points, rate feasibility HIGH/MEDIUM/LOW with reasons. Summarize,
+   ask for unknown technical constraints. **GATE: brief pause for the user.**
+6. **DECISIONS** — Ask: MVP definition, must-have vs nice-to-have, key hypothesis
+   ("We believe [capability] will [solve problem] for [users]; we'll know we're
+   right when [measurable outcome]"), explicit out-of-scope, open questions.
+   **GATE: wait for the user before generating.**
+7. **GENERATE** — Only after the DECISIONS gate, run the `<process>` below and
+   write the output (see `<output_mapping>`).
+
+**Anti-invention rule (MANDATORY)**: Never fill a section with plausible-sounding
+fluff. If information is missing, write **`TBD - needs research`** (and name the
+method to resolve it) rather than inventing an answer. Acknowledge uncertainty
+honestly; list open questions instead of hiding them.
+</gated_question_flow>
+
 <process>
 1. **Define personas**: Create 2-4 user personas relevant to the feature:
    - Name, role, and demographic summary
@@ -65,6 +100,7 @@ Knowledge: PROJECT.md, existing BRDs, market research, competitive analysis, use
    - Technical Constraints and Dependencies
    - Success Metrics (leading and lagging indicators)
    - Release Plan (milestones with dates)
+   - **Implementation Phases** (dependency table — see `<output_mapping>`)
    - Open Questions and Risks
 
 8. **Define success metrics**: For the feature overall:
@@ -88,3 +124,43 @@ Knowledge: PROJECT.md, existing BRDs, market research, competitive analysis, use
     - Timeline with confidence intervals
     - Request specific decisions from specific stakeholders
 </process>
+
+<output_mapping>
+> Adapted from the PRP-PRD Implementation-Phases pattern. The PRD's phase table
+> is the hand-off that lets `/mindforge:plan-phase` and `/mindforge:plan-write`
+> auto-select the next pending phase.
+
+**Primary output path**: write the generated PRD to `.planning/REQUIREMENTS.md`
+(create the `.planning/` directory if it does not exist). This is the file
+`/mindforge:execute-phase` and `/mindforge:plan-phase` read from.
+
+**Implementation-Phases dependency table** — include this section in
+`.planning/REQUIREMENTS.md`. The `Status` / `Parallel` / `Depends` columns let
+downstream commands auto-select the next eligible pending phase (a phase is
+eligible when its `Status` is `pending` and every phase in `Depends` is `complete`):
+
+```markdown
+## Implementation Phases
+
+<!--
+  STATUS:   pending | in-progress | complete
+  PARALLEL: phases that can run concurrently (e.g., "with 4" or "-")
+  DEPENDS:  phases that must be complete first (e.g., "1, 2" or "-")
+-->
+
+| # | Phase | Description | Status | Parallel | Depends |
+|---|-------|-------------|--------|----------|---------|
+| 1 | {Phase name} | {What this phase delivers} | pending | - | - |
+| 2 | {Phase name} | {What this phase delivers} | pending | - | 1 |
+| 3 | {Phase name} | {What this phase delivers} | pending | with 4 | 2 |
+| 4 | {Phase name} | {What this phase delivers} | pending | with 3 | 2 |
+| 5 | {Phase name} | {What this phase delivers} | pending | - | 3, 4 |
+```
+
+**Anti-invention rule still applies**: any phase whose scope is not yet known
+gets `TBD - needs research` in its Description rather than an invented deliverable.
+
+**Next step to report**: tell the user to run `/mindforge:plan-phase` (or
+`/mindforge:plan-write .planning/REQUIREMENTS.md`), which will read this table and
+plan the next pending, dependency-satisfied phase.
+</output_mapping>

package/.claude/commands/mindforge/profile-team.md

@@ -1,5 +1,5 @@
 ---
-description: Generate and maintain team/developer profiles for response personalization.
+description: "Generate and maintain team/developer profiles for response personalization."
 ---
 
 # MindForge — Profile Team Command

package/.claude/commands/mindforge/publish-skill.md

@@ -1,5 +1,5 @@
 ---
-description: Publish a skill to the npm registry (or private registry).
+description: "Publish a skill to the npm registry (or private registry)."
 ---
 
 # MindForge — Publish Skill Command

package/.claude/commands/mindforge/push-notify.md

@@ -1,5 +1,5 @@
 ---
-name: mindforge:push-notify
+name: "mindforge:push-notify"
 description: "Design push notification architecture. Usage: /mindforge:push-notify [channel] [--platform ios|android|web] [--priority high|normal|low]"
 argument-hint: "[channel] [--platform ios|android|web] [--priority high|normal|low]"
 allowed-tools:

package/.claude/commands/mindforge/pwa.md

@@ -1,5 +1,5 @@
 ---
-name: mindforge:pwa
+name: "mindforge:pwa"
 description: "Progressive Web App design. Usage: /mindforge:pwa [app] [--cache networkfirst|cachefirst|stale] [--scope full|partial]"
 argument-hint: "[app] [--cache networkfirst|cachefirst|stale] [--scope full|partial]"
 allowed-tools:

package/.claude/commands/mindforge/qa.md

@@ -1,5 +1,5 @@
 ---
-description: @mindforge qa [--phase N] [--auto]
+description: "@mindforge qa [--phase N] [--auto]"
 ---
 
 # /mindforge:qa

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

@@ -1,5 +1,5 @@
 ---
-description: Run weighted 4-dimension quality scoring on current output. Usage - /mindforge:quality-audit [target] [--mode quick|full|comparative] [--compare path]
+description: "Run weighted 4-dimension quality scoring on current output. Usage - /mindforge:quality-audit [target] [--mode quick|full|comparative] [--compare path]"
 ---
 
 <objective>

package/.claude/commands/mindforge/queue.md

@@ -1,5 +1,5 @@
 ---
-description: Design message queue topology and broker selection. Usage - /mindforge:queue [domain] [--broker kafka|rabbitmq|sqs] [--pattern fanout|topic|p2p]
+description: "Design message queue topology and broker selection. Usage - /mindforge:queue [domain] [--broker kafka|rabbitmq|sqs] [--pattern fanout|topic|p2p]"
 ---
 
 <objective>

package/.claude/commands/mindforge/quick.md

@@ -1,5 +1,5 @@
 ---
-description: Use QUICK for:
+description: "Use QUICK for:"
 ---
 
 # MindForge — Quick Command

package/.claude/commands/mindforge/rag.md

@@ -1,5 +1,5 @@
 ---
-description: Design RAG pipeline architecture with chunking and retrieval. Usage - /mindforge:rag [corpus] [--chunking semantic|fixed] [--retrieval hybrid] [--rerank]
+description: "Design RAG pipeline architecture with chunking and retrieval. Usage - /mindforge:rag [corpus] [--chunking semantic|fixed] [--retrieval hybrid] [--rerank]"
 ---
 
 <objective>

package/.claude/commands/mindforge/rate-limit.md

@@ -1,5 +1,5 @@
 ---
-description: Design rate limiting strategy with per-tenant quotas. Usage - /mindforge:rate-limit [api] [--algorithm token-bucket|sliding-window] [--per-tenant]
+description: "Design rate limiting strategy with per-tenant quotas. Usage - /mindforge:rate-limit [api] [--algorithm token-bucket|sliding-window] [--per-tenant]"
 ---
 
 <objective>

package/.claude/commands/mindforge/react-native.md

@@ -1,5 +1,5 @@
 ---
-name: mindforge:react-native
+name: "mindforge:react-native"
 description: "React Native specific architecture guidance. Usage: /mindforge:react-native [feature] [--arch new|legacy] [--state redux|zustand|jotai]"
 argument-hint: "[feature] [--arch new|legacy] [--state redux|zustand|jotai]"
 allowed-tools:

package/.claude/commands/mindforge/realtime-analytics.md

@@ -1,5 +1,5 @@
 ---
-name: mindforge:realtime-analytics
+name: "mindforge:realtime-analytics"
 description: "Design real-time analytics backend. Usage: /mindforge:realtime-analytics [domain] [--engine clickhouse|druid|pinot] [--latency sub-second|seconds]"
 argument-hint: "[domain] [--engine clickhouse|druid|pinot] [--latency sub-second|seconds]"
 allowed-tools:

package/.claude/commands/mindforge/record-learning.md

@@ -1,5 +1,5 @@
 ---
-description: Append a new Learning Entry to the Evolution Log in AGENTS_LEARNING.md
+description: "Append a new Learning Entry to the Evolution Log in AGENTS_LEARNING.md"
 ---
 
 # /mindforge:record-learning

package/.claude/commands/mindforge/release.md

@@ -1,5 +1,5 @@
 ---
-description: Execute the complete MindForge v1.0.0 (or any version) release pipeline.
+description: "Execute the complete MindForge v1.0.0 (or any version) release pipeline."
 ---
 
 # MindForge — Release Command

package/.claude/commands/mindforge/remember.md

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

package/.claude/commands/mindforge/research.md

@@ -1,5 +1,5 @@
 ---
-description: Deep research using Gemini 1.5 Pro's 1-million-token context window.
+description: "Deep research using Gemini 1.5 Pro's 1-million-token context window."
 ---
 
 # MindForge v2 — Research Command

package/.claude/commands/mindforge/retrospective.md

@@ -1,5 +1,5 @@
 ---
-description: Facilitate a structured retrospective with objective metrics + qualitative insights.
+description: "Facilitate a structured retrospective with objective metrics + qualitative insights."
 ---
 
 # MindForge — Retrospective Command

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

@@ -1,6 +1,6 @@
 ---
-name: mindforge:review-backlog
-description: Review and promote backlog items to the active phase sequence
+name: "mindforge:review-backlog"
+description: "Review and promote backlog items to the active phase sequence"
 argument-hint: [optional filters]
 allowed-tools:
   - view_file

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

@@ -1,5 +1,5 @@
 ---
-description: - /mindforge:review (no args) → review all uncommitted changes (git diff)
+description: "- /mindforge:review (no args) → review all uncommitted changes (git diff)"
 ---
 
 # MindForge — Review Command

package/.claude/commands/mindforge/rfc.md

@@ -1,5 +1,5 @@
 ---
-description: Decompose a specification into an executable dependency DAG with parallel waves. Usage - /mindforge:rfc [spec-path] [--output DAG.json] [--worktree] [--execute]
+description: "Decompose a specification into an executable dependency DAG with parallel waves. Usage - /mindforge:rfc [spec-path] [--output DAG.json] [--worktree] [--execute]"
 ---
 
 <objective>

package/.claude/commands/mindforge/santa.md

@@ -1,5 +1,5 @@
 ---
-description: Run multi-angle verification by spawning 2-3 independent reviewers on current work. Usage - /mindforge:santa [scope] [--angles 2|3] [--batch-sample]
+description: "Run multi-angle verification by spawning 2-3 independent reviewers on current work. Usage - /mindforge:santa [scope] [--angles 2|3] [--batch-sample]"
 ---
 
 <objective>

package/.claude/commands/mindforge/secrets-mgmt.md

@@ -1,5 +1,5 @@
 ---
-name: mindforge:secrets-mgmt
+name: "mindforge:secrets-mgmt"
 description: "Design secrets management platform. Usage: /mindforge:secrets-mgmt [scope] [--tool vault|aws-sm|doppler] [--rotation auto|manual]"
 argument-hint: "[scope] [--tool vault|aws-sm|doppler] [--rotation auto|manual]"
 allowed-tools:

package/.claude/commands/mindforge/secrets.md

@@ -1,5 +1,5 @@
 ---
-description: Design secrets rotation strategy with zero-downtime. Usage - /mindforge:secrets [--store vault|aws-sm|gcp-sm] [--schedule 90d] [--ephemeral]
+description: "Design secrets rotation strategy with zero-downtime. Usage - /mindforge:secrets [--store vault|aws-sm|gcp-sm] [--schedule 90d] [--ephemeral]"
 ---
 
 <objective>

package/.claude/commands/mindforge/security-scan.md

@@ -1,5 +1,5 @@
 ---
-description: - Default: OWASP Top 10 review on the changed files or specified path
+description: "- Default: OWASP Top 10 review on the changed files or specified path"
 ---
 
 # MindForge — Security Scan Command

package/.claude/commands/mindforge/serverless.md

@@ -1,5 +1,5 @@
 ---
-name: mindforge:serverless
+name: "mindforge:serverless"
 description: "Design serverless function composition and cost model. Usage: /mindforge:serverless [app] [--composition step-functions|choreography] [--cold-start mitigate]"
 argument-hint: "[app] [--composition step-functions|choreography] [--cold-start mitigate]"
 allowed-tools:

package/.claude/commands/mindforge/session-report.md

@@ -1,6 +1,6 @@
 ---
-name: mindforge:session-report
-description: Generate a post-session summary document capturing work performed and resource usage
+name: "mindforge:session-report"
+description: "Generate a post-session summary document capturing work performed and resource usage"
 argument-hint: none
 allowed-tools:
   - run_command

package/.claude/commands/mindforge/ship.md

@@ -1,5 +1,5 @@
 ---
-description: Create a release PR for a verified phase. Usage: /mindforge:ship [N]
+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]

package/.claude/commands/mindforge/skills.md

@@ -1,5 +1,5 @@
 ---
-description: /mindforge:skills list
+description: "/mindforge:skills list"
 ---
 
 # MindForge — Skills Command

package/.claude/commands/mindforge/status.md

@@ -1,5 +1,5 @@
 ---
-description: Display a rich dashboard of the current project state.
+description: "Display a rich dashboard of the current project state."
 ---
 
 # MindForge — Status Command

package/.claude/commands/mindforge/steer.md

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