From roadmap to reviewable issues.

Run more of the loop from the CLI

Research, review, dependency updates, post-merge changelog capture and learning can now run through ourobuild run --layer N once you configure their executors. Each layer uses the commands, credentials and trusted actors you set; nothing runs or installs on its own.

Chain the whole cycle

run --cycle runs all seven configured stages in order, checks each stage's output before the next one starts, and resumes from the last completed stage.

Review without approving

ourobuild review runs your configured reviewer against the exact pull-request head and posts its findings as a comment. Merge approval stays with your team.

Read the configuration guide

Your first issue preview

The source-checkout quickstart creates a configuration the CLI can load in your project. Add roadmap checkboxes to PRD.md, then use run --layer 2 --dry-run to see proposed issue titles, priorities and labels. The preview makes no GitHub write.

Pick up where you left off

Before a connected Layer 2 run creates issues, Ourobuild reads its labeled issues, including closed ones. It shows links to matching proposals and reports how many it skipped and created. Roadmap items with the same title but different context remain separate work.

Use your team's label

Pass --issue-label to init to use your own label in the preview, issue creation and open and closed issue check. The generated implementation workflow responds to that exact label. If you edit it later, doctor flags a stale trigger and explains how to update it.

Keep the write boundary clear

If the complete issue list cannot be read, the run stops before creating anything. Generated workflows run through the agent and CI you configure; the local preview is one step in that workflow.

Try the local preview