Deadline Prep
Productivity skill, available on Zeplik
Deadline Prep is a ready-to-run productivity skill on Zeplik. Not for sprint ceremonies (use sprint-planning) or capacity math (use capacity-plan). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
The Deadline Prep skill loads automatically when your request matches it, or you can invoke it directly by typing /deadline-prep in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.
What the Deadline Prep skill can do
- Turn git history or commit logs into a demo-ready outline
- Categorize changes into features, fixes, refactors, config, tests, docs
- Summarize architecture decisions and tradeoffs for reviewers
- Compute session metrics like files changed, lines, and commits
Try these prompts on Zeplik
Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.
How the Deadline Prep skill works
/deadline-prep
Generate a structured demo outline from a work session. Combines whatever change records are available (git history, commit lists, session notes, or the user's own description of what they did) into presentation-ready talking points for demos, standups, or delivery deadlines.
Workflow
Step 1: Gather data sources
Use whatever is available, in order of preference:
- Git history (if working in a repo):
git log --oneline --since="today 00:00"andgit diff --stat HEAD~10 2>/dev/null || git diff --stat - Pasted logs: if the user pastes a
git log, commit list, changelog, or change-log CSV, parse it (group by files created, files modified, commands executed) - User description: if no logs exist, ask the user to briefly list what they worked on and build the outline from that; note in the output that it is based on their description
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:
# 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
## Architecture Decisions
- **[Decision]**: Why this approach over alternatives
- **[Decision]**: Tradeoff 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
Omit Session Metrics if no logs are available to compute them honestly.
Step 4: Deliver
Present the full outline in chat so the user can review it immediately; if working in a repo, also offer to save it (e.g., demo-outline.md).
Tips
- Run this 30 minutes before the deadline to leave 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 thinking beyond the immediate task
- Encourage the user to edit the outline into their own voice and add context the log missed
Usage
/deadline-prep $ARGUMENTS
How to use the Deadline Prep skill
Sign in to Zeplik
Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Deadline Prep skill right away.
Describe your productivity task
Ask in plain language, or type /deadline-prep to invoke the skill directly. Zeplik recognizes the Deadline Prep skill and applies its method.
Review and refine the result
Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.
Source and credit
- Author
- davila7
- License
- MIT
Adapted from the open-source davila7/claude-code-templates project and tuned to run natively on Zeplik. View source on GitHub.
Frequently asked questions
- What is the Deadline Prep skill?
- Deadline Prep is a ready-to-run productivity skill on Zeplik. Not for sprint ceremonies (use sprint-planning) or capacity math (use capacity-plan). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
- How do I use Deadline Prep on Zeplik?
- Sign in to Zeplik and ask in plain language, or type /deadline-prep in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
- Which AI model does the Deadline Prep skill use?
- Any model you choose. Zeplik works across every model in one chat, so the Deadline Prep skill runs on your preferred model for the task.
- Where does the Deadline Prep skill come from?
- The Deadline Prep skill is adapted from the open-source davila7/claude-code-templates project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
- How much does the Deadline Prep skill cost?
- Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.
Related productivity skills
- Audio TranscriberUse when the user attaches audio or voice recordings to transcribe -- cleanup, speaker labels, timestamps, minutes or notes from a recording. Not for summarizing documents (use summarize-anything).
- File OrganizerUse when designing a folder structure and reorganization plan for messy files -- downloads cleanup, duplicates, naming, archive rules. Not for converting file formats (use file-conversion).
- Linear Issue AssistantUse when the user pastes Linear issues, CSV exports, or cycle data -- triage, well-formed issue writeups, cycle plans, updates in Linear conventions. Not for sprint ceremonies (use sprint-planning).
- Marp Slide DecksUse when creating Markdown/Marp slide decks with themed embedded CSS the user renders via Marp CLI or VS Code. Not for general presentation building (use slides).
- Notion WorkflowsUse when designing Notion databases, templates, formulas, or workspace systems -- knowledge capture, meeting docs, specs, template businesses. Not for generic note-taking advice.
- Obsidian WorkflowsUse when working in Obsidian -- vault structure, Bases (.base files), wikilinks, callouts, plugins, zettelkasten, Web Clipper templates. Not for Notion (use notion-workflows).
More on Zeplik
Try Deadline Prep on Zeplik
Every model, one chat. Bring the Deadline Prep skill into your next conversation and let the assistant do the work.