handoff
Use at session end to summarise work for the next person/session — what was done, what's next, blockers. Different from /pause (mid-session freeze) — handoff is end-of-session deliverable.
What this skill does
# handoff End-of-session summary for the next reader (future self, teammate, fresh CC session). ## Method 1. **Span.** What's the timeframe — this session, this week, this sprint? 2. **Aggregate.** - **Done** — concrete deliverables (commits, PRs, doc updates) - **In progress** — active work paused mid-flight (cross-link to `/pause` if applicable) - **Blocked** — items waiting on external (other team, decision, dep) - **Discovered** — context the next reader needs (constraints, gotchas, things that surprised us) - **Recommended next** — top 3 actions for the next reader 3. **Memory anchor.** Capture the handoff itself with `kind: handoff`. Future "what's the status of X" queries hit this. 4. **Format for the audience.** - Self → terse, working memory shorthand OK - Teammate → fuller context, link to specific commits / files - Fresh CC session → essentially a project brief ## Output shape ``` # Handoff: <span> ## Done - ✓ <commit / PR / update> — <commit SHA> - ✓ <...> ## In progress - <task> — paused at <state>; resume with /siftcoder:continue <id> ## Blocked - <task> — blocked on <external thing>; ETA <when known>; owner <if any> ## Discovered (context for the reader) - Constraint: <surfaced> - Gotcha: <warning> - Decision: <made — w/ rationale> ## Recommended next (top 3) 1. <action> — why 2. <action> 3. <action> ## References - Memory: <ids> - Commits: <range> - Related: <other handoffs> ``` ## Rules - **Done is concrete.** Commits, PRs, file paths — not "worked on X". - **Discovered is rich.** This is the section the next reader values most. - **Top 3 next, not top 10.** Decision pressure forced; useful filter. - **Capture to memory.** Future sessions retrieve this automatically. - **Audience-shaped.** A teammate handoff has more linking than a self-handoff. ## Anti-patterns - "Working on the auth refactor" — not concrete enough - Listing every commit without grouping - Skipping "discovered" section (highest-value) - Long preamble before the structured content ## When NOT to use - Mid-session — `/pause` instead - Tiny session — overkill - Active conversation — handoff is end-state ## Subagent dispatch - None — synthesis of conversation + git - Memory MCP for capture and reference lookups - `Bash` for `git log --since=<start>` ## Value over native CC CC will summarise on request. CC won't naturally produce handoff-shape output with done/in-progress/blocked/discovered/recommended structure or audience-targeted detail. The structure IS the value.
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.