1. What to replace:
Replace each {{placeholder}} with your professional role, top goals for the week, brain dump of pending tasks, calendar meetings, and biggest distractions.
2. How to customize variables:
- user_role_and_work_style: Specify whether you are a developer, founder, student, or manager.
- core_weekly_milestones: Limit to 2-4 major outcomes.
- raw_task_dump: Paste your entire unordered to-do list without worrying about formatting.
- fixed_meetings_and_constraints: Include existing calendar blocks.
- primary_productivity_leaks: Be honest about your procrastination habits.
3. Compatible AI Tools:
Claude 3.5 Sonnet, ChatGPT (GPT-4o), Gemini 1.5 Pro.
4. Expected Result:
A realistic, battle-tested weekly sprint schedule that prevents burnout, protects deep work hours, and guarantees high-leverage execution.
Act as an executive performance coach and master agile productivity strategist. Transform my messy weekly to-do list, project deliverables, and strategic commitments into an elite, realistic 5-day Deep Work Sprint Plan.
Context & Inputs:
- My Role & Context: {{user_role_and_work_style}}
- Key Weekly Milestones to Accomplish: {{core_weekly_milestones}}
- Raw Task Backlog / Commitments: {{raw_task_dump}}
- Fixed Commitments / Meetings: {{fixed_meetings_and_constraints}}
- Main Distractions or Productivity Bottlenecks: {{primary_productivity_leaks}}
Sprint Architecture Framework:
1. Cognitive Triage & The 3 MITs (Most Important Tasks):
- Select exactly 3 needle-moving initiatives that make this week an objective success.
- Classify all remaining tasks into: Quick Batching (<15 mins), Delegate / Defer, and Eliminate.
2. Daily Time-Blocked Execution Schedule (Monday to Friday):
- Allocate 2 dedicated "Deep Work Focus Blocks" (90-120 mins each) during peak cognitive hours for the MITs.
- Create 1 daily "Shallow Work Consolidation Window" (45 mins) for email, Slack, and administrative triage.
- Build in buffer zones (30 mins daily) to absorb unexpected fires without breaking sprint velocity.
3. Friction Barriers & Distraction Defense Protocol:
- Customized rules addressing {{primary_productivity_leaks}} (e.g., notification boundaries, async communication templates, browser blockers).
4. Friday Retrospective & Closure Ritual:
- A 5-minute review checklist to audit completion metrics, log cognitive fatigue, and cleanly power down for the weekend.
Customize this prompt (fill variables)
How to use this prompt
Example: what to expect
Example input
user_role_and_work_style: Lead Full-Stack Engineer working remotely, best focus between 8 AM - 12 PM
core_weekly_milestones: 1) Ship auth refactor PR, 2) Write technical migration spec for database cluster
raw_task_dump: review 4 pending PRs, fix bug #402 in payment webhook, attend sprint retro, write unit tests for OAuth, answer junior dev questions
fixed_meetings_and_constraints: Daily standup 9:30-9:45 AM, Wednesday sprint planning 2-3:30 PM
primary_productivity_leaks: context-switching every time a Slack notification pops up
Example output
A complete Monday-to-Friday schedule blocking 8:00-9:30 AM and 10:00-11:30 AM for undisturbed coding on the OAuth refactor and migration spec. Slack and PR reviews are consolidated into two 30-minute afternoon sprints (1:30 PM and 4:30 PM). Includes a pre-written Slack status template ("In Deep Work Block until 11:30 AM") to set team boundaries.
Variables explained
| Variable | What to enter |
|---|---|
{{user_role_and_work_style}} |
Describe your profession and peak mental energy hours. |
{{core_weekly_milestones}} |
State your essential deliverables for the week. |
{{raw_task_dump}} |
Paste your full unordered to-do list. |
{{fixed_meetings_and_constraints}} |
List immovable meetings or personal obligations. |
{{primary_productivity_leaks}} |
Identify habits that derail your focus. |
Tips for better results
Best used for: Executive productivity and sprint management
- Give the AI context first: who you are, who the audience is, and what “good” looks like for you.
- Ask for output in a specific format (bullets, table, markdown) when you need structure.
- If the result is close but not perfect, reply with “keep the structure, make it more…” — do not start over.
- For long tasks, split the prompt into steps instead of expecting one giant answer.
- Different tools behave differently — ChatGPT, Claude and Gemini each have their own style. Try this prompt on the tool you use most.
How to use this Productivity prompt effectively
What this prompt does
Transform scattered task backlogs and high-level quarterly goals into a prioritized 5-day time-blocked sprint with cognitive load balancing, deep work blocks, and friction barriers.
Getting the most out of it
- Copy the prompt and paste it into your AI tool of choice (ChatGPT, Claude or Gemini).
- Fill the variables in curly brackets with your own topic, audience and tone — the customize button above builds a ready version for you.
- Review the first draft for facts and style before using it. AI output is a starting point, not a final product.
- Iterate: tell the AI what to keep and what to change. Small corrections beat re-typing the whole prompt.
Common mistakes to avoid
- Leaving the {{variables}} unfilled — the AI then guesses your topic.
- Expecting one output to be perfect — plan for 2–3 rounds of refinement.
- Pasting confidential information into public AI tools.