Projects / HandoffCheck

Product → Engineering

HandoffCheck

Clear requirements.
Shared agreement.
A better handoff.

Explore the workflow Read the technical study

00 / The idea

Make the agreement
easy to follow.

HandoffCheck gives product and engineering one place to turn an idea into an agreed implementation brief. Authors capture requirements, resolve questions, and ask the assigned product and engineering leads to approve the same revision. The approved brief carries that agreement into delivery.

For
Product authors, product leads, and engineering leads.
Workflow
Draft → review → clarify → two approvals → implementation brief.
Assistance
Requirement review, wording proposals, reviewer summaries, and QA scenarios.
Delivery
Web workspace and Windows app, with optional Google Workspace and Linear connections.

01 / In the workspace

Four moments.
One connected workflow.

Follow the actual workspace through review, reminders, an approved brief, and team setup.

01Requirement review & summaries

Get everyone working from the same context.

Open a saved request, inspect the assistant's findings alongside the original requirements, and prepare a short summary for the reviewers. Source quotes keep the discussion connected to the exact revision.

  • Inspect requirements and source evidence
  • Review clarification questions
  • Prepare a summary for both leads

02Approval reminders

Keep the next decision moving.

Set a reminder interval and choose whether to email the reviewers from a connected Gmail account. The schedule follows the current approval state and targets the assigned leads who still need to respond.

  • Choose minutes, hours, or days
  • Save a repeat reminder schedule
  • Combine in-app and optional email reminders

03Approved brief & QA assistant

Turn agreement into something the team can use.

Open the approved implementation brief, copy or download its Markdown, then draft QA scenarios from its acceptance criteria. Each scenario presents steps, expected results, and the criterion it came from.

  • Export the approved brief
  • Draft positive, negative, and permission checks
  • Inspect each scenario's source criterion

04Workspace & integration settings

Set up how your team hands work over.

Manage member invitations and reviewer roles, inspect the engineering checklist, and choose which assistant features are enabled. The walkthrough also shows Google Workspace settings and confirmation of a Linear destination.

  • Manage members and reviewer roles
  • Configure checklist and assistant features
  • Choose an integration destination

02 / System architecture

A shared workspace.
Clear responsibilities.

React and TypeScript power the interface. Supabase provides Google authentication, PostgreSQL, private files, and Edge Functions. Gemini supports structured language tasks; database transactions preserve revision and approval consistency.

One workflow across web, desktop, and connected toolsHandoffCheck / System map
The workspaceApplication authorityConnected services
React + Viterequests · review · briefs · settings
Google sign-inSupabase Auth + active membership
ElectronWindows app · system-browser sign-in
Supabase Edge Functionsverified commands · AI adapter · workers
PostgreSQLrevisions · findings · approvals · briefs · jobs
Private Storagerequest-scoped screenshots and PDFs
Geministructured drafting · review · summaries · QA
Google Workspaceconfigured Forms → Sheets → approved Docs
Gmail & Linearauthorized reminders · confirmed handoffs
React and the Windows shell share the hosted workspace. Supabase enforces identity, request access, workflow transactions, and private file storage.
Requirements

Keep the source close.

Findings, summaries, edits, and QA scenarios connect back to saved requirements or acceptance criteria.

Decisions

Agree on a revision.

Both assigned leads approve the same revision and input hash. Subsequent edits create a fresh revision for review.

Access

Share with the participants.

Drafts belong to their author. Submitted requests are available to the author and the currently assigned active leads.

03 / Review & approval

Keep the decision
with its evidence.

Required-field checks and unresolved blocking questions determine readiness. Product and engineering decisions are recorded against the reviewed snapshot, and the final brief is built from the approved fields.

Both leads approve the same revisionHandoffCheck / System map
AuthorReviewHuman decisionHandoff
Feature requestscope · behavior · criteria · selected leads
Review & clarifychecklist + optional AI findings
Two approvalsproduct + engineering · same revision/hash
Approved briefimmutable snapshot · Markdown export
Readiness, access, and approval are checked in application/database logic. Assistant suggestions become requirements only after the author confirms an edit.
A saved change creates a new revision. Prior review and approval records remain in history; the new revision needs its own review and decisions.

04 / Context & assistance

Useful suggestions.
Traceable sources.

Each task receives its own role, constraints, selected guidance, authorized source, example, and output schema. Structured responses are checked for valid evidence before appearing in the workspace.

Give each assistant task the context it needsHandoffCheck / System map
TaskContextModelValidation
Choose a taskdraft · review · edit · summarize · QA
Assemble contextrole · constraints · guidance · source · schema
Gemini responsebounded JSON with source evidence
Validate & showcheck quotes, fields, and criterion indexes
The author checks proposed wording. Assigned reviewers make approval decisions. QA scenarios remain reviewable drafts tied to the agreed criteria.
Drafting, review, edits, summaries, and QA use separate contexts through the same Gemini adapter. The model identifier is supplied by server configuration.

05 / Engineering underneath

A dependable path
between teams.

Shared schemas, participant permissions, durable tasks, and revision checks support the product flow. Integrations carry approved work into the team's existing tools, with explicit configuration and confirmation.