ckis-weekly-review

name	ckis-weekly-review
description	CKIS-aware weekly review. Wraps the operational weekly-review skill with CKIS-specific health checks and proposed _MEMORY.md edits. Use when [OWNER] says "ckis weekly review" or runs the Sunday cadence. Never writes to _MEMORY.md automatically; surfaces edits for confirmation.

CKIS Weekly Review

Sunday cadence. Wraps the existing weekly-review skill (.claude/ckis-skills/weekly-review/skill.md) and adds a CKIS-specific layer: lightweight health checks and proposed _MEMORY.md edits.

Workflow

0. De-duplication check (Cron 4 coordination). Cron 4 runs this skill automatically every Friday at 17:00 via headless claude -p. Before doing anything else:

   • Glob 08-goals/weekly/YYYY-MM-DD-weekly-review.md for today's date.
   • If a file already exists for today (likely written by Cron 4), STOP and surface to [OWNER]: show the existing path and ask explicitly: "A weekly review already exists for today — likely from Cron 4. Overwrite, append addendum, or abort? (overwrite/append/abort)"
   • Only proceed when Eduardo answers. Default behavior on no-answer is abort.

1. Run the operational weekly-review skill. Either invoke it (if the harness supports nested skills) or replicate its core logic:

   • Scan daily notes for the past 7 days (02-daily/2026-MM-DD.md).
   • Check 08-goals/2026-annual.md and current quarter targets.
   • Detect patterns: recurring themes, repeated blockers, unmet commitments.
   • Flag unprocessed inbox items (>7 days old).
   • Generate a "what shipped / slipped / patterns" summary.

2. Append CKIS health items. Lightweight subset of CKIS file 13 §8:

   • Inbox items older than 7 days — count.
   • Active projects silent ≥14 days — list.
   • Open decisions in _MEMORY.md older than 14 days — list.
   • Blockers unchanged across 2+ weekly reviews — list (compare to last weekly review file).
   • CKIS file index integrity — does 01-systems/ckis/00-ckis-master-context.md §10 still match what's in the folder?
   • Dev Brain session activity this week — if ~/Documents/Dev Brain/sessions/index.md exists, run grep $(date '+%Y-%m-%d') ~/Documents/Dev\ Brain/sessions/index.md | wc -l and report the count of coding sessions logged this week.

3. Propose _MEMORY.md edits. Read the current _MEMORY.md, then:

   • For each section (Business state, Active focus, Open Decisions, Blockers, Financial state, University, System state) — produce a proposed edit only if the past week's activity warrants one.
   • Render each proposed edit as a unified-diff-style block (don't write it).
   • Keep proposals concise; if no change needed, say so.

4. Save the review to 08-goals/weekly/YYYY-MM-DD-weekly-review.md using the template from CKIS file 08 §9.

5. Surface to Eduardo. Output:

   • The path to the saved review.
   • The CKIS health items.
   • The proposed _MEMORY.md edits.
   • Top 3 priorities for next week.
   • Single explicit ask: "Apply these _MEMORY.md edits? (y/n)"

6. Apply _MEMORY.md edits only if [OWNER] says yes. Never silent-apply.

Rules

• Never write to _MEMORY.md without explicit confirmation.
• Never modify a previous weekly review file.
• Always save to 08-goals/weekly/YYYY-MM-DD-weekly-review.md.
• Always preserve the daily-note files; this skill is read-only on 02-daily/.
• Limit the review file to ~150 lines. If patterns sprawl, link out to a permanent note in 05-knowledge/patterns/ instead of inlining everything.

Output Shape

# Weekly Review — YYYY-MM-DD

## What shipped
- …

## What slipped
- …

## Patterns noticed
- …

## Inbox state
- Processed: N
- Pending: N
- Stale flagged: N

## Goal check
- [[08-goals/2026-annual]] alignment: …

## CKIS health
- Inbox >7d: N items
- Silent active projects: <list>
- Stale open decisions (>14d): <list>
- Persistent blockers: <list>
- CKIS index integrity: ok | drift detected
- Dev Brain coding sessions this week: N (or "Dev Brain not present")

## Proposed _MEMORY.md edits
- (diff-style block per section needing changes; "no change" otherwise)

## Next week — top 3 priorities
1.
2.
3.

QA Checklist

• Review saved to correct path.
• No _MEMORY.md writes without confirmation.
• Top 3 priorities are concrete (not "work on [YOUR_PROJECT]").
• CKIS health checked.
• Stale items surfaced, not auto-deleted.

Do Not

• Auto-delete stale inbox items.
• Edit _PROFILE.md or _INTERESTS.md.
• Run a knowledge-synthesis pass — that's monthly-consolidation's job.
• Touch CKIS architecture files.