handoff
Use when the user needs to compact the current conversation into a document for another agent to continue.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- handoff
- triggers
- [ "user" ]
- description
- Use when the user needs to compact the current conversation into a document for another agent to continue.
- argument-hint
- What will the next session be used for?
03 SKILL.md 正文
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
Use this structure (adapted from the devin acp summarizer schema, eval #455):
## Overview
<2-3 sentences: what was being done and the outcome so far>
## Key Details & Breadcrumbs
- <file path>: <what it contains / what changed, with line refs where useful>
- <command or artifact>: <result worth re-checking>
## Current State
<where the work stands right now: pending items, blockers, next step>
## Suggested skills
- <skills the next agent should invoke>
Breadcrumbs are the contract: every file or artifact the next agent needs appears as a path it can re-read, not a retelling of its contents.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
Cross-skill: If the handoff captures a decision, convention, or gotcha worth remembering across sessions, also invoke memory-management with the user's approval.
Cross-skill: Inside adaptive-agenda-calendar-routine-engine, this document is the artifact the block-transition handoff rite requires between HH:MM-HH:MM blocks.
04 同仓库更多 Skills
montador-de-ideias
Use when assembling, expanding, or elevating a raw project idea or initial prompt into an ultra-detailed, first-principles dossier and compiled master prompt with journalistic OSINT market research, Tech Lead and Staff Architect justifications, atomic and modular hardening/optimization, and high-impact contact surfaces.
git-github-adaptive-engineering
Use when any task touches git history, GitHub issues/PRs/releases/CI, repo governance, or branch and merge decisions. Runs the Fase Zero situational-awareness battery, picks one of five delivery flows via the adaptive decision engine, and enforces commit/PR information-density standards. Orchestrates the gh, git-workflows, github-actions, pr, and debug/finish skills.
adaptive-agenda-calendar-routine-engine
Use when planning or executing work across hours, days, weeks, or sprints. Turns the calendar into a strict time-blocked agenda (HH:MM-HH:MM blocks carrying a routine profile, expected inputs, and a handoff output artifact), runs the 5-stage cognitive flow (Radar and Hunt -> Triage plus Steve Jobs conception -> workbench manifest -> >=32-cycle loop -> Close plus Open-Minded Scrum), and unfolds macro calendar milestones into micro agenda blocks through extensions/gcal/wrapper.py.
demo
Use when demonstrating a skill in a fixture project.
duplicate-skill
Use when testing duplicate skill name detection.
duplicate-skill
Use when testing duplicate skill name detection.