agentsclimarketplace

Setup handoff

Skill WillowRyu/agent-handoff/skills/setup-handoff

Strict 3-stage handoff workflow (plan → execute → verify) for coding agents. Disk-backed state lets verify run in a fresh chat.

Install
npx -y skills add WillowRyu/agent-handoff --skill setup-handoff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use once per project before /plan, /execute, /verify. Auto-scans the repo (manifests, agent guidance, doc tree, toolchain) and runs a short interview to write .handoff/config.md. Pass --auto to skip the interview and accept all auto-detected values, falling back to interview only for items that auto-detection cannot resolve. Part of the agent-handoff bundle (4 skills) — install /setup-handoff, /plan, /execute, /verify together.

SKILL.md

2.2 KB, 439 tokens by cl100k_base, as published. Nobody here has run it

Setup Handoff Workflow

Bootstrap the .handoff/ directory by scanning the project and writing config.md — the source of truth that /plan, /execute, /verify read on every invocation.

Modes

ModeAuto-scanInterview
/setup-handoff (default)always4 questions, ~1 min
/setup-handoff --autoalwaysskipped; falls back to asking ONLY for items auto-detection couldn't resolve

Workflow

  1. Detect mode (default vs --auto).
  2. Run auto-scan → see auto-scan.md.
  3. Decide per item: use auto-detected value, or ask the user.
    • Default mode: ask all 4 items, presenting auto-detected values as defaults → see interview.md.
    • --auto mode: use auto-detected values silently. For items where detection failed, fall back to asking just that one (announce the fallback).
  4. Create .handoff/ if missing. Write .handoff/config.md.
  5. Print summary: 
    ✅ Handoff config written to .handoff/config.md
Next step: /plan "<task description>"

Output language

Question [1] of the interview asks the user's response language. Up until that answer, use the conversation's existing language (or en if unclear). The instant question [1] is answered, switch ALL subsequent output (remaining interview prompts, status messages, the written config.md) to the chosen response_language. Code, file paths, command syntax, and identifiers stay in their native language regardless.

Boundaries

  • Allowed: read project files, write/update .handoff/config.md, create .handoff/ directory.
  • Forbidden: modify any file outside .handoff/. Run no build/test/lint commands.

Gates

setup-handoff has no input gate — it's the entry point. Always proceeds.

What ships with it: 2 files

12.4 KB alongside SKILL.md

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.