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. The documented source-checkout dry run currently stops at a generated-config import; issue preview needs a resolved target package.
Runs today: file scaffolding and setup checks. PRD issue preview or creation needs a loadable target config; the documented quick start does not install its ourobuild import. The other stages are templates for external execution.
signal → ticket → implement → review → merge → changelog → learn ↺
Seven stages in the proposed loop.
Ourobuild generates starter files for agent workflows. The CLI runs PRD-to-issue decomposition locally; the other stages depend on external agents and CI.
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. With a loadable target config, run --layer 2 processes the PRD; 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
Condensed illustration of an observed disposable source-checkout run; command paths and diagnostic lines are paraphrased. The dry run stopped at config loading; no GitHub issue or external agent was invoked.
start with a scaffold
Generate starter files from a source checkout.
Install dependencies, select an engine, and run init in the target project.
Review the generated files and configure external execution before relying on them. In the current source-checkout quick start, the generated config imports ourobuild from the target project; run and doctor cannot validate that config until the package is available there.
bun /path/to/ourobuild/packages/cli/src/index.ts init --engine codex