eforge-build

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

Compare eforge eval runs of the same scenario across two or more backends. Reads eforge.log, result.json, and workspace artifacts to judge decision quality stage-by-stage — pipeline composer, planner, builder, tester, reviewer, review-fixer, evaluator — and writes a ranked analysis to the results directory. Use when the user asks to compare backends, rank backends, analyze which backend made better decisions, or review a specific eval run.

Compile a directory of per-scenario eval analyses into a top-level README.md suitable for publishing. Reads analyses/<dated-dir>/*.md, optionally re-aggregates from results/<timestamp>/ result.json files, and writes a factual, non-sensational summary following analyses/_TEMPLATE/. Use when the user asks to publish, compile, or finalize an eval analysis set, or points at an analyses dir containing per-scenario files but no aggregated README.md.