Build a feature
One item, any size. Set the boundary, approve new intent or strategy when needed, and get an independently reviewed change.
One item of any size: a feature, an improvement, a technical task, a patch. Forge calls this an Issue.
Issue never means small. A single one can earn a full spec, a designer, and three workers running at once, because depth comes from effort, complexity, uncertainty and risk rather than from the word on the ticket.
Ask for it
Forge build the export button on the files page.
CSV and JSON, and anything over 50 MB should stream.
Run through Acceptance, then stop before Ship.Read the plan of attack
Before Forge dispatches anyone or edits anything substantive, it shows you what it picked:
Workflow: Issue
Depth: Full
Control: Guided
Agents: PM, Engineer, Reviewer, QA
Boundary: Acceptance
Sequence: Spec → Plan → Build (including Review) → Acceptance
Gates: Launch approval; Spec approval; Plan approval
Workspace: acme/app, worktree forge/export-buttonEverything in that list is yours to change before you say go. Say make it Quick
or drop QA or stop after Plan and it re-reads with your choices.
Approve new decisions when needed
Once you've accepted Launch, Guided delivery stops if Forge authors a new or materially revised Spec or a consequential Plan. It shows you the exact draft before dependent work. A ready Issue or accepted Plan can satisfy those gates; brief tactical notes for a direct Build don't create another approval stop. Silence, a green test run, and a passing verdict aren't approvals.
After required gates, Forge builds and returns the result at your named boundary.
Name where it stops
The boundary is the difference between a plan and a surprise. Put it in the request:
| You say | You get |
|---|---|
Forge build … | Implementation plus independent review |
Forge build … stop after Plan | A plan, and nothing built |
Forge build … through Acceptance | The above, exercised against the actual outcome; UI work uses a real browser |
Forge build … full auto through Acceptance | The same, with ordinary Launch, Spec, and Plan gates handled within the explicit grant |
Building never authorizes publishing
Ship needs explicit publication authority. Importing a ticket, writing a spec, or drawing a mockup does not authorize implementation either.
If it turns out to be bigger
If the work reveals several outcomes that need coordinating, Forge proposes a project with its evidence and keeps the work already done rather than starting over.