phase-recaplisted

# Phase Recap This is a **context-loading skill**. Its job is to make the agent better-informed about the project's current state by reading the right phase logs, internalizing what matters, and using that knowledge in everything the agent says or does next. It runs in two modes: - **Ambient recap** (Mode A) — silent. Loads general project state into working memory at session start or before substantial work. Output to the user is one or two sentences of confirmation. - **Scoped recap** (Mode B) — explicit. The user asks for a recap *at a phase level* ("phase recap Major 5", "recap 5.4"). This prints a **clean report** of the phases preceding the anchor, within that anchor's scope, using the recap template. Terminology (Major / Minor / Patch, capitalized) follows [TERMINOLOGY.md](../../../TERMINOLOGY.md): a **Major** contains Minors, a **Minor** contains Patches. The phase workflow that produces the files this skill reads is owned by `phase-tracker`. ## Where state lives Everything this skill reads is under `development/phase_log/`. In a bundle-shaped project each record opens with front matter carrying `phase`, `phase_status`, `delivery_status`, and `recorded_on` — read those rather than inferring state from prose, and fall back to the body only when the front matter is absent. The agent does **not** read source code, configs, or git history while running this skill — those are the wrong source of truth for "what's the project state". The phase log is the curated recor