deadline-prep

Generates a structured demo outline from change log CSV data and git history.

30.5k|3.5k|Updated Jul 4, 2025
One-click install
npx skills add https://github.com/davila7/claude-code-templates --skill deadline-prep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deadline-prep
Source: https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/productivity/deadline-prep
Command: npx skills add https://github.com/davila7/claude-code-templates --skill deadline-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preparing talking points for end-of-day demos, standups, or delivery deadlines is time-consuming when you must manually review everything you changed during a work session. This Skill automates that by turning your session's change log and git history into a presentation-ready outline.

Core Features & Use Cases

  • Data Gathering: Reads .claude/critical_log_changes.csv (from the change-logger hook) and falls back to git history (git log, git diff --stat) when the CSV is unavailable.
  • Automatic Categorization: Groups changes into features shipped, bug fixes, refactors, config/setup, tests, and documentation based on file signals and commit prefixes.
  • Structured Output: Produces a markdown demo outline with sections for shipped work, architecture decisions, next priorities, and session metrics, saved to .claude/demo-outline.md.
  • Use Case: Thirty minutes before a sprint demo, run the Skill to get a draft outline of everything you shipped today, then edit it to add your own context and voice.

Quick Start

Ask the assistant to generate a demo outline from today's changes and git history before your deadline presentation.

Frequently Asked Questions about deadline-prep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a demo outline from my git history?

Run the Skill before your deadline and it reads today's commits via git log and git diff --stat, categorizes the changes, and writes a markdown outline to .claude/demo-outline.md. You can then edit the outline to add personal context.

What data sources does the demo outline use?

It primarily reads .claude/critical_log_changes.csv produced by the change-logger hook, parsing timestamp, tool, file path, action, and details columns. If the CSV is missing, it falls back to git history alone and notes this in the output.

Does deadline-prep work without the change-logger hook installed?

Yes, it functions with git history alone by running git log --oneline since midnight and git diff --stat. The output notes that it is operating in git-only mode, though the change-logger hook provides richer session detail.

What sections are included in the generated demo outline?

The outline includes What I Shipped, Architecture Decisions, What I Would Do Next, and Session Metrics. Metrics cover files changed, lines added and removed, commit count, key files, and the session time window.

When should I run the demo outline generation?

Run it about 30 minutes before your deadline so you have time to review and add personal context. The architecture decisions and next-steps sections benefit most from your own edits and reasoning.