fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
3d52f2de85abc9a4e88aceacf4622df8b3440e4a
agentic-dev/.claude/skills/handoff/SKILL.md
Danijel Martinek f77e6ea881 chore(template): clean-slate template snapshot from bb4a0c7 
Curated, product-agnostic snapshot of the post-story-04 tree: demo
content deleted, auth-only reference feature, web-next shell, all gates
green. Product-specific docs, ADRs 027-029, PRDs/epics/archive, editor
library traces, and product naming are curated out; generic template
repairs (coverage provider devDeps, root test:coverage script, live
lint fixes, root-only release-please) are kept. See TEMPLATE.md for
provenance, curation list, and usage.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK
2026-07-12 20:40:54 +02:00

1.9 KiB
Raw Blame History

name, description, argument-hint
name description argument-hint
handoff Compact the current conversation into a handoff document for another agent to pick up. Use when the user wants to transition work to a fresh session, switch worktrees, or hand off to a subagent. What will the next session be used for?

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it to a path produced by mktemp -t handoff-XXXXXX.md (read the file before you write to it).

Suggest the skills the next session should use, if any. In this repo, the common follow-ups are:

  • grill-with-docs — stress-test the plan before coding
  • to-prd — materialize the plan into docs/work/prds/<date>-<slug>.prd.md
  • superpowers:writing-plans — author the implementation plan
  • superpowers:subagent-driven-development — dispatch implementer + reviewer subagents per task

Don't duplicate

Reference these artifacts by path or URL rather than inlining their content:

  • PRDs (docs/work/prds/*.prd.md), epics (docs/work/epics/<epic>/_epic.md), stories (_story.md), tasks (*.task.md)
  • ADRs (docs/decisions/adr-NNN-*.md)
  • AGENTS.md and CLAUDE.md (the next agent loads these automatically)
  • _state.json (orchestrator-derived; the next agent regenerates it from markdown via pnpm work rebuild-state)
  • Commit messages, diffs, PR descriptions — link the SHA / PR number
  • Existing plans under docs/superpowers/plans/

Do capture

  • The active goal in one sentence
  • In-flight branch / worktree and any uncommitted state (e.g. git status summary, dangling commits)
  • Decisions made in conversation that haven't yet landed in a PRD or ADR
  • Blockers and proposed next steps
  • Skills to invoke first in the next session
  • If the user passed arguments, treat them as the next session's focus and tailor the doc accordingly

Keep the document short — it's a baton, not a thesis.