Distills a conversation into a self-contained work-item for downstream agents.
npx skills add https://github.com/ai-hero/hero-skills --skill handoff-ai-hero
Please help me install this Agent Skill. Skill: handoff Source: https://github.com/ai-hero/hero-skills/tree/main/skills/handoff Command: npx skills add https://github.com/ai-hero/hero-skills --skill handoff-ai-hero
.plans/ work-item. - Tracker integration: Optionally files the item to GitHub Issues via gh or to Linear via MCP tools, with cross-linking between the tracker and the local store. - Cross-repo handoff: Files work to a different repository's tracker with repo-local references rewritten for the receiving team, plus a local stub tracking the dependency. - Use Case: You spent a session designing a payment-retry migration but ran out of time. Run the handoff command to capture every decision and open question, then let a fresh agent execute it ticket-to-merge later. ## Quick Start Ask the assistant to hand off the current work by running the handoff skill with an optional title, for example to package the migration follow-ups into a work-item.High-intent search queries and answers about installing and using this skill.
Run the handoff skill to distill the current conversation into a self-contained work-item in the .plans/ store. The item captures goals, decisions with reasoning, remaining work, and acceptance criteria so a fresh session can execute it without prior context.
Pass the --issue flag to the handoff skill. It reads the project management setting from HERO.md and runs gh issue create with the work-item as the body, then cross-links the issue URL back into the local item.
Yes, use the --repo OWNER/NAME flag. The skill verifies the target repo, rewrites repo-local references like paths and PR numbers for the receiving team, files an issue there, and keeps a cross-linked stub in your local .plans/ store.
Yes, when HERO.md configures Linear as the tracker, the skill creates issues through the Linear MCP tools instead of the gh CLI. For cross-repo handoffs to Linear teams, you confirm the target team since a repo name alone does not identify it.
The .plans/ store is private and repo-local by design, so it is never committed or pushed. Sharing work happens deliberately through the --issue or --repo flags, which file items to a tracker that teammates can see.
endorphin-aiManage project documentation and work items using markdown files with Git.
SethGammonConverts loose ideas into git-tracked decision maps of typed investigation tickets resolved one per session.
steilerDevDecompose specifications into 2–6 sequential work items with dependencies.
GameDevFoxSend Telegram notifications when local Claude Code sessions finish or need attention.