Relay Documentation

Relay turns scattered product context into approved product documents, technical discovery notes, delivery tasks, implementation blueprints, and implementation packs.

The main working surface is Slack. The web UI is used for review, configuration, billing, and delivery visibility.

Who Uses Relay

• Product and engineering leads use Relay to collect context, generate product documents, approve scope, and move work toward delivery.
• Workspace admins configure Slack, GitHub, Linear, billing, teams, provider routing, and delivery handoff settings.
• Engineers use generated Linear issues, blueprint pull requests, implementation packs, and draft GitHub pull requests during delivery.

Core Workflow

1. Create or select an initiative.
2. Add source material from Slack, email, documents, spreadsheets, slides, PDFs, transcripts, or other supported files.
3. Run a quality check.
4. Answer document-readiness questions if Relay asks for more context.
5. Proceed with document generation.
6. Review, export, approve, or reject the generated document.
7. Answer technical discovery questions in Slack after approval.
8. Generate delivery tasks and sync them to Linear.
9. Review Work Packages and implementation blueprints if enabled.
10. Generate implementation packs and draft GitHub pull requests for delivery.

GitHub and Linear are optional until the workflow reaches their stages. Phase 1 remains useful with Slack and the web UI only.

Start Here

• Workflow stages explains how an initiative moves through Relay.
• Slack commands covers the /intake command.
• Document review explains approval and rejection in the UI.
• Source material describes supported inputs and inbound email routing.