deadline-prep

Topics in the source

• Deadline Prep
• Workflow
• Step 1: Gather data sources
• Step 2: Analyze and categorize changes
• Step 3: Generate the demo outline
• Step 4: Save and present
• Tips

Generate a structured demo outline from your work session. Combines the change log CSV (from the change-logger hook) with git history to create presentation-ready talking points. Change log (primary source if available): Read .claude/criticallogchanges.csv if it exists Parse columns: timestamp, tool, filepath, action, details Group by: files created, files modified, commands executed Git history (always available): If the CSV doesn't exist, fall back to git-only mode and note this in the output. Group all changes into categories: | Category | Signals | |----------|---------| | Features shipped | New files, new routes, new components, feat commits | | Bug fixes | Modified files with fix commits, error handling changes | | Refactors | Renamed files, structural changes, refactor commits | | Config/Setup | package.json, tsconfig, CI/CD, Docker changes | | Tests | Test files created or modified | | Documentation | README, docs, comments | Create a structured markdown document: Save the outline to .claude/demo-outline.md. Print the full outline to the terminal so the user can review it immediately. Run this 30 minutes before your deadline to have time to review and add personal context T

This is an excerpt. Refer to the complete source and its current requirements.