Project Handoff
Collect everything a new owner needs: repository state from git output, how to run, architecture, progress, blockers, risks, tests and next tasks. The tool checks completeness against published rules and prepares a document for a developer or a HANDOFF.md for an AI agent.
Free, no sign-up
Everything runs in this browser: the document, command and test output are sent nowhere; a request you choose to send carries only the check summary, without the document text. The draft and versions are kept in localStorage.
Who hands over, to whom, and what the project is. The snapshot date is when the git and test output was captured.
When the git commands and tests were run. A snapshot older than the threshold is flagged by rule HO-14.
Rules v1.0, 2026-10-13. The check gives hints with evidence; people decide on the handoff.
How Project Handoff works
Fill in the sections
Project and repository, git snapshot (paste the output of git log --oneline -n 30, git status --short --branch, git branch -vv, git stash list), how to run and environment variables (names only), architecture (you can import a diagram from Architecture Canvas), progress, blockers, risks, test output, environments, access, tasks, decisions, contacts.
Command output parsing
The tool extracts the commit count and latest commit, the current branch and its divergence from upstream, uncommitted files by kind, branches with a gone upstream and stashes; from test output — passed/failed/skipped and failing test names (vitest, jest, pytest, Playwright, go test, JUnit XML).
Completeness check
Published rules HO-01…HO-22 with severity: blocking, high, medium, low. The result is “ready to hand over”, “ready with notes” or “not ready”; each finding has evidence and a link to the section where it is fixed.
The document
For a developer — a readable document with tables. For an AI agent — HANDOFF.md as instructions: context, current state, verification commands first with expected results, explicit “Do not” rules, tasks by priority with acceptance criteria, where to look. Export: Markdown, PDF via print, JSON with re-import.
Check rules
The table is generated from the same code that runs the check — rules v1.0 (2026-10-13). Readiness: any blocking or high finding — “not ready”; only medium and low — “ready with notes”; no findings — “ready to hand over”.
HO-01 No test run evidence
- Severity
- high
- What is checked
- Test output is missing or not recognised.
HO-02 Failing tests
- Severity
- high
- What is checked
- The test output contains failures (failed/errors).
HO-03 Uncommitted changes
- Severity
- high
- What is checked
- git status shows modified, added, deleted or untracked files.
HO-04 Unpushed commits
- Severity
- high
- What is checked
- The current branch is ahead of its upstream (ahead > 0).
HO-05 Branch without upstream
- Severity
- medium
- What is checked
- The current branch has no upstream or it was deleted: commits exist only locally.
HO-06 Stashes present
- Severity
- medium
- What is checked
- git stash list is not empty — stashed changes are easy to lose.
HO-07 Branches with a gone upstream
- Severity
- low
- What is checked
- git branch -vv shows [gone]: the remote branch was deleted, the local one remains.
HO-08 Blocker without an owner
- Severity
- high
- What is checked
- A blocker has no owner.
HO-09 Task without acceptance criteria
- Severity
- medium
- What is checked
- A next task has no acceptance criteria.
HO-10 No run instructions
- Severity
- high
- What is checked
- Neither setup nor run is filled in.
HO-11 Secrets in the document
- Severity
- blocking
- What is checked
- A field contains a value that looks like a key, token, password or connection string.
HO-12 Environment variable values
- Severity
- blocking
- What is checked
- The environment variable list contains values — only names are allowed.
HO-13 Risk without mitigation
- Severity
- medium
- What is checked
- A risk has no mitigation.
HO-14 Snapshot is stale
- Severity
- medium
- What is checked
- The snapshot date is more than N days old (7 by default) relative to today.
HO-15 No snapshot date
- Severity
- low
- What is checked
- git or test output is pasted, but the snapshot date is missing — freshness cannot be judged.
HO-16 Missing repository info
- Severity
- high
- What is checked
- The repository URL or the default branch is missing.
HO-17 No repository snapshot
- Severity
- medium
- What is checked
- Neither git status nor git log is pasted — the code state cannot be verified.
HO-18 No next tasks
- Severity
- medium
- What is checked
- The next-task list is empty.
HO-19 Merge conflicts
- Severity
- high
- What is checked
- git status shows unresolved conflicts (UU, AA etc.).
HO-20 Detached HEAD
- Severity
- medium
- What is checked
- The snapshot is not on a branch: new commits are easy to lose.
HO-21 No summary or goal
- Severity
- medium
- What is checked
- Neither the summary nor the goal is filled in.
HO-22 Branch mismatch
- Severity
- low
- What is checked
- The current branch in the form differs from the one in git status.
The default snapshot freshness threshold is 7 days and can be changed. Secrets are searched in every field; export is blocked while they remain — hide them with one button (values become [REDACTED], environment variables keep names only) or explicitly confirm they are not secrets.
Limitations
- Parsing expects the standard command formats; localised git output or custom test reporters may not be recognised — this shows right under the field.
- The tool does not verify that the pasted output matches the repository and the date: that is up to the person handing over.
- The secret scan catches common key formats and assignments like password=…; finding nothing does not prove there are no secrets.
- Risk score is likelihood × impact on a 1–3 scale; it orders risks, it is not a quantitative model.
- The document lives in one browser; there is no collaboration or access control — share the file.
Privacy
- Everything runs in your browser: the document and command output are not sent to an InterLAB server or third-party services (a request carries only a summary without the document text, see below); there is no AI model inside the tool — published rules do the work.
- The draft and versions are kept only in this browser (localStorage); “Clear all” deletes them.
- Analytics receives only the fact of an export: the format, the recipient (developer or agent) and the readiness level — never the document text.
- The result reaches us only if you send a request yourself and keep the “Attach the result” box ticked — the form shows exactly what will be sent. The summary holds the readiness level, check rules and counts (blockers, risks, tasks, tests) — never commands, environment variables, addresses or access details.
Related tools
All tools · 40
Code reviewer, incl. AI-written codePaste a pull request diff — get findings on security, migrations, tests and architecture with evidence from the code, sorted by severity. The code is never changed.
MVP health check16 questions about code, access, data, tests and releases. Shows what to check first — no “score out of 100”, no sign-up.
Context VaultProject docs, decisions and constraints in one place: source search, staleness control and task-specific context packs for an AI agent or a new developer.
Spec Drift DetectorRequirements ↔ Git/PR changes: a traceability map, likely drift, changes without requirements and requirements without test evidence — with a reviewer workflow.
Agent cost trackerImport API events (CSV/JSONL) → tokens and spend by project, model and task, retries, budgets and alerts. Prices come from your own price list.
Release readinessAn evidence-backed check matrix: CI, migrations, backups, a rollback plan, monitoring, risk exceptions and sign-off → a GO / NO-GO decision.Handing over a project and want nothing lost?
Technical mentorship: we go through the handoff document, the code state and the risks with your team. The first short conversation about the format is free; the cost is set after a brief and an agreed scope.
- The first short conversation is free — we choose the format
- NDA — yours or ours
- Pricing after a brief and an agreed scope