Slack intake
Create initiatives with `/intake`, attach message threads, capture files, and keep status visible without switching tools.
Features
Relay is built for product and engineering teams that need better source control for decisions before tickets and implementation work begin.
Create initiatives with `/intake`, attach message threads, capture files, and keep status visible without switching tools.
Route longer briefs, forwarded customer conversations, and supported attachments into the right initiative.
Review confidence, coverage, conflicts, warnings, thresholds, and relevance before document generation.
Generate structured product documents with problem, goals, stories, scope, constraints, questions, and success criteria.
Ask focused follow-up questions in Slack after document approval, with unresolved items preserved downstream.
Generate delivery tasks, dependencies, estimates, and reusable Relay task IDs that sync to Linear.
Index selected repositories so task generation can account for relevant codebase summaries and repo ownership.
Use GitHub PR review for implementation blueprints, then generate repo-specific implementation packs.
Track generation usage, route providers where configured, and keep cost and token usage visible in billing.
Evidence review
Relay keeps generated sections connected to source material so reviewers can inspect strong signals, inferred assumptions, unresolved conflicts, and missing coverage.
Quality controls
Quality checks help teams avoid turning incomplete Slack threads into delivery work too early. Failed attempts and regenerations remain visible without becoming the billing basis.
Implementation path
Generated tasks can sync to Linear, repository context can come from GitHub, and blueprint PRs provide an engineering review gate before implementation packs are generated.
Connected tools
Primary working surface for intake, quality reports, approvals, discovery, and task triggers.
Delivery task sync with estimates, dependencies, issue reuse, and state reflection.
Repository indexing, blueprint review, validation statuses, and implementation handoff.
Inbound context from emails, documents, PDFs, spreadsheets, slides, and transcripts.