MCP servers
.mcp.json
GitHub remote MCP, SearXNG / search, Playwright — surfaced to whatever engine uses these files after setup.
source-first workflow scaffolding
Starter workflows for your repo.
Ourobuild scaffolds agent workflow files, MCP settings and skills into an existing repository. Add roadmap items to a PRD, then preview proposed GitHub issues locally before connecting an account.
Start with a local preview: scaffold the files, see proposed issues from your PRD, then connect GitHub when you choose to create them. Later stages run through the agent and CI you configure.
signal → ticket → implement → review → merge → changelog → learn ↺
A path from signal to shipped change.
Use this map to shape your workflow. Ourobuild prepares the files and previews issues from your PRD; your configured agent and CI carry out later stages.
A scaffolder, not a runtime.
Ourobuild doesn't embed an LLM SDK or run a heavy local orchestrator. It generates provider-neutral agentic artifacts — and the engine you pick can use them inside CI or your own agent harness after setup.
There is no default engine. Config validation fails until you choose one. Claude-specific outputs are layered on only as an adapter when you pick Claude.
One init. Starter files for your project.
Review, configure and execute the generated files with your chosen engine.
Agent Skills
SKILL.md
Cross-agent procedures — implement-issue, self-heal-ci,
and templates for adding more skills.
Agentic workflows
github/gh-aw
GitHub Agentic Workflow templates describe stages for CI. A
claude-code-action adapter layers on for Claude.
Drive it from the terminal.
init scaffolds. run --layer 2 --dry-run previews proposed issues from PRD roadmap items; other layers print guidance. doctor
runs nine setup checks. status shows configured layers and
budget settings.
- init scaffold the agentic setup
- run --layer 2 decompose the PRD into issues
- doctor nine setup checks, non-zero on failure
- status configured layers + budget settings
Example PRD preview: one proposed issue, no GitHub write. The issue title is fictional; doctor shows that GitHub credentials are still needed for connected work.
start with a scaffold
See your first issue preview.
Copy these commands to create a disposable Git project, scaffold with Codex, and preview one PRD issue locally. Review the generated files before using Ourobuild in your own repository. No GitHub credentials or write are needed.
local preview · no GitHub write
(
set -e
demo_dir="$(mktemp -d)"
git clone https://github.com/aylith-labs/ourobuild.git "$demo_dir/ourobuild"
(cd "$demo_dir/ourobuild" && bun install --frozen-lockfile)
mkdir "$demo_dir/project" && cd "$demo_dir/project"
git init
printf '# Demo\n\n## Roadmap\n\n- [ ] Draft a release note\n' > PRD.md
bun "$demo_dir/ourobuild/packages/cli/src/index.ts" init --engine codex --search custom
bun "$demo_dir/ourobuild/packages/cli/src/index.ts" run --layer 2 --dry-run
)