Command reference

Find the command for your task, then check its flags. Replace angle-bracket values with your own values. All commands accept --help. The reference tracks the pinned CLI registry, including the three hidden compatibility and administration commands.

init

e11 init

Prepare a fresh or cloned checkout. Start here for project identity, the Toolkit pin, price list, profiles, ignore rules, and editor skills. Run again to restore generated files.

Flag	Use
-y, --yes	Take the defaults without asking
--ide <codes>	Comma-separated IDE codes to write skills for (remembered on this machine)
--output-folder <path>	Where planning and stories live, relative to the checkout (default: foundry)
--project-name <name>	The project name in the configuration (default: the directory name)
--from <tarball>	Pin the Toolkit from a local package tarball instead of the registry
-d, --dir <path>	Project directory (default: current working directory)
--no-register	Do not add this project to the dashboard registry
--json	Emit the report as JSON instead of text

doctor

e11 doctor

Check run prerequisites without writing files. Follow fix rows and review rate differences before starting work.

Flag	Use
-d, --dir <path>	Project directory (default: current working directory)
--json	Emit the checks as JSON instead of text

status

e11 status

Read installed modules and versions. Use doctor to check readiness for a run.

This command has no additional flags.

initiative

e11 initiative <action> [subject]

Use new to create an effort, use to select the current effort, open for a separate worktree, list for available efforts, and show for identity and location. Board actions create, import, or show a managed board. Boards lists the initiative’s boards. Import with --legacy is an upgrade path.

Flag	Use
--slug <slug>	new, use, open, show: the initiative, when not given as the subject
--title <text>	new, board create, board import: the title
--initiative <id>	board actions: the initiative (default: the one this checkout points at)
--location <path>	board create, board import: where the board lives, relative to the initiative directory
--stories <ids>	board create: comma-separated story ids, each optionally id=key
--legacy <path>	board import: the legacy status file, relative to the checkout root
--artifact <id>	board show: the board artifact
--operation-key <key>	board create, board import: the idempotency key (default: a fresh one)
-d, --dir <path>	Project directory (default: current working directory)
--json	Emit the result as JSON instead of text

board

e11 board <action> [story] [status]

Use show to read status, set to change one story, add for new entries, create for a new board, and reconcile after a merge changes the file. Each write uses an operation key.

Flag	Use
--initiative <slug|id>	The initiative (default: the one this checkout points at)
--artifact <id>	The board, when the initiative holds more than one
--title <text>	create: the title
--stories <ids>	create, add: comma-separated story ids, each optionally id=key
--location <path>	create: where the board lives, relative to the initiative directory (default: board.yaml)
--operation-key <key>	set, add, create, reconcile: the idempotency key (default: a fresh one)
-d, --dir <path>	Project directory (default: current working directory)
--json	Emit the result as JSON instead of text

run

e11 run <kind> [paths...]

Start from story, stories, series, epic, or manifest. Each source compiles to a sealed plan. Review with --plan-only before starting a worker. An epic is a source for the same engine.

Run sources and acceptance explains normal execution.

Flag	Use
-e, --epic <id>	With epic: the epic to select from the epics file
--initiative <id>	The initiative the work belongs to, when the documents sit under no initiative file
--profile <id>	The trusted execution profile to plan with (default: default)
--model <provider/model>	The priced runtime to try first (default: the first priced one)
--max-cost-usd <usd>	Run ceiling. Default: planned items times one call allowance, plus 25 percent headroom.
--max-cost-usd-per-attempt <usd>	The most one worker call reserves (default: the binding’s token bound at the first runtime’s list rate)
--max-turns <n>	The turn allowance of one worker invocation (default: 400). a worker at its allowance is resumed to finish
--plan-only	Print the sealed plan and start nothing
--no-publish	Plan with publication off: no board entry moves and no document is published
--no-report	Narrate no report when the run settles. the engine’s own brief is the report
-d, --dir <path>	Project directory (default: current working directory)
--json	Emit the result as JSON instead of text

runs

e11 runs <action> [run]

Always supply an action. List, status, and report inspect work. Resume and retry continue work. Approve, reject, and adopt record decisions or manual delivery. Stop parks a run. Cancel ends a run. Land records accepted work on the target, cleanup releases its worktree, and successor seals a fresh plan with policy changes.

Adopt, land, and cleanup explains completion.

Flag	Use
--reason <text>	With stop, cancel, retry and reject: why, recorded with the request
--work-item <id>	With retry, approve, reject, adopt and land: the work item
--by <principal-id>	With approve, reject and adopt: who is answering for the work
--commit <sha>	With land: the commit the reached the target ref (default: the accepted head). With adopt: the commit carrying the work (default: the run branch head)
--merge	With land: fast-forward the checkout onto the accepted commit first. the branch the run came from must be checked out and clean
--change <json>	With successor: the policy change as JSON, applied over the original policy
--raise-ceiling <usd>	With resume: raise the spend ceiling to this amount first, then drive on. a run paused for money continues
--approved-by <principal-id>	With successor and resume --raise-ceiling: who approved the change (default: this machine’s principal)
-d, --dir <path>	Project directory (default: current working directory)
--json	Emit the result as JSON instead of text

dashboard

e11 dashboard

Open the operator page on port 4711. The server binds to loopback and offers commands to copy. Register additional checkouts with project add before serving all projects.

Flag	Use
-p, --port <n>	Pin the port (default: 4711, the port e11 run names)
--no-open	Print the url without opening a browser
--all-projects	Serve every registered project in a read-only view.
--principal <role>	Act as this role for one invocation (observer, planner, ux, engineer). overrides .foundry/principal.yaml
-d, --dir <path>	Project directory (default: current working directory)
--json	Emit {url, port} as JSON instead of text

install

e11 install

The lower-level installer configures modules and tools. Use init for a checkout ready to execute runs. Installer flags remain available for module and custom-content administration.

Flag	Use
-d, --debug	Enable debug output for manifest generation
--directory <path>	Installation directory (default: current directory)
--modules <modules>	Comma-separated list of module IDs to install (e.g., "foundry,bmb")
--tools <tools>	Comma-separated list of tool/IDE IDs to configure (e.g., "claude-code,cursor"). Use "none" to skip tool configuration.
--custom-content <paths>	Comma-separated list of paths to custom modules/agents/workflows
--action <type>	Action type for existing installations: install, update, quick-update, compile-agents, or self-update (when a newer release exists)
--user-name <name>	Name for agents to use (default: system username)
--communication-language <lang>	Language for agent communication (default: English)
--document-output-language <lang>	Language for document output (default: English)
--output-folder <path>	Installer document output path. For run-ready checkouts, choose the publication root with init.
-y, --yes	Accept all defaults and skip prompts where possible
--no-register	Do not add this project to the dashboard registry (~/.e11-foundry/projects.json)

project

e11 project <action> [target]

Register a checkout with add, inspect registrations with list, or remove a registration with remove. Removing a registration changes the dashboard list.

Flag	Use
-n, --name <name>	With add: display name (defaults to the directory name)

agent

e11 agent [agentName] [task...]

Invoke an installed agent through an AI runtime. Use --list to inspect installed agent names and --print to review a prompt. Use run for story execution with run acceptance and accounting.

Flag	Use
-r, --runtime <runtime>	AI runtime: claude | opencode | print | auto (default: auto)
-l, --list	List the agents available in this project and exit
-p, --print	Print the assembled prompt without launching a runtime
-d, --dir <path>	Project directory (default: current working directory)

toolkit

e11 toolkit <verb> [args...]

Skills call these helpers for activation, knowledge techniques, configuration, rosters, rendering, and checks. Verbs include activate, brain, customizable-skills, git-evidence, personas, pick-methods, render, roster, spine-lint, and word-metrics.

Flag	Use
--workspace <dir>	With spine-lint: the folder holding the spine document
-o, --output <file>	Write the result to a file instead of stdout
--project-root <dir>	The project root a verb resolves against (default: current directory)
--skill <dir>	The skill directory a verb resolves against
--skills-root <dir>	With customizable-skills: ssupports this root instead of the installed platform roots
--roster <id>	With roster: resolve this group instead of the default room
--group <id>	With roster: an alias for --roster
--list-groups	With roster: list the groups without resolving any of them
--file <path>	With brain: the technique catalog CSV
--extra <path>	With brain: a JSON overlay of extra techniques, merged into every command
--category <name...>	With brain list and brain random: restrict to these categories
--all	With brain list: dump the whole catalog on purpose
-n <count>	With brain random: how many to draw (default 1)
--json	Emit the result as JSON when supported
--initiative <slug>	With activate: resolve against this initiative instead of the one the checkout points at
--require-initiative	With activate: refuse when the checkout points at no initiative
--range <rev-range>	With git-evidence: the commit range to read, such as main..HEAD
--story <ids>	With git-evidence: the story ids to attribute commits to, comma-separated

pipeline

e11 pipeline [file]

Run a sequence of agent tasks from .foundry/pipeline.yaml. Steps pass documents through files. Use --dry-run to inspect the sequence and --init to create a starter file.

Flag	Use
-r, --runtime <runtime>	Override the runtime for every step: claude | opencode | print | auto
-d, --dir <path>	Project directory (default: current working directory)
--from <step>	Resume from a step (1-based index or agent name)
--continue-on-error	Keep going past a failing step (overrides per-step continueOnError)
--dry-run	Print the resolved plan without running anything
--init	Write a starter pipeline.yaml from the installed agents and exit

export-plugin

e11 export-plugin

Export selected skills as a local plugin bundle for Claude Agent SDK consumers. Supply a dedicated output directory. Review selected modules and skills before exporting.

Flag	Use
--out <dir>	Output directory for the bundle (required)
--modules <ids>	Comma-separated module IDs to source skills from (default: "foundry")
--skills <names>	Comma-separated skill names to include (default: all skills in the modules)
--name <name>	Plugin manifest name (default: "e11-foundry")
--plugin-version <version>	Plugin manifest version (default: the CLI package version)
--description <text>	Plugin manifest description (default: derived)
--no-clean	Do not wipe the output directory before writing

uninstall

e11 uninstall

Remove generated Foundry installation files from a checkout. Preserve your user artifacts and inspect the resulting Git diff.

Flag	Use
-y, --yes	Remove all E11 components without prompting (preserves user artifacts)
--directory <path>	Project directory (default: current directory)

admin

e11 admin <operation>

Hidden administration commands preview destructive operations under Foundry Home. Operations include detach-project, prune-toolkit-cache, delete-operational-state, and delete-artifacts. Apply requires the current preview’s confirmation token. Follow the operations runbook.

Administration and cutover procedures

Flag	Use
--workspace <id>	detach-project, delete-operational-state: the workspace
--machine <id>	prune-toolkit-cache: the machine (default: this one)
--project <id>	delete-artifact: the project the artifact belongs to
--initiative <id>	delete-artifact: the initiative the artifact belongs to
--artifact <id>	delete-artifact: the artifact
--confirm <token>	Apply the preview the printed this confirmation
-d, --dir <path>	Project directory, for the artifact store (default: current working directory)
--json	Emit the preview or the report as JSON

epic

e11 epic <action> [target] [subject]

Hidden compatibility access for the previous engine. Status, events, and runs read history. Plan refuses and points to run. Dashboard forwards to the current dashboard. Writing actions refuse. Compatibility flags below remain in the parser and do not restore retired writing actions.

Legacy engine compatibility

Flag	Use
-e, --epic <number>	Epic number to select from the epics file (plan/run)
-c, --config <path>	Dependency/verification overlay YAML (epic-run.yaml)
-r, --runtime <runtime>	Worker runtime: claude (live workers) | fake (deterministic replay. default) | print (plan-only)
-d, --dir <path>	Project directory (default: current working directory)
--continue	Keep running stories whose ancestors all succeeded after a failure
-s, --story <id>	Story id for retry (grants fresh attempts) or adopt (records work you finished by hand)
--refresh-spec	Legacy parser compatibility. The retired writing action refuses.
--reason <text>	With stop: why, recorded in the run ledger with the request
--worker-timeout-ms <ms>	Legacy parser compatibility. The retired writing action refuses.
--stall-timeout-ms <ms>	Legacy parser compatibility. The retired writing action refuses.
--max-cost-usd <usd>	Legacy parser compatibility. The retired writing action refuses.
--max-cost-usd-per-story <usd>	Legacy parser compatibility. The retired writing action refuses.
-f, --follow	With status/events: keep streaming new events live until the run reaches a terminal state
--files	With status: list each story's commit subjects and every changed file
-p, --port <n>	With dashboard: pin the port (default: 4711)
--no-open	With dashboard: print the url without opening a browser
--all-projects	With dashboard: serve every registered project instead of this checkout (read-only. see e11 project add)
--revision <sha>	Legacy parser compatibility. The retired writing action refuses.
--verify-only	Legacy parser compatibility. The retired writing action refuses.
--principal <role>	Act as this role for one invocation (observer, planner, ux, engineer). overrides .foundry/principal.yaml
--json	Emit machine-readable JSON instead of the text report
--export	Legacy parser compatibility. The retired writing action refuses.
--rebase-onto-files	Legacy parser compatibility. The retired writing action refuses.

migrate

e11 migrate <area> <action> [subject]

Hidden upgrade commands cover identity bootstrap, storage check, apply, adopt, import, cohort install, cohort complete, and toolkit install. Follow the upgrade checklist for one checkout. Cohort commands belong to the coordinated operations runbook.

Upgrade a checkout

Flag	Use
--cutover <id>	The coordinated cutover this command belongs to (required for storage actions)
-d, --dir <path>	Project directory (default: current working directory)
--file <path>	cohort install: the distributed cohort.json
--workspace <id>	storage apply, storage adopt, storage import: the workspace, one at a time
--consumed <dir>	storage cohort complete: the consumed records collected from every machine
--from <tarball>	toolkit install: pin from a local package tarball instead of the registry
--json	Emit machine-readable JSON instead of the text report

Pinned command surface