Generate a next-agent continuation prompt with task card path.
npx skills add https://github.com/davidlee/spec-driver --skill next-davidlee
Please help me install this Agent Skill. Skill: next Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/next Command: npx skills add https://github.com/davidlee/spec-driver --skill next-davidlee
It solves the friction of handing off work between agents by producing a concise, task-aware prompt for what to do next.
Use the next skill to print the continuation prompt for your agent, then send it as the next-agent message with the current task card path included.
High-intent search queries and answers about installing and using this skill.
To write a continuation prompt for agent handoff, generate a concise next-step instruction that references the current task card path to anchor continuity and direct the next agent.
Spec-driven development agent handoff is the process of transferring documented work to a fresh context by printing a ready-to-send continuation prompt referencing the current task card path.
To ensure implementation readiness, prompt the next agent to read specific artifacts and explicitly identify unresolved assumptions or design questions before declaring readiness to start the implementation.
Yes, you can use a task card path for agent handovers by instructing the next agent to use the path as the anchor for continuity, ensuring clean context transfer without losing prior work.
You need to generate a continuation prompt when prior work is already documented and ordered, and you request continuing with fresh context to avoid friction between agents.
jellydnResume work from saved handoff sessions in .claude/handoffs/.
HexSleevesCompress a conversation into a handoff document for another agent.
tbdavid2019Implement OpenSpec change tasks and synchronize progress across task artifacts.
SjdjdiejdrirhdkjejDetect, create, and generate context for git worktrees via shell commands.
