القائمة
Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | shipyard-handoff |
| description | Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress. |
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 rootImport a spec-kit feature spec into Shipyard, replacing brainstorming. Use when a spec-kit feature directory exists with spec.md.
Use to inspect or manage Shipyard project state under Codex — show status, resume a previous session, cancel/pause in-progress work, or roll back to a checkpoint. Trigger when the user says "shipyard status", "what's the status", "resume", "continue where we left off", "cancel", "pause this", "roll back", or "restore the checkpoint". Codex has no SessionStart hook, so this skill loads state on demand.
Use when running any multi-step Shipyard workflow under Codex — build, audit, plan, ship, review, research, or map. Explains how Shipyard's parallel-agent workflows degrade to inline sequential execution in Codex, and routes intent to the right workflow skill. Trigger when the user says "build the plan", "audit this", "ship it", "review the code", "run the shipyard build", or asks how Shipyard works in Codex.
Use when performing brownfield analysis on an existing codebase under Codex — onboarding to a new project, generating codebase documentation, or understanding legacy code. Trigger when the user says "map this codebase", "help me understand this code", "document this project", "I just inherited this repo", or runs shipyard init on existing code. This is the Codex inline-sequential form of the mapper agent.
Use when conducting domain research, evaluating technology options, investigating ecosystem choices, or gathering knowledge for a development phase under Codex. Trigger when the user says "research X", "what are our options for", "evaluate these libraries", "what's the best approach to", or before planning a phase. This is the Codex inline-sequential form of the researcher agent.
Use when reviewing code under Codex — verifying spec compliance, conducting quality review after a build, or checking that an implementation matches its plan. Trigger when the user says "review this", "review the implementation", "does this match the plan", "check the code quality", or after a Shipyard build completes. This is the Codex inline-sequential form of the reviewer agent.