# eforge

> eforge is a build-engine kernel that turns normalized build source into reviewed, validated code.

eforge is an autonomous build-and-review kernel for code generation. It accepts normalized build source from direct prompts, PRD files, file inputs, or optional producer surfaces; plans implementation steps using AI agents; builds in parallel worktrees; reviews the result; and merges to the base branch. Playbooks are owned by the first-party eforge-playbooks extension; session plans and first-party planning extensions are optional workflow or host surfaces around the kernel. The daemon keeps a persistent HTTP server for queue management and live SSE event streaming.

## Core kernel guides

- [Getting Started](/docs/getting-started.md): Install eforge, initialize a project, and run your first direct prompt, PRD, or file build
- [Core concepts](/docs/concepts.md): Pipeline concepts, harnesses, tiers, queues, and agent-readable artifacts
- [Configuration guide](/docs/configuration.md): Configure the core daemon, builds, profiles, and optional workflow or extension surfaces
- [Profiles guide](/docs/profiles.md): Create, activate, and route agent runtime profiles across project and user scopes

## Optional workflow guides

- [Stacked PRs](/docs/stacking.md): Configure git-spice-backed artifact branch stacks and PR targeting

## Extension platform guides

- [Extensions guide](/docs/extensions.md): How native eforge extensions are discovered, trusted, loaded, authored, and bounded without product-specific first-party workflow semantics
- [Extensions API reference](/docs/extensions-api.md): Typed extension SDK concepts, ConsoleWorkstation APIs, frameBundle workstations, browser bridge helpers, SDK stability, hook registration, context objects, runtime support, and unsupported boundaries

## First-party extension guides

- [eforge-playbooks guide](/docs/playbooks.md): Install, manage, and run reusable playbooks through the first-party eforge-playbooks extension
- [eforge-plan guide](/docs/eforge-plan.md): Optional first-party eforge-plan extension documentation for planning, backlog, recommendation, workstation, and revision workflows

## Integration guides

- [Integrations guide](/docs/integrations.md): Use Claude Code, Pi, the standalone CLI, shell hooks, input sources, Langfuse tracing, daemon APIs, and the Console dashboard

## Operations guides

- [Troubleshooting guide](/docs/troubleshooting.md): Recover from failed builds, docs drift, invalid profiles, and other common issues

## Reference guides

- [Glossary](/docs/glossary.md): eforge-specific terms such as profile, worktree, planner, reviewer, recovery sidecar, playbook, and first-party extension ownership

## Canonical reference

- [CLI reference](/reference/cli.md): All eforge CLI subcommands and options
- [Daemon HTTP API](/reference/api.md): REST endpoints and SSE streams exposed by the eforge daemon
- [Event protocol](/reference/events.md): All EforgeEvent discriminant variants emitted on the SSE stream
- [Configuration](/reference/config.md): eforge/config.yaml schema with all fields and defaults
- [MCP tools and skills](/reference/tools.md): MCP tools (Claude Code plugin) and native commands (Pi extension) plus skill parity table

## Packages and source

- [GitHub repository](https://github.com/eforge-build/eforge): Source repository for the engine, daemon, docs, Claude Code plugin, and Pi extension
- [Standalone CLI npm package](https://www.npmjs.com/package/@eforge-build/eforge): npm package for the eforge CLI and daemon runtime
- [Pi extension npm package](https://www.npmjs.com/package/@eforge-build/pi-eforge): npm package for the native Pi integration
- [eforge-playbooks npm package](https://www.npmjs.com/package/@eforge-build/eforge-playbooks): First-party extension for scoped playbook management and execution handoff
- [eforge-plan npm package](https://www.npmjs.com/package/@eforge-build/eforge-plan): First-party extension for planning, backlog, recommendation, and revision workflows
- [Extension SDK npm package](https://www.npmjs.com/package/@eforge-build/extension-sdk): Public SDK for authoring native eforge extensions and Console workstations
- [Typed client npm package](https://www.npmjs.com/package/@eforge-build/client): Typed daemon routes, wire contracts, events, and browser-safe client helpers

## Schemas

- [Event schema (JSON Schema)](/schemas/events.schema.json)
- [Config schema (JSON Schema)](/schemas/config.schema.json)

## Optional

- [Full LLM reference bundle](/llms-full.txt): Complete concatenated reference documentation for agents that need full context
- [Why eforge](/why): Positioning and product thesis: asynchronous engineering for planned work
- [Extension authoring checklist](/docs/extensions.md#llm-first-extension-authoring-checklist): LLM-first scaffold, validate, test, trust, and reload checklist for native extension authors
- [SDK stability and migration guidance](/docs/extensions-api.md#sdk-stability-and-migration-guidance): Canonical versioning and migration guidance for @eforge-build/extension-sdk authors
- [Project README](https://github.com/eforge-build/eforge#readme): Broader project narrative, screenshots, install notes, and examples