session:start

Start a session with type-appropriate context. Load orientation, not information.

Session Types

Type	Purpose	Context
plan	Design work	overview, constitution, state
build	Implement	state, conventions, feature files
review	Code review	conventions, git history
fix	Debug	state, recent sessions
document	Update docs	overview, constitution

Instructions

1. Determine Type

If type not provided or invalid, ask:

Session type? [plan/build/review/fix/document]

2. Verify Structure

ls -d .project 2>/dev/null

If .project/ does NOT exist:

No session structure found.

Run /session:init to:
- Analyze your codebase (detects stack, framework, conventions)
- Create .project/ with pre-filled templates
- Set up .context/ for session memory
- Initialize beads for task tracking

Then return here with /session:start {type}

Stop here - do not continue without structure.

3. Load Type-Specific Context

Read the appropriate reference file and follow its instructions:

• plan → Read references/plan.md
• build → Read references/build.md
• review → Read references/review.md
• fix → Read references/fix.md
• document → Read references/document.md

4. Create Session File

ID format: {YYYY-MM-DD}-{type}-{3-random-chars}

Create .context/sessions/{id}.md:

# Session {date} ({type})

Goal: {user's goal}

Context loaded:
- {files loaded}

Progress:
- [ ] {goal as task}

5. Confirm and Begin

{TYPE} session started.
Focus: {from state.md if exists}
Session: .context/sessions/{id}.md

What are we working on?

Progressive Disclosure Principle

Load ORIENTATION, not INFORMATION:

• Show file paths, not file contents (Claude reads when needed)
• Show task IDs, not full task details (use bd show when needed)
• Extract key sections from state.md, not the whole file

If beads is active, bd prime already loaded command reference. Don't duplicate.