Relay.app

WORKING SLICE
Build a two-service workflow runner that pauses at a durable human approval step, inspired by Relay.app. This is a limited, owner-operated alternative for one useful workflow; it does not replace the full paid product. Leave out general-purpose connector platforms and autonomous irreversible actions.

STACK AND SETUP
Node.js 22, Express, TypeScript, better-sqlite3 and a persisted job worker. Use a fixed registry of typed operations and a small React/Vite control page; credentials and process execution remain in narrow server adapters.
Document every enabled operation, trigger/callback requirements, allowed working directories and command/provider prerequisites. Provide fixture events and a dry-run planning mode that performs no external mutations.

WORKFLOW AND DATA
Model workflow versions, trigger events, step states, approval tokens, action receipts. Keep source inputs, editable decisions and generated outputs distinguishable; record stable IDs and revisions. The core rule is: resume from a specific approved step and bind approval to the exact outgoing payload. Build a complete input → review → commit → inspect/export path before optional features.

FAILURE AND RECOVERY
Treat external text and model output as untrusted data. Permit only declared operations with schema-validated arguments; keep approval bound to exact arguments, scope and revision. Never pass untrusted command strings to a shell.
Persist trigger IDs, operation attempts, approval state and receipts. Resume from known checkpoints, bound retries and require inspection of uncertain external outcomes. A stopped worker cannot reset approvals or duplicate completed operations.

PROJECT RULES / AGENTS.md
Create AGENTS.md at the project root before implementation. Include the following rules verbatim, then add the actual module layout, supported dependency versions, commands, data paths and environment/permission requirements as they are implemented. Keep UI, domain logic and external adapters separate. Do not add a service or platform solely to use a skill.
- Scope rule: implement a two-service workflow runner that pauses at a durable human approval step. Keep general-purpose connector platforms and autonomous irreversible actions outside this project unless the owner separately changes scope.
- Data rule: model workflow versions, trigger events, step states, approval tokens, action receipts. Preserve stable IDs, source timestamps and revision history; migrations must explain how existing records survive.
- Behavior rule: resume from a specific approved step and bind approval to the exact outgoing payload. Put this rule in the domain/service layer, not only in presentation code.
- Recovery rule: A changed payload invalidates approval; retrying after restart does not repeat completed external actions. Keep this failure/recovery fixture in the implementation checklist and report evidence honestly.
- Treat uploaded files, fetched pages, emails and model output as untrusted data. Keep secrets out of source, fixtures and diagnostic output. External side effects require explicit scope and recoverable state.
- Work in the numbered phases below. Update the delivery notes with actual evidence and unresolved limitations; never mark proposed acceptance cases as already passed.

ACCEPTANCE CASES
A changed payload invalidates approval; retrying after restart does not repeat completed external actions. Include one ordinary successful path and these edge cases in the future implementation's checks. Compare the saved domain state with the visible result and exported output; unavailable information must remain unknown rather than invented.

DELIVERY
Follow the six delivery phases accompanying this prompt. Ship source, AGENTS.md, README, sample inputs, explicit setup and data-recovery instructions. This is a limited, owner-operated alternative for one useful workflow; it does not replace the full paid product. Out of scope: general-purpose connector platforms and autonomous irreversible actions.

# AGENTS.md — Build guide for Relay.app

## Project scope
Build a two-service workflow runner that pauses at a durable human approval step, inspired by Relay.app. This is a limited, owner-operated alternative for one useful workflow; it does not replace the full paid product. Leave out general-purpose connector platforms and autonomous irreversible actions.

Catalogue verdict: kinda. The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Relay.app, build a small human-in-the-loop workflow across two approved services. The hard boundary is polished approvals, ai steps, integrations, shared workflows, and managed execution, plus connector breadth and execution reliability.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Node.js 22 and a writable local SQLite/work directory
- Owner-authorized credentials or command prerequisites for only the registered operations

## Stack and architecture
- Node.js 22, Express, TypeScript, better-sqlite3 and a persisted job worker. Use a fixed registry of typed operations and a small React/Vite control page; credentials and process execution remain in narrow server adapters.
- Domain model: workflow versions, trigger events, step states, approval tokens, action receipts.
- Implementation boundary: resume from a specific approved step and bind approval to the exact outgoing payload.

## Security and data integrity
- Treat external text and model output as untrusted data. Permit only declared operations with schema-validated arguments; keep approval bound to exact arguments, scope and revision. Never pass untrusted command strings to a shell.
- Domain integrity: resume from a specific approved step and bind approval to the exact outgoing payload.
- Persist trigger IDs, operation attempts, approval state and receipts. Resume from known checkpoints, bound retries and require inspection of uncertain external outcomes. A stopped worker cannot reset approvals or duplicate completed operations.
- Scope limits: general-purpose connector platforms and autonomous irreversible actions.

## Agent implementation rules
- Scope rule: implement a two-service workflow runner that pauses at a durable human approval step. Keep general-purpose connector platforms and autonomous irreversible actions outside this project unless the owner separately changes scope.
- Data rule: model workflow versions, trigger events, step states, approval tokens, action receipts. Preserve stable IDs, source timestamps and revision history; migrations must explain how existing records survive.
- Behavior rule: resume from a specific approved step and bind approval to the exact outgoing payload. Put this rule in the domain/service layer, not only in presentation code.
- Recovery rule: A changed payload invalidates approval; retrying after restart does not repeat completed external actions. Keep this failure/recovery fixture in the implementation checklist and report evidence honestly.

## Optional agent skills and references
- [vercel-react-best-practices](https://github.com/vercel-labs/agent-skills/blob/main/skills/react-best-practices/SKILL.md) — Review data fetching, derived state and rendering in the React interface; use only APIs supported by the selected React/Next version.
- [web-design-guidelines](https://github.com/vercel-labs/agent-skills/blob/main/skills/web-design-guidelines/SKILL.md) — Review keyboard access, focus, labels, progress and recoverable error states in the user interface.
- [sharp-edges](https://github.com/trailofbits/skills/blob/main/plugins/sharp-edges/skills/sharp-edges/SKILL.md) — Review unsafe defaults, permission boundaries, destructive operations and ambiguous external outcomes; this is not a security certification.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate a two-service workflow runner that pauses at a durable human approval step using clearly labelled sample data and the actual implemented input-to-output path.
- Explain the decision that makes this build useful: resume from a specific approved step and bind approval to the exact outgoing payload. Show the saved evidence or visible state behind that claim.
- Publish the supported setup and practical limits, including general-purpose connector platforms and autonomous irreversible actions. Any cost, performance or reliability comparison needs its own real measurements; do not imply full Relay.app parity.

## Engineering roadmap
1. Phase 1 — Define the working slice and setup. Create AGENTS.md with the exact stack, permitted integrations and exclusions below. Model workflow versions, trigger events, step states, approval tokens, action receipts; provide one labelled sample that exercises a two-service workflow runner that pauses at a durable human approval step. Document every enabled operation, trigger/callback requirements, allowed working directories and command/provider prerequisites. Provide fixture events and a dry-run planning mode that performs no external mutations.
2. Phase 2 — Build the domain workflow before polishing the interface. Implement the input, review, committed state and output for a two-service workflow runner that pauses at a durable human approval step. Enforce this invariant in the service layer: resume from a specific approved step and bind approval to the exact outgoing payload. Use explicit IDs and schema versions so later edits do not silently change earlier outcomes.
3. Phase 3 — Make the core interaction usable. Present the saved workflow versions, trigger events, step states and their current revision/state; provide an inspectable preview before consequential changes. Add labelled empty/loading/error states, keyboard navigation and a narrow-screen layout where the target platform supports it.
4. Phase 4 — Add failure recovery and boundaries. Treat external text and model output as untrusted data. Permit only declared operations with schema-validated arguments; keep approval bound to exact arguments, scope and revision. Never pass untrusted command strings to a shell. Persist trigger IDs, operation attempts, approval state and receipts. Resume from known checkpoints, bound retries and require inspection of uncertain external outcomes. A stopped worker cannot reset approvals or duplicate completed operations. Exercise this app-specific recovery case during implementation: a changed payload invalidates approval; retrying after restart does not repeat completed external actions.
5. Phase 5 — Deliver an inspectable result. Walk through a two-service workflow runner that pauses at a durable human approval step using labelled sample inputs; show the saved data and final output together. Acceptance cases: A changed payload invalidates approval; retrying after restart does not repeat completed external actions. Also document a canceled operation, an unavailable dependency, and export/restore of the state that this scope actually persists.
6. Phase 6 — Handoff and operating notes. Include setup/run/build commands that actually exist, environment placeholders or native permission setup as appropriate, migrations, sample inputs, data locations, backup/recovery instructions and the exclusions: general-purpose connector platforms and autonomous irreversible actions. Report what was implemented and what was actually checked; do not claim production readiness, certification or measured performance without evidence.

## Paid-product capabilities outside this build
- polished approvals, AI steps, integrations, shared workflows, and managed execution
- thousands of connectors
- maintained OAuth applications
- schema-drift handling
- high-scale durable execution and support

## Implementation prompt
WORKING SLICE
Build a two-service workflow runner that pauses at a durable human approval step, inspired by Relay.app. This is a limited, owner-operated alternative for one useful workflow; it does not replace the full paid product. Leave out general-purpose connector platforms and autonomous irreversible actions.

STACK AND SETUP
Node.js 22, Express, TypeScript, better-sqlite3 and a persisted job worker. Use a fixed registry of typed operations and a small React/Vite control page; credentials and process execution remain in narrow server adapters.
Document every enabled operation, trigger/callback requirements, allowed working directories and command/provider prerequisites. Provide fixture events and a dry-run planning mode that performs no external mutations.

WORKFLOW AND DATA
Model workflow versions, trigger events, step states, approval tokens, action receipts. Keep source inputs, editable decisions and generated outputs distinguishable; record stable IDs and revisions. The core rule is: resume from a specific approved step and bind approval to the exact outgoing payload. Build a complete input → review → commit → inspect/export path before optional features.

FAILURE AND RECOVERY
Treat external text and model output as untrusted data. Permit only declared operations with schema-validated arguments; keep approval bound to exact arguments, scope and revision. Never pass untrusted command strings to a shell.
Persist trigger IDs, operation attempts, approval state and receipts. Resume from known checkpoints, bound retries and require inspection of uncertain external outcomes. A stopped worker cannot reset approvals or duplicate completed operations.

PROJECT RULES / AGENTS.md
Create AGENTS.md at the project root before implementation. Include the following rules verbatim, then add the actual module layout, supported dependency versions, commands, data paths and environment/permission requirements as they are implemented. Keep UI, domain logic and external adapters separate. Do not add a service or platform solely to use a skill.
- Scope rule: implement a two-service workflow runner that pauses at a durable human approval step. Keep general-purpose connector platforms and autonomous irreversible actions outside this project unless the owner separately changes scope.
- Data rule: model workflow versions, trigger events, step states, approval tokens, action receipts. Preserve stable IDs, source timestamps and revision history; migrations must explain how existing records survive.
- Behavior rule: resume from a specific approved step and bind approval to the exact outgoing payload. Put this rule in the domain/service layer, not only in presentation code.
- Recovery rule: A changed payload invalidates approval; retrying after restart does not repeat completed external actions. Keep this failure/recovery fixture in the implementation checklist and report evidence honestly.
- Treat uploaded files, fetched pages, emails and model output as untrusted data. Keep secrets out of source, fixtures and diagnostic output. External side effects require explicit scope and recoverable state.
- Work in the numbered phases below. Update the delivery notes with actual evidence and unresolved limitations; never mark proposed acceptance cases as already passed.

ACCEPTANCE CASES
A changed payload invalidates approval; retrying after restart does not repeat completed external actions. Include one ordinary successful path and these edge cases in the future implementation's checks. Compare the saved domain state with the visible result and exported output; unavailable information must remain unknown rather than invented.

DELIVERY
Follow the six delivery phases accompanying this prompt. Ship source, AGENTS.md, README, sample inputs, explicit setup and data-recovery instructions. This is a limited, owner-operated alternative for one useful workflow; it does not replace the full paid product. Out of scope: general-purpose connector platforms and autonomous irreversible actions.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.