@elalfner/relevo

An automatic issue-to-merge workflow where AI agents build and people verify.

English · Español · Documentation

Relevo is Spanish for "relay". The issue goes in, AI agents build and check the work in the cloud, and you step in only to think, to test on a real device and to decide. Every step is a handoff: the agent passes the baton to a person, and that person passes it to a peer.

Status: early development. All the commands below exist. The solo cycle (go, review, ship) has run once on a real repository and a real Android device; the team features (peer review, review reminders and escalation, reviewer selection) are covered by tests only and have not run against a live team yet. See pilot findings.

Install

Relevo is a Claude Code plugin. In a terminal:

claude plugin marketplace add elalfner/relevo --sparse .claude-plugin
claude plugin install relevo@relevo

That installs it for every project of the machine. To install it for one repository only, add --scope project to the second command (shared with the team through .claude/settings.json) or --scope local (only you). Only the plugin is installed (scripts, skills, agents, stack profiles and templates); the documentation is online.

A shortcut, if you prefer one command: npm install -g @elalfner/relevo gives you relevo install, which asks where to install it (the project is preselected; relevo install --scope project skips the question), relevo update and relevo doctor.

npm install -g @elalfner/relevo
relevo install

To use Relevo from Antigravity (the IDE, the App or the CLI), run relevo init: it asks which tools your team uses and installs a plugin rendered for each. Details in Install.

Restart Claude Code in your project and run /relevo:doctor to see what is still missing. What you need and the first steps are in Install.

How it works

The logo is the flow: the issue comes in on the left, AI agents work inside the circle, and the feature goes out on the right. The circle turns black only when a person holds the baton: thinking and reviewing.

	Command	What it does
	/relevo:init	Sets up your repository once: config, labels, branch protection and workflows.
	feature	Not a command, but the reason for the whole flow: the concept of what you want built. Every cycle starts here, and everything below turns it from idea into delivered work.
	/relevo:think	You and the AI explore the idea and settle every decision before any issue exists.
	/relevo:issue	Turns the idea into issues that pass the spec check, or rewrites an issue that is not being built yet.
	/relevo:go	AI agents build the issue and QA checks it, automatically in the cloud, with nobody waiting.
	/relevo:review	You test on a real device while the agent captures and audits the logs.
	/relevo:fix	Fixes what the review found, updating the spec first.
	/relevo:ship	Verifies approval, archives the spec, merges and closes the loop.

Plus /relevo:status (who is waiting on what) and /relevo:doctor (checks your setup). Every command in detail: Commands. A real run, from idea to merged pull request: How it works.

Why Relevo

• Specs first. The agent builds against detailed issues, and QA checks the diff against them.
• Pull, not push. A work-in-progress limit per person keeps the agent from burying the team in unreviewed branches.
• Humans decide. Approving and merging are explicit human acts, enforced by branch protection, never by a prompt alone.
• Every handoff is one message that says what happened, what is expected of you, and which command to run next.

Documentation

• Get started: from nothing to your first merged pull request, step by step.
• Install: what you need and the first steps.
• Upgrading: moving a project to a new version, in the right order.
• How it works: the idea, and a real run from idea to merged pull request.
• Commands: the nine commands, and the skills that think uses.
• Configuration: the relevo.yml file.
• Stacks and platforms: declare your platforms and add your own rules.
• Where go runs: the cloud, your machine or both, and the two credentials.
• Guide: what to do next, and what to do when something goes wrong.
• Security model: what Relevo protects and what it does not.
• All the documentation: reference, how it was built, and the brand.

Acknowledgements

Relevo builds on OpenSpec and mattpocock/skills, both MIT licensed. Their notices are in NOTICE.

License

MIT for the software and the documentation. The Relevo name and logo are not covered by it: see TRADEMARKS.md.