kairos-review
Run a review at weekly, monthly, quarterly, or yearly zoom — synthesize notes, surface patterns, generate retrospective. Use when running periodic reviews.
What this skill does
# Review One skill, four zoom levels. Data cascades up -- weekly reads raw data, monthly reads weeklies, quarterly reads monthlies, yearly reads quarterlies. ``` /review weekly -- end of work week (Friday) /review monthly -- end of month /review quarterly -- end of quarter (Mar, Jun, Sep, Dec) /review yearly -- end of year (December) ``` ## Core Principle **Present what happened. Don't judge.** The review surfaces data and patterns. It doesn't lecture about what should have been different. Not every milestone needs weekly attention -- Travel is episodic, connections are organic, art has seasons. Only flag gaps where attention was expected and didn't land (e.g., a trip 3 weeks out with no booking). The tone from shutdown feedback applies here: ask what drove the period, then assess. The weekly plan is a starting position, not a contract. ## Tone - Present data first, then patterns - "Chiro got 18h, Resin got 0h" not "You neglected Resin" - Only flag milestones where the gap is actionable - Travel with no activity = normal. Travel with no activity before an unbooked trip = flag. - The score has milestones with different rhythms. Respect that. ## Zoom Levels ### Weekly (`/review weekly`) See `weekly.md` for full template. **Reads:** Daily notes (Mon-Fri), Clockify CSV, ClickUp task completion (via shutdown script), LooseIt email, the week's plan file. **Writes to:** `# Weekly Summary` section at bottom of `kairos/logs/weekly/YYYY/YYYY-WNN.md` **Key sections:** What happened (from ClickUp + daily notes), time tracking (Clockify), where the time went (which milestones got attention), health (LooseIt), patterns, next week. ### Monthly (`/review monthly`) See `monthly.md` for full template. **Reads:** Weekly reviews for the month (already synthesized). Daily notes only if weekly reviews are missing data. **Writes to:** `kairos/logs/monthly/YYYY/YYYY-MM.md` **Key sections:** Portfolio snapshot (status changes), project movement, time trends (from weekly Clockify aggregates), where the time went across the month, goals check (reads `kairos/life-areas/goals.md`), patterns. ### Quarterly (`/review quarterly`) See `quarterly.md` for full template. **Reads:** Monthly reviews for the quarter (already synthesized). Life-area notes (`kairos/life-areas/`). The score (`kairos/roadmaps/`). **Writes to:** `kairos/logs/quarterly/YYYY/YYYY-QN.md` **Key sections:** The quarter in brief (narrative, not metrics), life area review (goals vs evidence), direction check (vision, purpose -- still true?), portfolio alignment (projects serving goals), next quarter focus. This is a compass check, not a performance review. ### Yearly (`/review yearly`) See `yearly.md` for full template. **Reads:** Quarterly reviews for the year (already synthesized). Life-area notes (`kairos/life-areas/`). Roadmaps (`kairos/roadmaps/`). Projects (`projects/`). **Writes to:** `kairos/logs/yearly/YYYY.md` **Key sections:** The year in narrative, life area arc (where each area started vs ended), goal outcomes (met / missed / evolved), portfolio evolution (what shipped, what was archived, what emerged), direction for next year. This is the annual reflection. What changed, what held, what surprised you. ## Notes - Can be run multiple times at any zoom level -- overwrites previous output - Each level trusts the level below. Monthly doesn't re-read daily notes if weeklies exist. - Create folders as needed (`kairos/logs/monthly/YYYY/`, `kairos/logs/quarterly/YYYY/`, `kairos/logs/yearly/`) - LooseIt data feeds weekly and bubbles up. If not provided at weekly, note it as missing. - Clockify CSV: look for `~/Desktop/Clockify_Time_Report_Detailed_*.csv`. If not found, ask once. - ClickUp shutdown data: use `~/workspace/primary-pm/_tools/clickup-today.sh [DATE] --shutdown` for completion picture - Week = Sun-Sat. Daily notes = Mon-Fri.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.