Interview
Interview — constitutional-context peer conversation
What It Does
Interview reads your constitutional files — TELOS, identity, projects, system prompt, architecture — plus the CURRENT_STATE and IDEAL_STATE dimension files, checks their freshness, and confronts stale claims with observed data: Oura sleep/HRV/RHR, Conduit creation-vs-consumption time, the work registry, git cadence, and the expense ledger. The conversation opens with the sharpest claim-vs-evidence contradiction, drafts corrections you ratify, offers to populate the files the machinery can write, and closes with an ideal-state review grounded in the measured gap. On a fresh install it falls back to first-time setup. The 🎤 statusline chip (fed by InterviewDue.ts, daily launchd refresh) says when one is due; wrapping with --mark-done clears the cadence reason, and the skew/staleness reasons clear as their files are actually reviewed.
The Problem
The files that define who you are and what you're working toward drift out of date the moment you stop looking at them. A goal you set in January may be done, dead, or still right — but nobody re-reads the whole TELOS to find out, so the context the system runs on slowly rots. The usual fix is a blank "what's your mission?" prompt, which ignores everything already on file and makes you repeat yourself. This skill reads what's there first, flags only what's gone stale, and asks "still right?" instead of starting from zero.
How It Works
The skill reads the constitutional files via the freshness tooling, scores each section's staleness, and routes to the right workflow — a check-in on a populated system, or first-time setup on a fresh one. Staleness is a priority signal, not a failure flag.