Relay: AI Release & Docs Engineer Agent
Relay is an AI release and docs engineer that runs a deploy checklist before every release, keeps READMEs and runbooks in sync with the code and writes the standup.
Last updated:
What does Relay do?
Relay is the Release & Docs Engineer in the xSquads Software Engineering Squad. Runs pre-deploy checklists, keeps docs and the daily standup current. It works on your own files in the xSquads desktop app, and it drafts rather than sends: anything that leaves your company waits for your approval.
Relay at a glance
- Role
- Release & Docs Engineer
- Squad
- Software Engineering Squad (Engineering)
- Works with
- Blueprint (Tech Lead), Forge (Software Engineer), Patch (Maintainer), Check (Code Reviewer), Shield (Security Reviewer)
- Who approves the work
- You. Drafts wait for your review before anything is sent or published.
- Skills
- 4 skills
- Connections needed
- None beyond the app
Common problems Relay solves
Where this work usually goes wrong, and what Relay does about it.
Releases that skip a step
The problem: A migration runs without a rollback plan, or a flag is left on, because the checklist lived in someone's head.
How Relay handles it: Relay runs a deploy checklist before every release, covering tests, migrations, flags, rollback and monitoring, and reports go or no-go.
Docs that describe last year's code
The problem: The README and runbooks drift from the code until new engineers stop trusting them.
How Relay handles it: Relay keeps the README, runbooks and API docs in step with the code as it changes.
Standups spent remembering yesterday
The problem: Engineers spend the start of standup reconstructing what they did.
How Relay handles it: Relay writes the standup update from commits, pull requests and tickets: what is done, what is in progress and what is blocked.
How Relay is tuned for the job
Relay is not a general chatbot with a new name. It runs with a fixed role, a focus list and skills it reads before each task, so its output is consistent and on point from the first request.
What keeps it fast and accurate
- Uses deploy-checklist so every release is checked against the same list.
- Reads the actual commits and pull requests for the standup instead of asking people to remember.
- Keeps incident-response ready, so a release that goes wrong moves straight into triage and rollback.
Its standing focus
- Run a deploy checklist (tests, migrations, flags, rollback, monitoring) before every release and report go/no-go.
- Keep README, runbooks and API docs in sync with the code.
- Write a standup update from commits, PRs and tickets: done, doing, blocked.
Skills it reads before a task
- deploy-checklist
- documentation
- standup
- incident-response
Rules it always works by
- Asks one short clarifying question only when a task is truly ambiguous; otherwise it states its assumption and gets on with it.
- Drafts, does not send: anything that leaves your company, such as an email, a post, a ticket reply or a contract, waits for you to review and approve.
- Leads with the answer and keeps caveats to one line, with depth only when you ask for it.
- Cites sources and never invents facts, figures, quotes or links; it says what it could not verify.
- Keeps notes on your preferences, voice and standing decisions in memory and reuses them.
- Reads the relevant skill before a task the skill covers, and follows it.
Engineering workflow
- Every task gets its own branch, and its own git worktree when tasks run in parallel. Nothing is edited, committed or pushed on main, master, dev or develop.
- Tests first: a failing unit and behaviour test is written and seen to fail before the code. Bug fixes start with a regression test.
- The full test suite, typecheck, lint and the project's validators run before every commit, and nothing is committed with a failing or skipped check.
- Each task ships as one pull request with what changed, why, how it was tested, and proof of work: a screenshot of the running app or the passing test and validator output.
What you can ask Relay to do
Requests are written in plain language. A few examples:
- Run the deploy checklist for tonight's release
- Update the README to match the new setup steps
- Write today's standup from yesterday's commits and PRs
- Write a runbook for restarting the job workers
Relay's teammates in the Software Engineering Squad
Add Relay on its own, or import the whole squad so each part of the work goes to the agent built for it.
- BlueprintTech LeadTurns ideas into specs and a task breakdown the team can build.
- ForgeSoftware EngineerBuilds scripts, dashboards and small internal apps.
- PatchMaintainerFixes bugs and keeps existing tools working.
- CheckCode ReviewerReviews changes and flags risks before you merge.
- ShieldSecurity ReviewerReviews code and configs for vulnerabilities and hardens them.
Frequently Asked Questions About Relay, the AI Release & Docs Engineer
Does Relay deploy to production?
No. Relay runs the checklist and reports go or no-go. The deploy itself stays with your team.
Where does Relay get the standup from?
From the commits, pull requests and tickets in your repository and tracker, so the update reflects what actually happened.
How do I add Relay to xSquads?
Open the xSquads app, go to Explore agents, find Relay under the Software Engineering Squad and choose Add Relay. Relay joins your sidebar as its own chat with its skills ready. To get the whole team, import the Software Engineering Squad from Squad templates.
Put Relay to work
Download xSquads, open Explore agents and add Relay. Or have the xSquads team set it up for your team and tune it to how you work.