Productivity LLM Prompts Easy Automation Ready

Deep Work Scheduling Blueprint

Helps you define what deep work means for your role, explore different scheduling strategies for it, and build a detailed plan to consistently protect and execute high-focus work blocks.

Best Model
ChatGPT GPT-5.5 / Claude Sonnet 4.6SOP and workflow building
Brevity Mode
Detailed
Difficulty
Easy
Automation
Yes

Use This When

SOPs, task systems, delegation, automation mapping.

Inputs Needed

Current workflow, tools, people involved, bottleneck, desired output, frequency, approval rules.

Expected Output

Workflow map, SOP, automation opportunities, owner/RACI, tools, checklist, maintenance cadence.

The Workflow Prompt

Copy-paste ready. Replace [bracketed placeholders] with your specifics.
You are a operations consultant and productivity systems designer.

Objective:
Deep Work Scheduling Blueprint

Context:
Helps you define what deep work means for your role, explore different scheduling strategies for it, and build a detailed plan to consistently protect and execute high-focus work blocks.

Original task:
I want to establish consistent deep work blocks for high-concentration tasks. First, explain the difference between deep work and shallow work, then analyze my role as {your_role} and list five tasks I do that absolutely require deep work (uninterrupted focus for 90+ minutes) versus five that are shallow work (can be done with distractions or in fragmented time).

Inputs I may provide:
Current workflow, tools, people involved, bottleneck, desired output, frequency, approval rules.

Operating instructions:
- First, restate the objective in one clear sentence.
- If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them.
- Use a Detailed response style.
- Be specific to the business, audience, channel, and constraints provided.
- Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use.
- When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources.
- Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead.
- End with a short QA checklist that helps me verify the output.

Required output:
Workflow map, SOP, automation opportunities, owner/RACI, tools, checklist, maintenance cadence.

Caution:
Avoid generic output; require concrete examples, assumptions, and next steps.

QA Follow-Up Checklist

After the AI returns its output, verify against:

  1. Output is specific to the provided business/context.
  2. Assumptions are clearly labeled.
  3. No unsupported claims without source checks.
  4. Next actions are clear and usable.

Follow-Up Prompt

Run this next to refine the first output into a client-ready version.
Now turn the result for 'Deep Work Scheduling Blueprint' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.

Avoid / Cautions

Avoid generic output; require concrete examples, assumptions, and next steps.

Related Workflows

Copied to clipboard