Outbound review workspace

Review researched prospects and draft outreach with a human decision step.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Outbound review workspace

Review researched prospects and draft outreach with a human decision step.

## Deliverable
A draft review queue with explicit approval status, contact provenance, and a sample export.

## Stack and visual direction
- Recommended starting stack: Next.js and TypeScript with a small data model. Build the core workflow with fixtures before connecting external services.
- Swiss grid: Use a visible modular grid, aligned baselines, asymmetric composition and tight typographic hierarchy. Reflow the grid without shrinking essential text. Apply this direction to the interface while keeping data and controls easy to read.

- Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [shadcn/ui Skill](https://ui.shadcn.com/docs/skills) (Skill) — Inspect the project's component registry and assemble accessible UI primitives.
  Project with compatible React and styling configuration. Follow the skill's agent-specific setup. Fallback: Reuse established controls in the project, or start with semantic native controls and test keyboard and error states.
- [Harvey](https://github.com/am-aayush/harvey) (Repository) — Reference the prospect research and outreach drafting workflow with a human review gate.
  Supported coding agent and any chosen integrations. Use fixtures or draft mode for verification.
- [Check If Email Exists](https://github.com/reacherhq/check-if-email-exists) (Repository) — Model email validation with explicit unknown and transient-failure states. Use owned test addresses.
  Remote mail systems and network restrictions can affect verification results.
- [React Hook Form](https://github.com/react-hook-form/react-hook-form) (Repository) — Implement labeled forms with validation, accessible errors and preserved inputs.

## Workflow
1. Build a workspace for permitted prospect records, reviewable evidence, and editable drafts. Use Harvey as a workflow reference and model address verification with safe fixtures and an unknown state.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] A reviewer can edit, approve or reject a draft without sending a message.
- [ ] Unknown or transient email validation remains distinguishable from a verified result.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Verify real actions and persisted data where required. Exercise relevant loading, empty, invalid, pending, failure and success states. Provide a clear recovery path.
- [ ] Use fixtures to verify core flows, including a narrow-screen layout and any applicable permission boundaries.

Recipe resources

Source, setup, and compatibility details.