mindforge-cc 9.0.0 → 10.0.0

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

@@ -1,228 +0,0 @@
-<purpose>
-Cross-AI peer review — invoke external AI CLIs to independently review phase plans.
-Each CLI gets the same prompt (PROJECT.md context, phase plans, requirements) and
-produces structured feedback. Results are combined into REVIEWS.md for the planner
-to incorporate via --reviews flag.
-
-This implements adversarial review: different AI models catch different blind spots.
-A plan that survives review from 2-3 independent AI systems is more robust.
-</purpose>
-
-<process>
-
-<step name="detect_clis">
-Check which AI CLIs are available on the system:
-
-```bash
-# Check each CLI
-command -v gemini >/dev/null 2>&1 && echo "gemini:available" || echo "gemini:missing"
-command -v claude >/dev/null 2>&1 && echo "claude:available" || echo "claude:missing"
-command -v codex >/dev/null 2>&1 && echo "codex:available" || echo "codex:missing"
-```
-
-Parse flags from `$ARGUMENTS`:
-- `--gemini` → include Gemini
-- `--claude` → include the agent
-- `--codex` → include Codex
-- `--all` → include all available
-- No flags → include all available
-
-If no CLIs are available:
-```
-No external AI CLIs found. Install at least one:
-- gemini: https://github.com/google-gemini/gemini-cli
-- codex: https://github.com/openai/codex
-- claude: https://github.com/anthropics/claude-code
-
-Then run /mindforge-review again.
-```
-Exit.
-
-If only one CLI is the current runtime (e.g. running inside the agent), skip it for the review
-to ensure independence. At least one DIFFERENT CLI must be available.
-</step>
-
-<step name="gather_context">
-Collect phase artifacts for the review prompt:
-
-```bash
-INIT=$(node ".agent/bin/mindforge-tools.cjs" init phase-op "${PHASE_ARG}")
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Read from init: `phase_dir`, `phase_number`, `padded_phase`.
-
-Then read:
-1. `.planning/PROJECT.md` (first 80 lines — project context)
-2. Phase section from `.planning/ROADMAP.md`
-3. All `*-PLAN.md` files in the phase directory
-4. `*-CONTEXT.md` if present (user decisions)
-5. `*-RESEARCH.md` if present (domain research)
-6. `.planning/REQUIREMENTS.md` (requirements this phase addresses)
-</step>
-
-<step name="build_prompt">
-Build a structured review prompt:
-
-```markdown
-# Cross-AI Plan Review Request
-
-You are reviewing implementation plans for a software project phase.
-Provide structured feedback on plan quality, completeness, and risks.
-
-## Project Context
-{first 80 lines of PROJECT.md}
-
-## Phase {N}: {phase name}
-### Roadmap Section
-{roadmap phase section}
-
-### Requirements Addressed
-{requirements for this phase}
-
-### User Decisions (CONTEXT.md)
-{context if present}
-
-### Research Findings
-{research if present}
-
-### Plans to Review
-{all PLAN.md contents}
-
-## Review Instructions
-
-Analyze each plan and provide:
-
-1. **Summary** — One-paragraph assessment
-2. **Strengths** — What's well-designed (bullet points)
-3. **Concerns** — Potential issues, gaps, risks (bullet points with severity: HIGH/MEDIUM/LOW)
-4. **Suggestions** — Specific improvements (bullet points)
-5. **Risk Assessment** — Overall risk level (LOW/MEDIUM/HIGH) with justification
-
-Focus on:
-- Missing edge cases or error handling
-- Dependency ordering issues
-- Scope creep or over-engineering
-- Security considerations
-- Performance implications
-- Whether the plans actually achieve the phase goals
-
-Output your review in markdown format.
-```
-
-Write to a temp file: `/tmp/mindforge-review-prompt-{phase}.md`
-</step>
-
-<step name="invoke_reviewers">
-For each selected CLI, invoke in sequence (not parallel — avoid rate limits):
-
-**Gemini:**
-```bash
-gemini -p "$(cat /tmp/mindforge-review-prompt-{phase}.md)" 2>/dev/null > /tmp/mindforge-review-gemini-{phase}.md
-```
-
-**the agent (separate session):**
-```bash
-claude -p "$(cat /tmp/mindforge-review-prompt-{phase}.md)" --no-input 2>/dev/null > /tmp/mindforge-review-claude-{phase}.md
-```
-
-**Codex:**
-```bash
-codex -p "$(cat /tmp/mindforge-review-prompt-{phase}.md)" 2>/dev/null > /tmp/mindforge-review-codex-{phase}.md
-```
-
-If a CLI fails, log the error and continue with remaining CLIs.
-
-Display progress:
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- MindForge ► CROSS-AI REVIEW — Phase {N}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-◆ Reviewing with {CLI}... done ✓
-◆ Reviewing with {CLI}... done ✓
-```
-</step>
-
-<step name="write_reviews">
-Combine all review responses into `{phase_dir}/{padded_phase}-REVIEWS.md`:
-
-```markdown
----
-phase: {N}
-reviewers: [gemini, claude, codex]
-reviewed_at: {ISO timestamp}
-plans_reviewed: [{list of PLAN.md files}]
----
-
-# Cross-AI Plan Review — Phase {N}
-
-## Gemini Review
-
-{gemini review content}
-
----
-
-## the agent Review
-
-{claude review content}
-
----
-
-## Codex Review
-
-{codex review content}
-
----
-
-## Consensus Summary
-
-{synthesize common concerns across all reviewers}
-
-### Agreed Strengths
-{strengths mentioned by 2+ reviewers}
-
-### Agreed Concerns
-{concerns raised by 2+ reviewers — highest priority}
-
-### Divergent Views
-{where reviewers disagreed — worth investigating}
-```
-
-Commit:
-```bash
-node ".agent/bin/mindforge-tools.cjs" commit "docs: cross-AI review for phase {N}" --files {phase_dir}/{padded_phase}-REVIEWS.md
-```
-</step>
-
-<step name="present_results">
-Display summary:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- MindForge ► REVIEW COMPLETE
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Phase {N} reviewed by {count} AI systems.
-
-Consensus concerns:
-{top 3 shared concerns}
-
-Full review: {padded_phase}-REVIEWS.md
-
-To incorporate feedback into planning:
-  /mindforge-plan-phase {N} --reviews
-```
-
-Clean up temp files.
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] At least one external CLI invoked successfully
-- [ ] REVIEWS.md written with structured feedback
-- [ ] Consensus summary synthesized from multiple reviewers
-- [ ] Temp files cleaned up
-- [ ] User knows how to use feedback (/mindforge-plan-phase --reviews)
-</success_criteria>

package/.agent/workflows/mindforge-session-report.md

@@ -1,146 +0,0 @@
-<purpose>
-Generate a post-session summary document capturing work performed, outcomes achieved, and estimated resource usage. Writes SESSION_REPORT.md to .planning/reports/ for human review and stakeholder sharing.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="gather_session_data">
-Collect session data from available sources:
-
-1. **STATE.md** — current phase, milestone, progress, blockers, decisions
-2. **Git log** — commits made during this session (last 24h or since last report)
-3. **Plan/Summary files** — plans executed, summaries written
-4. **ROADMAP.md** — milestone context and phase goals
-
-```bash
-# Get recent commits (last 24 hours)
-git log --oneline --since="24 hours ago" --no-merges 2>/dev/null || echo "No recent commits"
-
-# Count files changed
-git diff --stat HEAD~10 HEAD 2>/dev/null | tail -1 || echo "No diff available"
-```
-
-Read `.planning/STATE.md` to get:
-- Current milestone and phase
-- Progress percentage
-- Active blockers
-- Recent decisions
-
-Read `.planning/ROADMAP.md` to get milestone name and goals.
-
-Check for existing reports:
-```bash
-ls -la .planning/reports/SESSION_REPORT*.md 2>/dev/null || echo "No previous reports"
-```
-</step>
-
-<step name="estimate_usage">
-Estimate token usage from observable signals:
-
-- Count of tool calls is not directly available, so estimate from git activity and file operations
-- Note: This is an **estimate** — exact token counts require API-level instrumentation not available to hooks
-
-Estimation heuristics:
-- Each commit ≈ 1 plan cycle (research + plan + execute + verify)
-- Each plan file ≈ 2,000-5,000 tokens of agent context
-- Each summary file ≈ 1,000-2,000 tokens generated
-- Subagent spawns multiply by ~1.5x per agent type used
-</step>
-
-<step name="generate_report">
-Create the report directory and file:
-
-```bash
-mkdir -p .planning/reports
-```
-
-Write `.planning/reports/SESSION_REPORT.md` (or `.planning/reports/YYYYMMDD-session-report.md` if previous reports exist):
-
-```markdown
-# MindForge Session Report
-
-**Generated:** [timestamp]
-**Project:** [from PROJECT.md title or directory name]
-**Milestone:** [N] — [milestone name from ROADMAP.md]
-
----
-
-## Session Summary
-
-**Duration:** [estimated from first to last commit timestamp, or "Single session"]
-**Phase Progress:** [from STATE.md]
-**Plans Executed:** [count of summaries written this session]
-**Commits Made:** [count from git log]
-
-## Work Performed
-
-### Phases Touched
-[List phases worked on with brief description of what was done]
-
-### Key Outcomes
-[Bullet list of concrete deliverables: files created, features implemented, bugs fixed]
-
-### Decisions Made
-[From STATE.md decisions table, if any were added this session]
-
-## Files Changed
-
-[Summary of files modified, created, deleted — from git diff stat]
-
-## Blockers & Open Items
-
-[Active blockers from STATE.md]
-[Any TODO items created during session]
-
-## Estimated Resource Usage
-
-| Metric | Estimate |
-|--------|----------|
-| Commits | [N] |
-| Files changed | [N] |
-| Plans executed | [N] |
-| Subagents spawned | [estimated] |
-
-> **Note:** Token and cost estimates require API-level instrumentation.
-> These metrics reflect observable session activity only.
-
----
-
-*Generated by `/mindforge-session-report`*
-```
-</step>
-
-<step name="display_result">
-Show the user:
-
-```
-## Session Report Generated
-
-📄 `.planning/reports/[filename].md`
-
-### Highlights
-- **Commits:** [N]
-- **Files changed:** [N]  
-- **Phase progress:** [X]%
-- **Plans executed:** [N]
-```
-
-If this is the first report, mention:
-```
-💡 Run `/mindforge-session-report` at the end of each session to build a history of project activity.
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Session data gathered from STATE.md, git log, and plan files
-- [ ] Report written to .planning/reports/
-- [ ] Report includes work summary, outcomes, and file changes
-- [ ] Filename includes date to prevent overwrites
-- [ ] Result summary displayed to user
-</success_criteria>

package/.agent/workflows/mindforge-settings.md

@@ -1,283 +0,0 @@
-<purpose>
-Interactive configuration of MindForge workflow agents (research, plan_check, verifier) and model profile selection via multi-question prompt. Updates .planning/config.json with user preferences. Optionally saves settings as global defaults (~/.mindforge/defaults.json) for future projects.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="ensure_and_load_config">
-Ensure config exists and load current state:
-
-```bash
-node ".agent/bin/mindforge-tools.cjs" config-ensure-section
-INIT=$(node ".agent/bin/mindforge-tools.cjs" state load)
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Creates `.planning/config.json` with defaults if missing and loads current config values.
-</step>
-
-<step name="read_current">
-```bash
-cat .planning/config.json
-```
-
-Parse current values (default to `true` if not present):
-- `workflow.research` — spawn researcher during plan-phase
-- `workflow.plan_check` — spawn plan checker during plan-phase
-- `workflow.verifier` — spawn verifier during execute-phase
-- `workflow.nyquist_validation` — validation architecture research during plan-phase (default: true if absent)
-- `workflow.ui_phase` — generate UI-SPEC.md design contracts for frontend phases (default: true if absent)
-- `workflow.ui_safety_gate` — prompt to run /mindforge-ui-phase before planning frontend phases (default: true if absent)
-- `model_profile` — which model each agent uses (default: `balanced`)
-- `git.branching_strategy` — branching approach (default: `"none"`)
-</step>
-
-<step name="present_settings">
-Use AskUserQuestion with current values pre-selected:
-
-```
-AskUserQuestion([
-  {
-    question: "Which model profile for agents?",
-    header: "Model",
-    multiSelect: false,
-    options: [
-      { label: "Quality", description: "Opus everywhere except verification (highest cost)" },
-      { label: "Balanced (Recommended)", description: "Opus for planning, Sonnet for research/execution/verification" },
-      { label: "Budget", description: "Sonnet for writing, Haiku for research/verification (lowest cost)" },
-      { label: "Inherit", description: "Use current session model for all agents (best for OpenRouter, local models, or runtime model switching)" }
-    ]
-  },
-  {
-    question: "Spawn Plan Researcher? (researches domain before planning)",
-    header: "Research",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "Research phase goals before planning" },
-      { label: "No", description: "Skip research, plan directly" }
-    ]
-  },
-  {
-    question: "Spawn Plan Checker? (verifies plans before execution)",
-    header: "Plan Check",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "Verify plans meet phase goals" },
-      { label: "No", description: "Skip plan verification" }
-    ]
-  },
-  {
-    question: "Spawn Execution Verifier? (verifies phase completion)",
-    header: "Verifier",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "Verify must-haves after execution" },
-      { label: "No", description: "Skip post-execution verification" }
-    ]
-  },
-  {
-    question: "Auto-advance pipeline? (discuss → plan → execute automatically)",
-    header: "Auto",
-    multiSelect: false,
-    options: [
-      { label: "No (Recommended)", description: "Manual /clear + paste between stages" },
-      { label: "Yes", description: "Chain stages via Task() subagents (same isolation)" }
-    ]
-  },
-  {
-    question: "Enable Nyquist Validation? (researches test coverage during planning)",
-    header: "Nyquist",
-    multiSelect: false,
-    options: [
-      { label: "Yes (Recommended)", description: "Research automated test coverage during plan-phase. Adds validation requirements to plans. Blocks approval if tasks lack automated verify." },
-      { label: "No", description: "Skip validation research. Good for rapid prototyping or no-test phases." }
-    ]
-  },
-  // Note: Nyquist validation depends on research output. If research is disabled,
-  // plan-phase automatically skips Nyquist steps (no RESEARCH.md to extract from).
-  {
-    question: "Enable UI Phase? (generates UI-SPEC.md design contracts for frontend phases)",
-    header: "UI Phase",
-    multiSelect: false,
-    options: [
-      { label: "Yes (Recommended)", description: "Generate UI design contracts before planning frontend phases. Locks spacing, typography, color, and copywriting." },
-      { label: "No", description: "Skip UI-SPEC generation. Good for backend-only projects or API phases." }
-    ]
-  },
-  {
-    question: "Enable UI Safety Gate? (prompts to run /mindforge-ui-phase before planning frontend phases)",
-    header: "UI Gate",
-    multiSelect: false,
-    options: [
-      { label: "Yes (Recommended)", description: "plan-phase asks to run /mindforge-ui-phase first when frontend indicators detected." },
-      { label: "No", description: "No prompt — plan-phase proceeds without UI-SPEC check." }
-    ]
-  },
-  {
-    question: "Git branching strategy?",
-    header: "Branching",
-    multiSelect: false,
-    options: [
-      { label: "None (Recommended)", description: "Commit directly to current branch" },
-      { label: "Per Phase", description: "Create branch for each phase (mindforge/phase-{N}-{name})" },
-      { label: "Per Milestone", description: "Create branch for entire milestone (mindforge/{version}-{name})" }
-    ]
-  },
-  {
-    question: "Enable context window warnings? (injects advisory messages when context is getting full)",
-    header: "Ctx Warnings",
-    multiSelect: false,
-    options: [
-      { label: "Yes (Recommended)", description: "Warn when context usage exceeds 65%. Helps avoid losing work." },
-      { label: "No", description: "Disable warnings. Allows the agent to reach auto-compact naturally. Good for long unattended runs." }
-    ]
-  },
-  {
-    question: "Research best practices before asking questions? (web search during new-project and discuss-phase)",
-    header: "Research Qs",
-    multiSelect: false,
-    options: [
-      { label: "No (Recommended)", description: "Ask questions directly. Faster, uses fewer tokens." },
-      { label: "Yes", description: "Search web for best practices before each question group. More informed questions but uses more tokens." }
-    ]
-  },
-  {
-    question: "Skip discuss-phase in autonomous mode? (use ROADMAP phase goals as spec)",
-    header: "Skip Discuss",
-    multiSelect: false,
-    options: [
-      { label: "No (Recommended)", description: "Run smart discuss before each phase — surfaces gray areas and captures decisions." },
-      { label: "Yes", description: "Skip discuss in /mindforge-autonomous — chain directly to plan. Best for backend/pipeline work where phase descriptions are the spec." }
-    ]
-  }
-])
-```
-</step>
-
-<step name="update_config">
-Merge new settings into existing config.json:
-
-```json
-{
-  ...existing_config,
-  "model_profile": "quality" | "balanced" | "budget" | "inherit",
-  "workflow": {
-    "research": true/false,
-    "plan_check": true/false,
-    "verifier": true/false,
-    "auto_advance": true/false,
-    "nyquist_validation": true/false,
-    "ui_phase": true/false,
-    "ui_safety_gate": true/false,
-    "text_mode": true/false,
-    "research_before_questions": true/false,
-    "discuss_mode": "discuss" | "assumptions",
-    "skip_discuss": true/false
-  },
-  "git": {
-    "branching_strategy": "none" | "phase" | "milestone",
-    "quick_branch_template": <string|null>
-  },
-  "hooks": {
-    "context_warnings": true/false,
-    "workflow_guard": true/false
-  }
-}
-```
-
-Write updated config to `.planning/config.json`.
-</step>
-
-<step name="save_as_defaults">
-Ask whether to save these settings as global defaults for future projects:
-
-```
-AskUserQuestion([
-  {
-    question: "Save these as default settings for all new projects?",
-    header: "Defaults",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "New projects start with these settings (saved to ~/.mindforge/defaults.json)" },
-      { label: "No", description: "Only apply to this project" }
-    ]
-  }
-])
-```
-
-If "Yes": write the same config object (minus project-specific fields like `brave_search`) to `~/.mindforge/defaults.json`:
-
-```bash
-mkdir -p ~/.mindforge
-```
-
-Write `~/.mindforge/defaults.json` with:
-```json
-{
-  "mode": <current>,
-  "granularity": <current>,
-  "model_profile": <current>,
-  "commit_docs": <current>,
-  "parallelization": <current>,
-  "branching_strategy": <current>,
-  "quick_branch_template": <current>,
-  "workflow": {
-    "research": <current>,
-    "plan_check": <current>,
-    "verifier": <current>,
-    "auto_advance": <current>,
-    "nyquist_validation": <current>,
-    "ui_phase": <current>,
-    "ui_safety_gate": <current>,
-    "skip_discuss": <current>
-  }
-}
-```
-</step>
-
-<step name="confirm">
-Display:
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- MindForge ► SETTINGS UPDATED
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-| Setting              | Value |
-|----------------------|-------|
-| Model Profile        | {quality/balanced/budget/inherit} |
-| Plan Researcher      | {On/Off} |
-| Plan Checker         | {On/Off} |
-| Execution Verifier   | {On/Off} |
-| Auto-Advance         | {On/Off} |
-| Nyquist Validation   | {On/Off} |
-| UI Phase             | {On/Off} |
-| UI Safety Gate       | {On/Off} |
-| Git Branching        | {None/Per Phase/Per Milestone} |
-| Skip Discuss         | {On/Off} |
-| Context Warnings     | {On/Off} |
-| Saved as Defaults    | {Yes/No} |
-
-These settings apply to future /mindforge-plan-phase and /mindforge-execute-phase runs.
-
-Quick commands:
-- /mindforge-set-profile <profile> — switch model profile
-- /mindforge-plan-phase --research — force research
-- /mindforge-plan-phase --skip-research — skip research
-- /mindforge-plan-phase --skip-verify — skip plan check
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] Current config read
-- [ ] User presented with 10 settings (profile + 8 workflow toggles + git branching)
-- [ ] Config updated with model_profile, workflow, and git sections
-- [ ] User offered to save as global defaults (~/.mindforge/defaults.json)
-- [ ] Changes confirmed to user
-</success_criteria>