The opinionated end-to-end harness for builders

A single workplace for you and your team of agents where you research, plan, spec, build and test. Never losing context and never drifting from spec.

Get started See how it works

Pricing page launch ▾

Edit planPR in 2mPauseStop

waiting on your call at ship · 6m in

three-tier pricing page as a draft PR behind your sign-off

full SDLC · over the recommended build loop - public pricing is a spec-and-verify launch, not a patch

Product Spec · Pricing one-pagerDesign Spec · pricing-pageTechnical Spec

4m25m1h 12m1h 31m

intake✓

launch ask

page only · 4m

plan✓

21m

researchnot activated · spec answers why

pricing one-pager

3 tiers · guardrails · 9m

build✓

47m

Eapi + modelsEng · Api

+612 -180 · 12 files · 33m

Dui + wiringDes · UI

+592 -208 · 19 files · 41m

target page

1 frame · no new endpoints · 9m

verify✓

19m

browser sweep

31 green · 2 flaky · 8m

preview deploy

preview up · 11m

ship⚠︎

draft PR #289

changes + copy read

3 of 3 read4 nits filed · 6m

How Bright ships

Agents do the work. You make the calls.

Every task runs the same five steps: intake, plan, build, verify, ship. Each one ends with something you can check, a spec, a decision, a passing build, a cold review, a draft PR, and a stop where nothing moves until you say so.

1Intake: a request becomes a spec.Say what you want in plain language. Bright writes the spec, what's in, what's out, and what counts as done, and hands it to an engineer.

The stage · what happens at each step

Bright — Session · Pricing one-pagerSpec locked · 2m ago

You · 14:02

Put the three-tier pricing page live behind my sign-off.

Bright · 14:03

Three-tier pricing page

Spec · locked

What ships: Public pricing page with three tiers, copy and tier data wired to the CMS.
What’s out: No new endpoints, no billing changes.
Done means: 31 tests green · preview up · 0 blocking findings · draft PR behind your merge.

Dispatched · Engineerspec and context attached

1 · Intake. The spec Bright wrote from a one-line request, locked before any work starts.

2Plan: your call before a line of code.Where the work could go two ways, Bright lays out the options, recommendation first. Nothing is built until you pick.

The stage · what happens at each step

Bright — Session · Pricing one-pagerWaiting on your call

BBright — needs your callDecision 1 of 3

Scale tier: show a price, or “Talk to us”?

Show the pricematches the pricing one-pager you wrote last weekRecommended

“Talk to us” instead of a price — copy change only

Price plus a “Talk to us” link under the card

Hide the Scale card until the sales page exists

Paused until you pick. Nothing moves until you do.

2 · Plan. A decision card: the options, a recommendation, and a pause until you choose.

3Build: proof while it runs.A manager routes work to specialists building in parallel on their own machines. Tests and the build run in the open as they go.

The stage · what happens at each step

Bright — Session · Pricing one-pagerBuild · live · 5 agents

Manager

Bright

Holds the frame. Routes the work. No new endpoints.

Active

Eng · APItier data wired to the CMSDone

Eng · UIlayout + copy at 320 / 768 / 1440Done

Designertier card visual passDone

PMcopy vs one-pagerSigned off

Tests31 passed · 2 flaky

BuildSucceeded · 41m

3 · Build. The manager routing work to specialists, with tests and the build passing.

4Verify: a second agent reads it cold.A reviewer that shared nothing with the builder checks the diff against the spec. Blocking findings go back to build; nits get fixed.

The stage · what happens at each step

Bright — Session · Pricing one-pagerVerify · verdict in

RReviewer agent · read cold

Ship it.

Read against the spec, with nothing shared from the build.

Matches the spec
Copy matches the CMS
No new endpoints
1 nit · wording aligned in the draft

0 blocking findingsReady for your eyes

4 · Verify. The reviewer's verdict, filed before you ever see the pull request.

5Ship: it stops at the door.The run ends with a draft PR carrying the spec, the decisions, the tests, and the review. Bright doesn't merge or deploy. You do.

The stage · what happens at each step

GitHub — acme/web · PR #289Opened by Bright

Draft

Three-tier pricing page behind sign-off

bright/pricing-page → main · 19 files

Spec locked
Decision logged · Scale price, your call
Reviewed cold · 0 blocking findings
Tests · 31 green · 2 flaky quarantined

Merge pull requestYour callBright stops here.

5 · Ship. The draft PR waiting on your merge, receipts attached.

The stage · what happens at each step

Bright — Session · Pricing one-pagerSpec locked · 2m ago

You · 14:02

Put the three-tier pricing page live behind my sign-off.

Bright · 14:03

Three-tier pricing page

Spec · locked

What ships: Public pricing page with three tiers, copy and tier data wired to the CMS.
What’s out: No new endpoints, no billing changes.
Done means: 31 tests green · preview up · 0 blocking findings · draft PR behind your merge.

Dispatched · Engineerspec and context attached

Bright — Session · Pricing one-pagerWaiting on your call

BBright — needs your callDecision 1 of 3

Scale tier: show a price, or “Talk to us”?

Show the pricematches the pricing one-pager you wrote last weekRecommended

“Talk to us” instead of a price — copy change only

Price plus a “Talk to us” link under the card

Hide the Scale card until the sales page exists

Paused until you pick. Nothing moves until you do.

1 · Intake. The spec Bright wrote from a one-line request, locked before any work starts.

Hover a step (tap on touch) to swap the stage.

Open source · spec to PR

Give Forge an approved spec. Come back to a verified PR.

The loop above handles one task. Type /forge when the job is bigger than that, and Forge takes the whole approved spec instead of a stack of tickets. You approve the plan, then it coordinates the build, an independent review, and verification, and only comes back when it needs a decision.

In BrightBuilt in

Built in. Type /forge in any session, nothing to install.

Anywhere else

MIT licensed. Set it up once, same process in Claude Code, Cursor, or Codex.

Explore Forge on GitHub

Each /forge run leaves readable records

spec/: Intake
decisions.md: Plan
build/: Build
verify/: Verify
ship.md: Ship

Roles it assigns

PMDesignerEngineerReviewerQA

Features

Ten components of a disciplined software factory.

Everything a coding agent needs to ship on its own: a team of specialists, isolated machines, memory that carries between runs, and gates that stop for you.

Click any tile to see the full feature.