How devrel-origin works.
The OSS CLI scaffolds a .devrel/ directory in your repo, runs 15 agents against your code and KB, and ships marketing as committed deliverables every week.
v0.2.14 · MIT · self-host forever.
13 May 2026Docs
- 01→
Concepts.
The .devrel/ directory, the 15 agents grouped by pillar (Health, DevRel, Sales), the 7-stage editorial pipeline, and how repo-grounded generation works.
- 02→
Configure.
config.toml product identity + model routing, voice.md / style.md / slop-blocklist.md editorial contract, and BYO LLM keys via .devrel/.env.
- 03→
CLI reference.
All 24 verbs from init to video. Top-level commands and sub-groups with their primary flags and a one-line description each.
- 04→
Operate.
Cron via devrel schedule install, health via devrel doctor, cost via devrel cost, recovery via devrel migrate. Common errors from troubleshooting.md.
- 05→
Examples.
Four real deliverables generated against the PostHog repo: blog post, tutorial, cold-email, battle card. Every claim grounded in the PostHog handbook.
Start here if it's your first time.
// QUICKSTART
Four commands to a marketing PR.
Install → init → read draft → open PR. The fastest path to a first deliverable.
// HOW_IT_WORKSThe five-step workflow.
Repo-grounded generation + the 15 named agents + their weekly cadence.
// MANIFESTOMarketing belongs in the repo.
Seven principles. The why.