shipyard-handoff
Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress.
What this skill does
<!-- TOKEN BUDGET: 80 lines / ~240 tokens --> # Session Handoff <activation> ## When to Use - User says "handoff", "hand off", "transfer session", "save context", or "I'm done for now" - User is ending a session and wants context preserved for the next session - A long work session is wrapping up and state should be recorded ## Natural Language Triggers - "handoff", "hand off", "transfer session", "save context", "I'm done for now" </activation> ## Overview 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. <instructions> ## The Process Write `.shipyard/HANDOFF.md` with exactly these five sections in order: ### 1. Current Task What was being worked on at handoff time. Be specific: which file, which feature, which plan task. ### 2. Approach The strategy or design being followed. Include key decisions already made so the next session doesn't re-litigate them. ### 3. Tried What has been attempted and the outcomes — both successes and failures. Include error messages or unexpected behaviors observed. ### 4. Remaining Concrete next steps not yet done. List as actionable items, ordered by priority. ### 5. Open Questions Unresolved decisions or blockers that need human input or further investigation. ## File Format ```markdown ## 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] ``` </instructions> <rules> ## Key Principles - **Orchestrator writes the file** — never delegate to a sub-agent; sub-agents frequently fail to write output files - **File path is always** `.shipyard/HANDOFF.md` relative to the project root - **All five sections are required** — do not omit any section, even if the content is "none" - **Be concrete** — vague handoffs are useless; include file paths, line numbers, error text where relevant - **After writing**, confirm to the user: "HANDOFF.md is ready. The next session will automatically pick it up when it starts." </rules>
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.