# Relay 80 100 Workflow

Use when writing agent-relay workflows that must fully validate features end-to-end...

- Repository: https://github.com/AgentWorkforce/relay (1088 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add AgentWorkforce/relay --skill relay-80-100-workflow -g -a claude-code -y`
Codex: `npx skills add AgentWorkforce/relay --skill relay-80-100-workflow -g -a codex -y`
Cursor: `npx skills add AgentWorkforce/relay --skill relay-80-100-workflow -g -a cursor -y`
Gemini CLI: `npx skills add AgentWorkforce/relay --skill relay-80-100-workflow -g -a gemini-cli -y`

## Description

Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, review-depth fresh-eyes review/fix loops with test hardening, PGlite for in-memory Postgres testing, mock sandbox patterns, test-fix-rerun loops, verify gates after every edit, and the full lifecycle from implementation through passing tests to commit.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

### Overview

Most agent workflows get features to ~80%: code written, types check, maybe a build passes. This skill covers the **80-to-100 gap**, making workflows that fully validate features end-to-end before committing. The goal: every feature merged via these workflows is **tested, verified, and known-working**, not just "it compiles."

### When to Use

- Writing workflows where the deliverable must be **production-ready**, not just code-complete
- Features that touch databases, APIs, or infrastructure that can be tested locally
- Any workflow where "it compiles" is not sufficient proof of correctness
- When you want confidence that the commit actually works before deploying

### Core Principle: Test In The Workflow

#### The key insight: **run tests as deterministic steps inside the workflow itself**. Don't just write test files, execute them, verify they pass, fix failures, and re-run. The workflow doesn't commit until tests are green.

```
implement → write tests → run tests → fix failures → re-run → build check → regression check → commit
```

### Repair Before Failure

An 80-to-100 workflow should not stop merely because a test, typecheck, lint, schema, or E2E gate turns red. That red output is work for the agent team. Capture it, hand it to a repair owner, fix it, and rerun. Workflow-owned validation gates should never terminate the run with `FAILED`. If the team exhausts its repair budget or hits an external blocker such as missing credentials, wrong repository, or unsafe dirty worktree, write a `BLOCKED_NO_COMMIT` artifact and end without committing or opening a PR instead of crashing the workflow.

Use this shape for every meaningful gate:

The rest: https://github.com/AgentWorkforce/relay/blob/HEAD/.agents/skills/relay-80-100-workflow/SKILL.md