Forgebeta
How to

Write a document

A research memo, a report, a standalone mockup — the same lifecycle as code, with proof that suits the artifact instead of tests that do not.

A bounded deliverable that is not software: a research memo, a written report, a standalone mockup, a visual artifact. Forge calls this Work, and it gets the same treatment code gets.

Ask for it

What you type
Forge research whether we should move the editor off ProseMirror.
I want the alternatives, what each one costs us to migrate to,
and what we lose. Cite sources.

What is different from code

One review dimension switches on that never fires for code, called Quality. It checks the claims against their sources, the reasoning from evidence to conclusion, the omissions that would defeat the purpose you stated, and internal consistency.

What counts as a defect is narrow on purpose:

AdmittedNot admitted
A factual errorA writing voice the reviewer would not have chosen
A consequential conclusion with nothing under itAn interesting topic you did not ask about
An omission that defeats the stated purposeA preference about structure
A violation of the format standard you setLength, unless it hides something

Sources it could not reach get disclosed rather than glossed over.

Mockups

What you type
Forge spec design a settings page for the workspace admin.

You get a single-page visual study built from your own codebase — its components, its tokens, its real content — rather than a generic template. Figma-style frames without a Figma account.

Studies are disposable proposals

Rendering one and looking at it is not acceptance of anything, and Forge will not record it as such.

A mockup that decides a product experience is not Work, though. That belongs inside the product's own spec, because it is making a product decision rather than being the deliverable.

Acceptance

Somebody opens the actual artifact and checks it against its purpose, its sources and its format. For anything visual that means rendering it and inspecting the output, not reading the markup that produced it.

On this page