Specs

Specs are longer-form documents that describe features, fixes, or operational changes. They bridge signal from production to actionable engineering work.

Specs list

Open Projects → Specs to browse all specs for the selected application.

Create a spec

1. Click New spec.
2. Add a title and outline the problem, proposed solution, and scope.
3. Save and share with your team.

Agents can draft specs from conversations when you ask them to turn investigation results into a plan.

Spec detail

The spec page supports rich content — headings, lists, and code blocks — so you can capture enough detail for implementation.

Spec lifecycle

Typical flow:

1. Draft — agent or person writes the spec from signal
2. Review — team comments and refines
3. Approved — linked issues are created or updated
4. Shipped — work moves through the board to done

Specs vs. in-app documentation

Use specs for what to build next; use Docs collections for how things work.