onboard

## Phase 1: Load Project Context Read CLAUDE.md for project overview and standards. Read the relevant agent definition from `.claude/agents/` if a specific role is specified. --- ## Phase 2: Scan Relevant Area - For programmers: scan `src/` for architecture, patterns, key files - For designers: scan `design/` for existing design documents - For narrative: scan `design/narrative/` for world-building and story docs - For QA: scan `tests/` for existing test coverage - For production: scan `production/` for current sprint and milestone Read recent changes (git log if available) to understand current momentum. --- ## Phase 3: Generate Onboarding Document ```markdown # Onboarding: [Role/Area] ## Project Summary [2-3 sentence summary of what this game is and its current state] ## Your Role [What this role does on this project, key responsibilities, who you report to] ## Project Architecture [Relevant architectural overview for this role] ### Key Directories | Directory | Contents | Your Interaction | |-----------|----------|-----------------| ### Key Files | File | Purpose | Read Priority | |------|---------|--------------| ## Current Standards and Conventions [Summary of conventions relevant to this role from CLAUDE.md and agent definition] ## Current State of Your Area [What has been built, what is in progress, what is planned next] ## Current Sprint Context [What the team is working on now and what is expected of this role] ## Key Dependencies [What other roles/...