Run any Skill in Manus with one click

handoff

Stars5

Forks0

UpdatedFebruary 6, 2026 at 20:35

This skill should be used when preparing a handoff checklist for agents and persisting it as a handoff note that can be picked up in a fresh thread.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

marchatton

marchatton/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	handoff
description	This skill should be used when preparing a handoff checklist for agents and persisting it as a handoff note that can be picked up in a fresh thread.

/handoff

Purpose: package the current state so the next agent (or future you) can resume quickly.

Persist the handoff note (always)

Determine repo root.
- Prefer: git rev-parse --show-toplevel
- Fallback: current working directory
Use a git-tracked handoff area so it can be reused later (including via automations):
- If the work is tied to a dossier under docs/04-projects/.../<dossier>/: write to <dossier>/tmp-handoffs/.
- Otherwise (non-dossier or cross-dossier): write to docs/98-tmp/handoffs/.
Create the folder if missing.
Generate filename using the handoff time:
- handoff_YYYY-MM-DD_HH-MM-SS_<3-5 words>.md
- Choose 3–5 words that describe the work or topic.
- Prefer lowercase kebab-case for the words (avoid spaces and special characters).
Write the handoff checklist content into that markdown file.
Echo the saved file path at the top of the handoff output.

Handoff checklist content (write in this order)

Scope/status: what you were doing, what’s done, what’s pending, and any blockers.
Working tree: git status -sb summary and whether there are local commits not pushed.
Branch/PR: current branch, relevant PR number/URL, CI status if known.
Running processes: list tmux sessions/panes and how to attach:
- Example: tmux attach -t codex-shell or tmux capture-pane -p -J -t codex-shell:0.0 -S -200
- Note dev servers, tests, debuggers, background scripts.
Tests/checks: which commands were run, results, and what still needs to run.
Next steps: ordered bullets the next agent should do first.
Risks/gotchas: any flaky tests, credentials, feature flags, or brittle areas.

Output format

Start with: “Saved handoff: ”
Then a concise bullet list (copy/paste friendly).
Include copy/paste tmux commands for any live sessions.

Notes

Prefer writing the note even if the session continues. A fresh thread can be started at any time without losing state.
If file write is not possible, print the handoff checklist in chat and ask the user to save it into the git-tracked handoff area.

More from this repository

same repository

precoil-emt

marchatton/agent-skills

Use this skill when the user wants to test a business idea, strategy, or initiative against real-world risk. Triggers include: 'test my idea', 'what are the riskiest assumptions', 'help me validate this', 'run EMT on this', 'extract assumptions', 'assumption mapping', 'what could go wrong with this plan', 'pressure test this', 'validate this plan', 'what could go wrong with this strategy', 'identify hidden risk in this idea', or any request to pressure-test a business decision before committing resources. Runs a guided Extract → Map → Test system based on David J. Bland's Precoil methodology.

2026-03-105

validate-evaluator

marchatton/agent-skills

Calibrate an LLM judge against human labels using data splits, TPR/TNR, and bias correction. Use after writing a judge prompt (write-judge-prompt) when you need to verify alignment before trusting its outputs. Do NOT use for code-based evaluators (those are deterministic; test with standard unit tests).

2026-03-105

visual-explainer

marchatton/agent-skills

Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.

2026-03-025

breadboarding

marchatton/agent-skills

This skill should be used when shaping a software change and needing to breadboard the solution at the right level of abstraction (places, affordances, connections), including mapping an existing system via UI + code affordances, producing a wiring diagram, a parts/BOM plan, a fit check, and (when relevant) an extract-vs-duplicate analysis.

2026-02-115

ask-questions-if-underspecified

marchatton/agent-skills

Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.

2026-02-105

demo-runbook

marchatton/agent-skills

This skill should be used when a user needs a demo package that starts with a live demo (not slides) and produces both a demo script and a navigable single-file HTML runbook, including caveats, respectful competitive comparison, and LLM architecture details (RAG, evals, observability).

2026-02-085

/handoff

Purpose: package the current state so the next agent (or future you) can resume quickly.

Persist the handoff note (always)

Determine repo root.

Prefer: git rev-parse --show-toplevel
Fallback: current working directory

Use a git-tracked handoff area so it can be reused later (including via automations):

If the work is tied to a dossier under docs/04-projects/.../<dossier>/: write to <dossier>/tmp-handoffs/.
Otherwise (non-dossier or cross-dossier): write to docs/98-tmp/handoffs/.

Create the folder if missing.

Generate filename using the handoff time:

handoff_YYYY-MM-DD_HH-MM-SS_<3-5 words>.md
Choose 3–5 words that describe the work or topic.
Prefer lowercase kebab-case for the words (avoid spaces and special characters).

Write the handoff checklist content into that markdown file.

Echo the saved file path at the top of the handoff output.

Handoff checklist content (write in this order)

Scope/status: what you were doing, what’s done, what’s pending, and any blockers.

Working tree: git status -sb summary and whether there are local commits not pushed.

Branch/PR: current branch, relevant PR number/URL, CI status if known.

Running processes: list tmux sessions/panes and how to attach:

Example: tmux attach -t codex-shell or tmux capture-pane -p -J -t codex-shell:0.0 -S -200
Note dev servers, tests, debuggers, background scripts.

Tests/checks: which commands were run, results, and what still needs to run.

Next steps: ordered bullets the next agent should do first.

Risks/gotchas: any flaky tests, credentials, feature flags, or brittle areas.

Output format

Start with: “Saved handoff: ”

Then a concise bullet list (copy/paste friendly).

Include copy/paste tmux commands for any live sessions.

Notes

Prefer writing the note even if the session continues. A fresh thread can be started at any time without losing state.

If file write is not possible, print the handoff checklist in chat and ask the user to save it into the git-tracked handoff area.