Why Foundry

Foundry connects your product requirements to the code and conventions your project uses. Planning skills define the work. Execution profiles name the checks. A run builds a committed story in a separate worktree and tests the result before acceptance.

Build your domain

Use the E11 platform SDKs for existing capabilities. Ask e11-knowledge for the pinned platform documentation before choosing an API. Put your application rules and uncovered requirements in your own code.

Run e11 init to prepare your checkout. Use e11-prd for requirements, e11-architecture for technical decisions, and e11-create-epics-and-stories for work with acceptance criteria.

Choose the amount of planning

For a small change, address e11-dev-flow in your editor. For a feature, prepare the requirements, design, and stories. Use e11 run for unattended execution with acceptance checks and a spend ceiling.

Follow the result

Money controls when a run starts more work. A cost pause preserves completed work. The dashboard puts your current work, result, and next command on one page. Fresh checkouts use e11 init without manual storage setup.

Get started to start your first run.