Stats
Actions
Tags
From shipyard
Writes .shipyard/HANDOFF.md with current task, approach, tried actions, remaining steps, and open questions to resume sessions without losing context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/shipyard:shipyard-handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- TOKEN BUDGET: 80 lines / ~240 tokens -->
Capture the current session's progress into .shipyard/HANDOFF.md so the next session can resume immediately with full context. The orchestrator writes the file directly — this is never delegated to a sub-agent.
I'm using the handoff skill to capture session context.
Write .shipyard/HANDOFF.md with exactly these five sections in order:
What was being worked on at handoff time. Be specific: which file, which feature, which plan task.
The strategy or design being followed. Include key decisions already made so the next session doesn't re-litigate them.
What has been attempted and the outcomes — both successes and failures. Include error messages or unexpected behaviors observed.
Concrete next steps not yet done. List as actionable items, ordered by priority.
Unresolved decisions or blockers that need human input or further investigation.
## Current Task
[What was being worked on]
## Approach
[Strategy and key decisions]
## Tried
[What was attempted and results]
## Remaining
[Concrete next steps]
## Open Questions
[Unresolved decisions or blockers]
.shipyard/HANDOFF.md relative to the project rootnpx claudepluginhub lgbarn/shipyard --plugin shipyardCaptures current workflow state into a handoff document so a fresh session can resume exactly where the previous one left off. Useful when context is running low or work needs to continue in a new session.
Captures full session context into a handoff document so a fresh agent can resume work with zero prior context. Write a single actionable sentence for the next agent.
Creates structured handoff documents that capture session state, active goals, and artifact context for seamless continuation. Useful before clearing context or at end of session.