Get started
Pick a path — create a project from an idea, or build specs from an existing codebase.
OriginAI is in public beta on personal accounts. Free includes the full loop: generate, publish, connect a coding agent.
There are two common ways to begin. Which one you pick depends on where the product lives today. Both end in the same place: structured specs you can refine, publish as a release, and hand off.
Releases
↑ ↓
Requirement ──► Spec ──► Coding Agent ──► PR ──► Feature
↑ ↖ ↓ ↑ ↓
│ Change request └── GitHub App
│
┌─ new product (in-app brief)
├─ existing codebase (CLI create-project)
├─ feature iteration (edit → publish)
└─ own-agent change requestGitHub originai / spec-review is a check, not a merge gate. See What is OriginAI?.
Start from an idea
Use this when you don't have a codebase yet, or you want OriginAI to draft specs from a product description. You describe what you're building, review the draft, refine it in the workbench, and publish when it's ready. Not sure what to write? The guide has examples that prefill the home page composer.
→ Create a project on OriginAI
Start from a codebase
Use this when the product already lives in code, but you don't have a shared, readable product definition. You connect a coding agent to the repository, have it read the code, and let it write specs into OriginAI — then you confirm, edit, and publish.
→ Create product specs from a codebase
After you have specs
Once specs are written and published, other people and tools need the same version — not a scrolling chat. OriginAI lets you hand off a specific, frozen release to a teammate or a coding agent.
→ Share specs with your team or coding agent
After an agent updates the spec
Once a release exists, coding agents don't write the workspace directly. They stage a change request you apply or dismiss, then you publish again.