catchup

## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Activation](#activation) - [Progressive Loading](#progressive-loading) - [4-Step Methodology](#4-step-methodology) - [Output Format](#output-format) # Catchup Analysis Methodology ## Overview Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently. ## When To Use - Joining ongoing work or returning after absence - Before planning or reviewing handoffs - Any "what happened and what's next" context ## When NOT To Use - Doing detailed diff analysis - use diff-analysis instead - Full code review needed - use review-core instead ## Activation **Keywords**: catchup, summary, status, progress, context, handoff **Cues**: "get me up to speed", "current status", "summarize progress" ## Progressive Loading Load modules based on context: **Git**: Load `modules/git-catchup-patterns.md` for git commands. Consider `sanctum:git-workspace-review` for initial data gathering. **Documents/Notes**: Load `modules/document-analysis-patterns.md` for meeting notes, sprint tracking, document revisions. **Logs/Events**: Load `modules/log-analysis-patterns.md` for time-series and metric analysis. **Always Available**: `imbue:proof-of-work`, TodoWrite workflow, structured output. ## Required TodoWrite Items 1. `catchup:context-confirmed` - Boundaries established 2. `...