eforge

Enqueue a source for the eforge daemon to build — PRD file, inline description, or conversation context. Use when the user wants to hand work off to eforge.

Initialize or edit eforge/config.yaml team-wide settings, with validation via daemon tools

Author eforge TypeScript extensions from a natural-language request using the existing extension tooling and docs/examples

Inspect the recovery verdict for a failed PRD and apply the recommended action (retry, continue-repair, abandon, or manual)

Create a new agent runtime profile in eforge/profiles/

List, inspect, and switch agent runtime profiles

Initialize eforge in the current project with an interactive setup flow

Safely restart the eforge daemon, checking for active builds first

Check for eforge updates and guide through updating the CLI package and daemon

Synchronize the git-spice stack, preview with dry-run, interpret the sync report, and recover from manual sync conflicts

Set up or reconfigure the eforge workflow preset — landing action, stacking, PR settings, and automatic stack sync

Release a new version of eforge with release notes, changelog, and GitHub Release - supports patch, minor, and major release types

Check eforge run status and queue state via daemon tools

Rebuild eforge from source and restart the daemon. Use during development after making code changes so the MCP tools pick up the latest build.

Analyze documentation drift and enqueue an eforge build to fix it. Use when docs are stale after implementation changes. Works in any project with eforge running.

Analyze eval results to understand signal quality and guide prompt/config changes. Use when the user says "eval-analysis", "analyze eval results", "what do the evals show", "eval regression", or asks about eval signal enrichment.