start-sessionlisted

# Start Session A portable orientation skill. Reads whatever context the project provides, surfaces what matters, recommends the first task, and **waits for the operator's decision before any code work begins**. ## When to use Invoke at the start of any coding session, especially when: - Returning to a project after >1 day away - Picking up a multi-slot feature wave mid-stream - Operating across multiple repos and need a fast re-orientation Skip when: - The user has already stated a precise task in the same turn - The session is a single-file edit or hotfix with clear scope ## Procedure Run these steps in order. **Use parallel tool calls wherever the reads are independent** (most of them are). ### 1. Discovery — what does this project have? Check for each of the following. Skip any that are absent; don't fail the skill on missing files. | Item | Where to look (in order) | What it gives you | |---|---|---| | **Project rules** | `CLAUDE.md` (root) → `.claude/CLAUDE.md` → `README.md` | Permanent constraints, coding rules, architecture pointers | | **Auto-memory** | `~/.claude/projects/<project-key>/memory/MEMORY.md` (Claude Code auto-loads) → `.claude/MEMORY.md` → `MEMORY.md` | Cross-session memory, banners, "RESUME HERE" pointers | | **Recurring tasks** | `docs/QUALITY_CALENDAR.md` → `.claude/QUALITY_CALENDAR.md` → `QUALITY_CALENDAR.md` | What recurring work is overdue | | **Active plan** | `docs/dev-log/weekly-plan-*.md` → `.claude/plans/weekly-plan-*.md` → `docs/PLAN