deadline-prep

Included with Lifetime

$97 forever

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.

Data & Analytics

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/critical_log_changes.csv` if it exists
- Parse columns: timestamp, tool, file_path, action, details
- Group by: files created, files modified, commands executed

**Git history** (always available):
```bash
git log --oneline --since="today 00:00"
git diff --stat HEAD~10 2>/dev/null || git diff --stat
```

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:

```markdown
# Demo Outline — [Date]

## What I Shipped
- **[Feature/Fix name]**: One sentence explaining what it does and why it matters
- **[Feature/Fix name]**: One sentence explaining what it does and why it matters
- **[Feature/Fix name]**: One sentence explaining what it does and why it matters

## Architecture Decisions
- **[Decision]**: Why I chose this approach over alternatives
- **[Decision]**: Tradeoff I made and the reasoning

## What I Would Do Next
1. **[Priority 1]**: Why this is the most important next step
2. **[Priority 2]**: What this would unlock
3. **[Priority 3]**: Nice-to-have improvement

## Session Metrics
- Files changed: X
- Lines: +Y / -Z
- Commits: N
- Key files: `path/to/important/file.ts`, `path/to/other.ts`
- Time window: HH:MM - HH:MM
```

### 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

Files: 1

Size: 2.9 KB

Complexity: 7/100

Category: Data & Analytics

Source: https://github.com/davila7/claude-code-templates/tree/main/cli-tool/components/skills/productivity/deadline-prep

Related in Data & Analytics

clawarr-suite

Included

Comprehensive management for self-hosted media stacks (Sonarr, Radarr, Lidarr, Readarr, Prowlarr, Bazarr, Overseerr, Plex, Tautulli, SABnzbd, Recyclarr, Unpackerr, Notifiarr, Maintainerr, Kometa, FlareSolverr). Deep library exploration, analytics, dashboard generation, content management, request handling, subtitle management, indexer control, download monitoring, quality profile sync, library cleanup automation, notification routing, collection/overlay management, and media tracker integration (Trakt, Letterboxd, Simkl).

Data & Analyticsscripts

querying-soql

Included

SOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.

Data & Analyticsscripts

app-store-optimization

Included

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.

Data & Analyticsscripts

habit-flow

Included

AI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.

Data & Analyticsscripts

app-store-optimization

Included

Data & Analyticsscripts

visualizing-data

Included

Builds dashboards, reports, and data-driven interfaces requiring charts, graphs, or visual analytics. Provides systematic framework for selecting appropriate visualizations based on data characteristics and analytical purpose. Includes 24+ visualization types organized by purpose (trends, comparisons, distributions, relationships, flows, hierarchies, geospatial), accessibility patterns (WCAG 2.1 AA compliance), colorblind-safe palettes, and performance optimization strategies. Use when creating visualizations, choosing chart types, displaying data graphically, or designing data interfaces.

Data & Analyticsscripts