start
Session startup with context recovery. USE WHEN starting session, after /clear, or recovering from autocompact.
What this skill does
# /start - Session Startup & Context Recovery
Gather project context and recover from handoffs automatically.
## Data Source Priority
**1. Pre-loaded (preferred)**: Check for "Pre-loaded Session Status" in the SessionStart hook output (appears in system-reminder tags at conversation start with `additionalContext`). If found, parse the JSON code block and use this data directly—no MCP call needed.
**2. MCP fallback**: If no pre-loaded data exists, call `get_session_status` with appropriate level.
Look for a section like this in the startup system-reminders:
```
# Pre-loaded Session Status
The following session context was gathered at startup...
```json
{
"level": "standard",
"integrations": {...},
"recovery": {...},
"project": {...},
"beads_triage": {...}
}
```
The pre-loaded data has the same structure as the MCP response—format and display it the same way.
## Quick Start (MCP Fallback)
```typescript
// Fresh session - full context
get_session_status({ level: "full" })
// Context recovery mid-session
get_session_status() // defaults to minimal
// Restore specific handoff
get_session_status({ handoff: "h7k2m" })
```
## Output Levels
| Level | Use Case | Sections |
|-------|----------|----------|
| `minimal` | Context recovery | project, harness, beads counts |
| `standard` | Most session starts | + beads_triage, agentmail |
| `full` | Fresh session | + claude_mem references |
## Auto-Recovery
The plugin tracks your work automatically via hooks. If context is lost (autocompact, /clear), recovery options appear:
### Session Marker Detection
If you see a marker like `<!-- session:abc123 -->` in context but lack detailed memory:
1. This means autocompact occurred mid-session
2. Immediately call: `get_session_status({ handoff: "abc123" })`
3. The MCP returns full working context
4. Resume work without asking user - just continue
### Rolling Checkpoint
If no marker but a recent checkpoint exists (< 24h), the response includes:
```json
{
"recovery": {
"available": true,
"id": "abc123",
"age": "2h"
}
}
```
Offer to restore: "Found recent work checkpoint. Resume?"
## Display Format
### Restored Session
```
┌─────────────────────────────────────────────────────────────────┐
│ SESSION RESTORED: {id} │
├─────────────────────────────────────────────────────────────────┤
│ Task: {context.task} │
│ Last active: {age} │
├─────────────────────────────────────────────────────────────────┤
│ RESTORED CONTEXT │
│ • Plan: {plan.path} (cached) │
│ • Files: {files.length} modified │
│ • Decisions: {userDecisions.length} │
│ • Todos: {todos.length} items │
├─────────────────────────────────────────────────────────────────┤
│ FRESH STATE │
│ • Branch: {branch} ({uncommitted} uncommitted) │
│ • Integrations: {detected integrations} │
├─────────────────────────────────────────────────────────────────┤
│ Continuing from: "{nextSteps[0]}" │
└─────────────────────────────────────────────────────────────────┘
```
### Normal Session Start
```
┌─────────────────────────────────────────────────────────────────┐
│ SESSION START │
├─────────────────────────────────────────────────────────────────┤
│ Project: {project.root} │
│ Branch: {branch} ({uncommitted} uncommitted) │
├─────────────────────────────────────────────────────────────────┤
│ Integrations: {list available} │
│ Harness: {if present, show status} │
│ Beads: {open} open | {actionable} actionable │
├─────────────────────────────────────────────────────────────────┤
│ {recommendations based on state} │
└─────────────────────────────────────────────────────────────────┘
```
## Session Tracking
After completing significant work, append a session marker to enable auto-recovery:
```markdown
<!-- session:{handoff_id} -->
```
This marker survives autocompact summarization and enables seamless recovery.
## Integrations
The plugin auto-detects and enhances with:
| Integration | Detection | Enhancement |
|-------------|-----------|-------------|
| **Git** | Always | Branch, uncommitted, recent commits |
| **Beads** | `.beads/` exists | Issue triage, actionable work |
| **Harness** | `.claude-harness/` exists | Features, memory, loop state |
| **Agent Mail** | MCP configured | Inbox status, file reservations |
| **Claude-Mem** | MCP configured | Observation ID references |
## Recommendations Logic
Based on state, recommend next action:
1. **Handoff recovered** → Continue from `nextSteps[0]`
2. **Loop in_progress** (harness) → Resume implementation
3. **Feature failing** (harness) → Fix failing verification
4. **Issue in_progress** (beads) → Continue that issue
5. **Actionable work** (beads) → Show top picks
6. **No tracked work** → Suggest adding work
## Related Commands
- `/handoff` - Create explicit checkpoint for session end
- `/session-context:handoff` - Same as above (full name)
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.