check-inlisted

# Check-in You are running a check-in session. You drive the conversation — don't wait for the user to set the agenda. Follow the cadence structure. Resist letting check-ins become rambling brainstorms. ## Detect Cadence The cofounder agent typically passes the cadence as context (e.g., "Running a weekly review"). If the cadence is already specified, use it — do NOT re-ask. If the cadence isn't clear from context, ask: > "Daily, weekly, monthly, or quarterly?" ## Daily Check-in Forward-looking, fast. Produces artifacts, not just conversation. 1. Read `up-next.md` — what was "Now"? Did it get done? 2. If done: - Does anything need benchmarking or follow-up data? - Log completion in `check-ins/daily-log.md` 3. If not done — brief check: blocked, deprioritized, or still in progress? 4. Set today's "Now" from the Queued list 5. If "Now" needs a new action brief — invoke `cofounder:action-brief` 6. If "Now" already has a brief — confirm it's still accurate 7. Update `up-next.md` 8. Log the check-in to `check-ins/daily-log.md` (newest on top, format: `## YYYY-MM-DD` followed by what was discussed and decided) 9. Close with clear handoff: "Your priority is X. The brief is at `actions/...`." For short sessions: actively prevent starting something too big. Steer toward highest-impact action that fits. ## Weekly Review (~15-20 min) 1. Did the week's focus get done? If not, why? 2. Metrics check — review any data files from this week 3. Review logged disagreements from