Agent skill · writing content · davila7
deadline-prep
Generate a structured demo outline from your session's change log and git history. Reads .claude/critical_log_changes.csv and git log to produce presentation-ready talking points for end-of-day demos, standups, or delivery deadlines.
Why this skill is useful
Generates a structured markdown outline for demos based on change logs and git history, which the AI wouldn't reliably create on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
Deadline Prep 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. Workflow Step 1: Gather data sources 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. Step 2: Analyze and categorize changes 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 Step 3: Generate the demo outline Create a structured markdown document: Step 4: Save and present Save the outline to .claude/demo-outline.md. Print the full outline to the terminal so the user can review it immediately. Tips Run this 30 minutes before your deadline to have time to review and add personal context The "Architecture Decisions" section is what reviewers care about most — add context about tradeoffs "What I Would Do Next" shows you think beyond the immediate task Edit the generated outline to add your own voice and any context the log missed Works best with the change-logger hook installed, but functions with git history alone
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/deadline-prep