sdv-session-start
ALWAYS invoke this skill FIRST at session start, after context reset/compaction, or when user mentions "reset", "new session", "where were we", "what was I working on". Do NOT skip this for specific task requests—orient first, then execute. This is Rule 0.
When & Why to Use This Skill
The sdv-session-start skill is a mandatory orientation protocol designed to synchronize Claude agents with the current state of a development project. It automates the retrieval of critical context by analyzing git branches, reading session journals, and verifying build statuses. By enforcing a 'Rule 0' approach—orient first, execute second—it eliminates context loss during session resets, branch switches, or long breaks, ensuring the agent is always aligned with the user's progress and technical environment.
Use Cases
- Session Initialization: Automatically gather context from git logs and journals when starting a new work day to resume development exactly where it left off.
- Context Recovery: Restore the agent's understanding of the project after a context reset or 'compaction' by following a standardized orientation checklist.
- Branch Switching: Quickly adapt to a new feature or fix branch by identifying relevant journal entries and verifying the current build status automatically.
- Project Onboarding: Use the orientation report to provide a structured summary of recent activity, current blockers, and next steps for better human-agent collaboration.
| name | sdv-session-start |
|---|---|
| description | ALWAYS invoke this skill FIRST at session start, after context reset/compaction, or when user mentions "reset", "new session", "where were we", "what was I working on". Do NOT skip this for specific task requests—orient first, then execute. This is Rule 0. |
| version | 1.1.0 |
SDV Session Orientation
Quick ramp-up at the start of a development session. Gather context from journals, git state, and build status to understand where work left off.
When to Use
- Starting a new development session
- After context compaction/reset
- Resuming work after a break
- Switching branches
- When uncertain about current state
Orientation Checklist
1. Identify Current Branch
git branch --show-current
Use the branch name to find the relevant journal file.
2. Read Branch Journal
# Journal files are named: YYYY-MM-DD_branch-name.md
ls Docs/journals/
Read the most recent journal for the current branch to understand:
- What work has been done
- What's in progress
- Known issues or blockers
- Build status from last session
3. Check Git Status
git status
git log --oneline -5
Understand:
- Uncommitted changes
- Recent commits
- Relationship to main branch
4. Verify Build Status
dotnet build
Confirm the project builds successfully before starting work.
5. Check for Pending Work
Review:
- Journal entries for incomplete tasks
Docs/ROADMAP.mdfor planned featuresDocs/BUGS.mdfor known issues
Orientation Report Template
Generate a brief orientation report:
## Session Orientation
**Branch:** liminalwarmth/feature-name
**Date:** YYYY-MM-DD
**Build Status:** Passing / Failing
### Recent Activity
- [Summary of last journal entry]
- Last commit: [hash] [message]
### Current State
- [What's working]
- [What's in progress]
- [Any blockers]
### Next Steps
1. [Immediate task]
2. [Following task]
### Notes
- [Any context that might be forgotten]
Quick Commands
# Full orientation
git branch --show-current && \
git status --short && \
git log --oneline -3 && \
dotnet build --verbosity quiet
# Find journal for current branch
BRANCH=$(git branch --show-current | sed 's/.*\///') && \
ls Docs/journals/*${BRANCH}*.md 2>/dev/null || echo "No journal found"
Context Recovery
If context was compacted or reset:
- Read CLAUDE.md - Always read the handbook first
- Read branch journal - Understand what was being worked on
- Check git diff - See what changes exist
- Run build - Verify current state compiles
- Ask the user - If unclear, ask for context
Journal Location Convention
Docs/journals/
├── 2025-12-27_random-outfit-names.md
├── 2025-12-26_dresser-sharing.md
├── 2025-12-25_rings-config.md
└── _archive.md (historical entries)
Journals are named with date and branch name for easy lookup.
Branch Naming Convention
Branch names typically follow:
liminalwarmth/feature-namefor featuresliminalwarmth/fix-namefor bug fixesmasterfor main branch
The journal file uses the portion after the last /.