Capability Reference

The Four Stations

Plan Forge is an AI-Native SDLC Forge Shop. Every capability on this page lives in one of four stations. See the full Shop Tour for deep-dive walkthroughs.

MCP Tools

All tools callable via Copilot Chat, Claude, Cursor, or any MCP client. Start with forge_capabilities for full discovery.

🧭 Forge-Master Studio (1 tool + dashboard — v2.63+) open-ended reasoning · read-only

A read-only reasoning orchestrator. Classifies user intent, retrieves OpenBrain memory context, and orchestrates other forge tools on the agent's behalf. Purpose-built for multi-step troubleshooting, plan status queries, and funneling ideas into Crucible smelts — without chaining tools by hand. Phase-29 added the Forge-Master Studio dashboard tab with a curated prompt gallery, streaming chat, and a live tool-call trace pane.

forge_master_ask

Accepts a freeform message. Returns a structured reasoning response built from intent classification, memory retrieval, and allowlist-gated read-only tool calls.

Studio tab · prompt gallery · chat stream · tool-call trace

Dashboard UI at localhost:3100/dashboard. Also available as CLI via pforge forge-master status|logs.

Autonomous Execution

Agent-Per-Slice Routing

Assign a different AI model to each execution role. The orchestrator auto-selects based on the current operation — tune cost vs. quality at every stage without changing your plan files.

Auto-Escalation

When a slice fails on one model, the orchestrator automatically walks the escalationChain and retries on the next model — no manual intervention. Emits a slice-escalated event on each re-route.

Model Performance Tracking

Per-slice performance data is appended to .forge/model-performance.json after every run. The orchestrator reads this on startup and auto-selects the cheapest model with >80% historical success rate for each slice type.

Quorum Mode

Multi-model consensus: dispatch complex slices to 3 AI models for independent analysis, synthesize the best approach, then execute with higher confidence. A/B tested: +20% more tests, better code structure, fewer brittle patterns vs single-model execution. Read the full A/B test results →

Web UI — Live Dashboard

localhost:3100/dashboard — 8 real-time tabs via WebSocket. No build step. Also runs standalone: node pforge-mcp/server.mjs --dashboard-only

Agents & Skills

Temper Guards & Warning Signs — Every instruction file includes tables of common shortcuts agents use (with rebuttals) and observable anti-patterns that indicate the file's guidance is being violated.

Observability & Memory

Stack Presets

REST API — External Integration

The MCP server exposes a REST API for external agents, CI systems, and tools like OpenClaw. Discover the full surface via GET /api/capabilities or GET /.well-known/plan-forge.json on first connect.

Full curl examples and config template: AGENT-SETUP.md Section 6.

Bridge — External Notifications

The Plan Forge Bridge subscribes to the WebSocket hub and dispatches run events to external platforms. Rate-limited (1/5s per channel), with automatic reconnect.

{
  "bridge": {
    "enabled": true,
    "channels": [
      { "type": "telegram", "url": "https://api.telegram.org/bot<TOKEN>/sendMessage", "chatId": "<ID>", "level": "important" },
      { "type": "slack",    "url": "https://hooks.slack.com/services/...", "level": "all" },
      { "type": "discord",  "url": "https://discord.com/api/webhooks/...", "level": "critical" },
      { "type": "webhook",  "url": "https://your-endpoint.example.com/hook", "level": "all" }
    ]
  }
}

CI/CD Hook Event

The ci-triggered event is emitted when a CI workflow is dispatched from a plan run. Observable via the WebSocket hub or captured in the run's events.log. The slice-escalated event is emitted when a slice is re-routed to a new model via the escalation chain.

Updating an Existing Install

pforge smith automatically checks GitHub for a newer Plan Forge release — 5 s timeout, 24 h cache in .forge/version-check.json, silent when offline.

pforge self-update --force  # latest GitHub release
pforge update              # auto-mode (v2.56.0+)
pforge update --from-github # force GitHub tag

git clone https://github.com/srnichols/plan-forge.git

Control the update source with pforge config set update-source <auto|github-tags|local-sibling> (v2.56.0+). See Manual Appendix G.

Dual-Publish Extensions

pforge ext publish <path> validates the extension and outputs two catalog entries in one command.

GitHub Stack Integration

First-class integration with GitHub Copilot, GitHub Models, and GitHub Actions for cloud-based execution and security-driven plan generation.