review-cockpit

1# review-cockpit
2 
3## Purpose
4 
5A single, living **review document** that doubles as the control surface for a session. Instead of scattering a meeting note here, a ticket there, two drafts in chat, everything lands in **one file** you can open in the Obsidian side panel (or Claude side panel) and drive: see progress at a glance, review each item in place, approve or request changes inline, and watch the doc update as the agent works. Mirrors a "co-work" cockpit (Progress / Working folder / Context).
6 
7## When to use
8 
9- Any session with **≥2 things you need to review or approve** (the default for "process X then plan/draft Y, Z").
10- Meeting-processing + pod planning, multi-ticket runs, briefs with several drafts, spec + plan + drafts.
11- NOT for a single trivial deliverable (one file, no approval loop) — a plain file is fine there.
12 
13Pairs with `closed-loop` (verification), `harvest` (learnings), and the V-model checkpoints. This skill governs **how the deliverable is presented and driven**, not the verification pipeline.
14 
15## The one rule
16 
17**One doc per session.** It opens with a cockpit, then one review card per item. Every artifact the session produces is linked from the **Working folder** table (fan-out to sub-files mid-run is fine; the cockpit is the single front door). Never hand the user "see files A, B, C" — hand them the cockpit.
18 
19## Structure
20…