260 prompts · 13 categories

The Productivity Prompt Pack

260 productivity prompts to get more done with less friction.

Goals, time, tasks, focus, energy, habits and systems — design a personal operating system that actually sticks, prompt by prompt.

Get all 260 prompts — free

Drop your email and the full library unlocks instantly.

No spam. Instant access. Unsubscribe anytime.

  • 260 copy-paste prompts across 13 categories
  • Works with ChatGPT, Claude & Gemini
  • From goal-setting to deep work to repeatable systems

Joined by 6,000+ founders & marketers

260 prompts

#001Personal Operating System Blueprint

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMFounders, freelancers, creators, managers, students, operators, consultants, and knowledge workers who need a repeatable productivity structure.

Build a clear personal operating system from your real goals, constraints, work patterns, tools, energy, and recurring responsibilities.

You are a personal operating system architect. Design a practical system that helps me choose the right work, protect focus, manage commitments, and review progress without relying on motivation alone. My context: Role / work type: [ROLE] Main goals: [GOALS] Current projects: [PROJECTS] Recurring responsibilities: [RESPONSIBILITIES] Current tools: [TOOLS] Current weekly schedule: [SCHEDULE] Biggest productivity problems: [PROBLEMS] Energy patterns: [ENERGY PATTERNS] Distractions: [DISTRACTIONS] What already works: [WORKING WELL] What feels chaotic: [CHAOS] Preferred system style: [LIGHT / MEDIUM / STRICT] Build the system in 5 layers: Layer 1 — Operating principles Create 10 rules that should govern how I work. Each rule must include: - principle - why I need it - behavior it creates - behavior it prevents - warning sign that I am breaking it Layer 2 — Priority architecture Turn my goals and projects into: - top outcomes - active projects - maintenance responsibilities - optional work - pause list - eliminate list For each item explain why it belongs there. Layer 3 — Execution workflow Design workflows for: - capturing tasks - clarifying tasks - choosing daily work - planning the week - protecting deep work - handling admin - processing messages - reviewing progress Layer 4 — Calendar and energy design Create a weekly structure that includes: - focus blocks - communication blocks - admin blocks - review blocks - recovery blocks - buffer time - no-meeting or low-meeting zones Layer 5 — Review loop Create: - daily startup checklist - daily shutdown checklist - weekly review - monthly reset - failure recovery protocol Rules: - Do not give generic productivity advice. - Do not recommend more tools unless there is a clear workflow reason. - Do not build a system that requires perfect discipline. - Make the system realistic, repeatable, and easy to restart after a bad week. --------------------------------------------------------------------------------

#002Work Style Compass

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who have tried generic productivity systems and need one that matches their energy, attention, personality, and work reality.

Identify how you naturally work best and translate that into schedules, task types, focus rules, and planning rituals.

Act as a work style analyst. Help me discover my productivity style and create a system that fits how I actually operate. Inputs: My work: [WORK TYPE] My best focus time: [BEST FOCUS TIME] My lowest energy time: [LOW ENERGY TIME] Tasks that energize me: [ENERGIZING TASKS] Tasks that drain me: [DRAINING TASKS] How I handle deadlines: [DEADLINE STYLE] How I handle ambiguity: [AMBIGUITY STYLE] How I make decisions: [DECISION STYLE] My environment: [ENVIRONMENT] Constraints: [CONSTRAINTS] Current problem: [PROBLEM] Use this structure: 1. Work style diagnosis Score me from 1 to 10 on: - planner vs improviser - sprinter vs steady executor - solo processor vs collaborative processor - deadline-driven vs routine-driven - deep worker vs task switcher - starter vs finisher - detail-driven vs big-picture-driven For each score explain: - why it matters - advantage - risk - system implication 2. Energy and attention map Create a map of: - best time for creative work - best time for analytical work - best time for admin - best time for meetings - best time for planning - best time for recovery 3. Work style rules Create 12 personalized rules that tell me: - when to schedule hard work - when to avoid decisions - when to batch communication - when to stop pushing - when to use deadlines - when to reduce options - when to ask for help 4. Ideal week design Create a sample week that matches my work style. Include: - deep work windows - shallow work windows - planning blocks - communication blocks - recovery blocks - open buffer 5. Personal user manual Write a one-page manual called "How I Work Best" with: - best work conditions - worst work conditions - how to start - how to avoid overload - how to recover after disruption - how to measure a good week Rules: - Do not force a one-size-fits-all routine. - Do not assume mornings are best. - Do not shame low-energy patterns. - Design for consistency, not fantasy. --------------------------------------------------------------------------------

#003Priority Stack Builder

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMBusy people juggling goals, projects, requests, deadlines, and unclear responsibilities.

Create a hierarchy of priorities that makes it easier to say yes, say no, schedule work, and remove low-value tasks.

You are a priority strategist. Turn my messy list of responsibilities into a clear priority stack that tells me what matters most and what should stop stealing attention. Raw inputs: Goals: [GOALS] Projects: [PROJECTS] Tasks: [TASKS] Deadlines: [DEADLINES] Requests from others: [REQUESTS] Recurring responsibilities: [RECURRING RESPONSIBILITIES] Available time: [TIME] Current stress points: [STRESS POINTS] Things I feel guilty ignoring: [GUILT ITEMS] Create a priority stack: A. Sort the work Group everything into: - mission-critical outcomes - high-leverage projects - required maintenance - relationship obligations - urgent but low-leverage work - optional opportunities - fake productivity - emotional clutter - unclear items B. Build the stack Create 5 levels: Level 1: Must protect Level 2: Must progress Level 3: Must maintain Level 4: Can defer Level 5: Should delete, delegate, or pause For each item include: - level - reason - cost of ignoring it - next action - deadline, if any - energy required - decision needed C. Create decision rules Write rules for what to do when: - two priorities compete - a new request appears - I have only 30 minutes - I have low energy - I am behind - someone pressures me - a task feels urgent but not important - I want to procrastinate D. Weekly priority filter Create a weekly process: - review goals - choose 3 outcomes - choose 5 must-do tasks - create a pause list - create a no-list - schedule the hardest work first - define what will not get done E. Final output Give me: - top 3 priorities - active project list - defer list - delete list - daily focus rule - weekly review question Rules: - Do not treat all tasks equally. - Do not prioritize by urgency alone. - Do not let guilt become a priority system. - Make the output simple enough to use every week. --------------------------------------------------------------------------------

#004Weekly Operating Rhythm Designer

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMAnyone who starts each week scattered, overcommitted, or unsure where to focus.

Design a repeatable weekly planning rhythm that turns goals into scheduled action, protects capacity, and prevents overload.

Act as a weekly operating rhythm designer. Create a weekly planning system I can repeat every week with minimal friction. Context: Main goals: [GOALS] Current projects: [PROJECTS] Recurring work: [RECURRING WORK] Meetings: [MEETINGS] Available hours: [AVAILABLE HOURS] Energy pattern: [ENERGY] Current planning habit: [CURRENT HABIT] Where weeks usually break: [BREAK POINTS] Tools: [TOOLS] Design the rhythm: 1. Weekly intake Tell me exactly what to review before planning: - calendar - deadlines - active projects - unfinished tasks - waiting-for items - personal commitments - energy constraints - upcoming risks 2. Weekly selection Create rules for choosing: - 1 primary outcome - 2 secondary outcomes - 3 to 5 must-do tasks - projects to move forward - work to pause - commitments to renegotiate 3. Weekly schedule structure Build a weekly template with: - planning block - deep work blocks - communication blocks - admin block - project review block - buffer block - recovery block - weekly shutdown 4. Midweek correction Create a 15-minute midweek review that answers: - what changed? - what is still important? - what is slipping? - what should be cut? - what needs communication? - what is the next best move? 5. End-of-week closeout Create a review ritual with: - wins - misses - unfinished work - lessons - bottlenecks - next week setup - system adjustment Rules: - Do not schedule every minute. - Do not allow a weekly plan with more work than capacity. - Do not ignore personal commitments. - The system should create clarity before the week begins and recovery when the week changes. --------------------------------------------------------------------------------

#005Daily Execution Command Center

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who lose days to reactive work, unclear priorities, procrastination, or fragmented attention.

Create a daily operating plan that chooses the right work, handles interruptions, and ends the day cleanly.

You are a daily execution coach. Build a daily command center that helps me turn priorities into completed work. Today’s inputs: Today’s tasks: [TASKS] Today’s calendar: [CALENDAR] Energy level: [ENERGY] Available focus time: [FOCUS TIME] Deadlines: [DEADLINES] Top weekly priorities: [WEEKLY PRIORITIES] Likely interruptions: [INTERRUPTIONS] Hard stop time: [HARD STOP] Current mood / mental state: [STATE] Create the command center: A. Morning triage Sort today into: - one mission-critical outcome - two supporting outcomes - must-respond items - admin items - optional items - defer items - delete items B. Execution order Build a realistic daily plan. For each block include: - time window - task - reason it belongs there - energy match - success criteria - backup option if interrupted C. If-then recovery rules Create rules for: - if a meeting runs long - if urgent work appears - if I procrastinate - if I lose focus - if I feel tired - if I finish early - if I only have 15 minutes - if the day collapses D. Anti-drift prompts Write 8 short questions I can ask during the day to return to focus. Examples: - What is the next visible action? - What matters if I only finish one thing? E. Shutdown ritual Create a 10-minute end-of-day process: - capture loose tasks - update status - reschedule unfinished work - choose tomorrow’s first task - close open loops - stop working Rules: - Do not create a perfect-day fantasy. - Do not overload the schedule. - Do not let optional tasks compete with critical outcomes. - The day should still be successful even if something changes. --------------------------------------------------------------------------------

#006Focus Firewall Builder

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who need focused execution for writing, coding, strategy, design, analysis, studying, or creative work.

Design boundaries, rules, and recovery protocols that protect deep work from notifications, context switching, meetings, and digital noise.

Act as a focus systems designer. Build a focus firewall that protects my attention before, during, and after deep work. My situation: Deep work I need to do: [DEEP WORK] Current distractions: [DISTRACTIONS] Notifications: [NOTIFICATIONS] Meetings / messages: [MEETINGS / MESSAGES] Work environment: [ENVIRONMENT] Devices: [DEVICES] Peak focus times: [PEAK TIMES] Typical interruption sources: [INTERRUPTIONS] Focus goal per week: [FOCUS GOAL] Build the focus firewall: 1. Attention threat model Identify threats from: - phone - email - chat - meetings - browser tabs - multitasking - unclear tasks - emotional stress - open loops - fatigue - environment - boredom For each include: - threat - trigger - damage - prevention - recovery action 2. Focus block protocol Create protocols for: - 25-minute block - 50-minute block - 90-minute block - 2-hour block Each must include: - setup checklist - task selection rule - allowed tools - forbidden behaviors - break rule - completion signal 3. Communication boundaries Write rules for: - email windows - chat response times - meeting buffers - urgent exceptions - status updates - do-not-disturb periods 4. Recovery system Create a protocol for when focus breaks: - 30-second reset - 2-minute reset - 10-minute reset - restart decision - task simplification - environment reset 5. 14-day focus experiment Design a test with: - rule to test - metric to track - daily note - weekly review - adjustment plan Rules: - Do not recommend unrealistic digital minimalism. - Do not ignore real communication obligations. - Do not rely only on willpower. - Protect focus through defaults, friction, and recovery. --------------------------------------------------------------------------------

#007Energy-First Calendar Architect

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople with fluctuating energy, creative workers, founders, parents, students, neurodivergent workers, and anyone tired of rigid time-blocking.

Build a calendar system that matches hard work, communication, admin, recovery, and decisions to your actual energy patterns.

You are an energy-first calendar architect. Help me design a schedule based on capacity, attention, and recovery instead of forcing identical days. Inputs: Energy pattern: [ENERGY PATTERN] Best time for hard work: [BEST TIME] Worst time for hard work: [WORST TIME] Work types: [WORK TYPES] Recurring commitments: [COMMITMENTS] Meetings: [MEETINGS] Deadlines: [DEADLINES] Recovery needs: [RECOVERY] Sleep / life constraints: [CONSTRAINTS] Current calendar problem: [PROBLEM] Create the energy-first calendar: A. Task-energy classification Classify my work into: - high-focus - creative - analytical - social - administrative - emotional - routine - recovery-compatible - not-for-low-energy B. Energy windows Define: - peak work window - stable work window - low-energy window - communication window - admin window - recovery window - decision window - no-decision window C. Calendar template Design a weekly template with: - deep work - meetings - admin - communication - planning - recovery - buffer - personal commitments D. Energy-based rules Create rules for: - high-energy days - normal days - low-energy days - disrupted days - deadline days - recovery days E. Minimum viable day Define what counts as success on a low-energy day: - one critical action - one maintenance action - one communication action - one recovery action - tomorrow setup Rules: - Do not treat low energy as laziness. - Do not schedule hard work in known low-energy windows. - Do not fill all empty calendar space. - The calendar must protect output and sustainability. --------------------------------------------------------------------------------

#008Task Capture Pipeline Designer

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople with tasks spread across notes, email, chat, memory, screenshots, meetings, and multiple apps.

Create a reliable task capture and processing system that turns scattered inputs into clear next actions.

Act as a task pipeline designer. Build a system that captures every task, clarifies it, and moves it to the right place without clutter. Current task situation: Where tasks appear: [SOURCES] Current task tools: [TOOLS] Task types: [TASK TYPES] Recurring tasks: [RECURRING TASKS] Follow-ups: [FOLLOW-UPS] Projects: [PROJECTS] Biggest task issue: [ISSUE] Review frequency: [REVIEW FREQUENCY] Preferred complexity: [SIMPLE / MODERATE / DETAILED] Design the pipeline: 1. Capture channels Create rules for capturing tasks from: - email - chat - meetings - calls - notes - ideas - calendar - documents - verbal requests - personal reminders 2. Clarification formula Rewrite each task using: - action verb - object - outcome - deadline - context - project - time estimate - energy level Show 10 examples of vague tasks rewritten clearly. 3. Processing workflow Create a daily workflow: - collect - clarify - delete - delegate - schedule - defer - batch - assign to project - mark waiting-for 4. Task states Define simple statuses: - inbox - next - today - scheduled - waiting - project - someday - done Explain what enters and exits each state. 5. Review and cleanup Create: - daily task cleanup - weekly task review - overdue task protocol - stale task rule - task deletion rule Rules: - Do not leave vague tasks in the active list. - Do not create too many categories. - Do not rely on memory. - The system should reduce mental load, not create another job. --------------------------------------------------------------------------------

#009Project Portfolio Radar

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMAnyone managing multiple personal, client, business, creative, academic, or operational projects.

Build a lightweight system for tracking active projects, stalled projects, risks, next actions, dependencies, and weekly momentum.

You are a project portfolio strategist. Help me see all active projects clearly and decide what needs attention next. Project list: [PASTE PROJECTS] Context: Role: [ROLE] Project types: [PROJECT TYPES] Deadlines: [DEADLINES] Stakeholders: [STAKEHOLDERS] Dependencies: [DEPENDENCIES] Available time: [TIME] Current tracking method: [METHOD] Biggest project problems: [PROBLEMS] Build the radar: A. Project inventory For each project define: - desired outcome - current status - next action - deadline - owner - dependency - blocker - risk - priority - energy required B. Project health scan Score each project from 1 to 10 on: - clarity - momentum - importance - urgency - risk - next-action clarity - capacity fit - stakeholder alignment C. Radar categories Sort projects into: - active and moving - active but blocked - urgent - strategic - maintenance - should pause - should finish fast - should delete or archive D. Weekly project review Create a review ritual: - inspect every active project - update status - choose next action - resolve blockers - communicate changes - pause low-priority work - close completed projects E. Dashboard layout Provide a copyable project dashboard with fields and example entries. Rules: - Do not turn every task into a project. - Do not track details that will not affect decisions. - Do not allow active projects with no next action. - The radar should make stalled work visible quickly. --------------------------------------------------------------------------------

#010Decision Rules Engine

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who lose productivity through indecision, too many options, unclear priorities, or repeated decision fatigue.

Create decision rules that reduce overthinking, speed up tradeoffs, and clarify when to act, wait, test, delegate, or decline.

Act as a decision systems coach. Build a personal decision rules engine for my work and life. Decision context: Common decisions I face: [DECISIONS] Current decision I am avoiding: [CURRENT DECISION] Goals: [GOALS] Constraints: [CONSTRAINTS] Risk tolerance: [RISK TOLERANCE] Information available: [INFO] Decision deadlines: [DEADLINES] People affected: [PEOPLE] Where I overthink: [OVERTHINKING AREAS] Build the engine: 1. Decision types Classify decisions into: - reversible - irreversible - low-stakes - high-stakes - urgent - strategic - operational - preference-based - data-dependent - emotion-heavy For each type, define the correct decision process. 2. Decision rules Create rules for: - when to decide immediately - when to research - when to ask for advice - when to test - when to delay - when to say no - when to reverse - when to commit fully 3. Decision templates Create 5 templates: - 5-minute decision - 30-minute decision - high-stakes decision - opportunity decision - stop / continue / change decision Each template must include questions, output, and stop condition. 4. Anti-overthinking safeguards Create safeguards for: - endless research - perfectionism - fear of regret - unclear tradeoffs - asking too many people - changing direction too often 5. Review loop Design a monthly review of decisions: - decisions made - decisions delayed - outcomes - lessons - rule updates Rules: - Do not make simple decisions complex. - Do not recommend endless information gathering. - Do not ignore emotional signals. - The system should help me act sooner with better judgment. --------------------------------------------------------------------------------

#011Commitment Firewall

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who overcommit, accept unrealistic deadlines, struggle to decline requests, or let other people's priorities consume their schedule.

Build boundaries for saying yes, saying no, renegotiating deadlines, limiting workload, and protecting strategic work.

You are a commitment and boundary systems designer. Create a system that helps me protect capacity while remaining reliable. Inputs: Current commitments: [COMMITMENTS] Main priorities: [PRIORITIES] People who request my time: [REQUESTERS] Common request types: [REQUEST TYPES] Where I overcommit: [OVERCOMMITMENT] Where I feel guilty saying no: [GUILT] Deadlines: [DEADLINES] Communication style: [STYLE] Relationship constraints: [CONSTRAINTS] Build the commitment firewall: A. Commitment audit Classify commitments as: - essential - strategic - maintenance - optional - inherited - outdated - unclear - emotional obligation - renegotiate - stop B. Acceptance criteria Create rules for accepting work based on: - goal alignment - time cost - energy cost - opportunity cost - deadline realism - hidden work - relationship impact - repeat risk - trust impact C. Boundary scripts Write scripts for: - saying no - saying yes with conditions - asking for more time - declining a meeting - renegotiating a deadline - redirecting a request - pausing a project - protecting a focus block - communicating overload D. Capacity limits Recommend practical limits for: - active projects - meetings per day - deep work blocks per week - urgent requests - response windows - weekly commitments E. Overcommitment recovery Create a recovery plan: - identify overload - choose what to renegotiate - communicate quickly - reset timeline - rebuild trust - prevent repeat overload Rules: - Do not make boundaries rude. - Do not ignore relationship context. - Do not pretend capacity is unlimited. - Boundaries should protect both execution and trust. --------------------------------------------------------------------------------

#012Goal-to-System Converter

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople with big ambitions who need an execution system instead of vague motivation.

Convert goals into weekly actions, habits, metrics, milestones, review loops, and recovery rules.

Act as a goal execution architect. Convert my goals into systems that create progress every week. Goals: [PASTE GOALS] Context: Time horizon: [TIME HORIZON] Why these goals matter: [WHY] Current baseline: [BASELINE] Available time: [TIME] Constraints: [CONSTRAINTS] Resources: [RESOURCES] Skills needed: [SKILLS] Current habits: [HABITS] Risks: [RISKS] Create the conversion: 1. Goal clarification For each goal define: - outcome - success metric - deadline or horizon - current baseline - required behavior - required resources - likely obstacle 2. System components For each goal create: - weekly action - minimum viable action - progress metric - habit trigger - review cadence - accountability method - failure recovery rule 3. Milestone ladder Break each goal into: - 90-day milestone - 30-day milestone - weekly target - next action - first 15-minute step 4. Failure prevention Identify: - where procrastination will appear - where motivation will drop - where the system may be too hard - where ambiguity will slow progress - where support may be needed 5. Operating dashboard Create a simple dashboard with: - goal - system - metric - weekly action - next review - warning signal - adjustment rule Rules: - Do not confuse goals with tasks. - Do not rely on motivation. - Do not create habits that are too large to start. - The final system must work on average weeks, not only ideal weeks. --------------------------------------------------------------------------------

#013Review Loop Designer

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who start systems but fail to maintain them, repeat the same mistakes, or never close feedback loops.

Create daily, weekly, monthly, and quarterly review rituals that improve planning, execution, learning, and system maintenance.

You are a review loop designer. Build a lightweight review system that helps me learn from execution and improve my operating system over time. Context: Goals: [GOALS] Projects: [PROJECTS] Current planning method: [METHOD] Current review habit: [REVIEW HABIT] What I often miss: [MISSES] What I want to improve: [IMPROVEMENTS] Available review time: [TIME] Tools: [TOOLS] Preferred style: [SHORT / DETAILED] Build the review loop: A. Daily review Create a 5 to 10 minute shutdown review: - what moved forward - what did not - what changed - what must be captured - what tomorrow starts with - what can be released B. Weekly review Create a 30 to 60 minute review: - outcomes completed - priorities missed - project status - tasks carried over - decisions made - bottlenecks - energy patterns - next week priorities C. Monthly review Create a monthly system check: - goal progress - project load - habits - tools - boundaries - recurring friction - lessons - system changes D. Quarterly review Create a deeper reset: - direction - goals - commitments - capacity - identity and work style - stop list - next quarter operating principles E. Review templates Provide copyable templates for each review. Rules: - Do not make review longer than useful. - Do not turn review into self-criticism. - Do not track data that does not improve decisions. - Reviews should create better choices, not more guilt. --------------------------------------------------------------------------------

#014Distraction Autopsy

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who lose time to phone use, tabs, messages, procrastination, emotional loops, or avoidance behaviors.

Analyze recurring distractions and design practical prevention, replacement, and recovery strategies.

Act as a distraction investigator. Perform an autopsy on my recurring distractions and design a realistic prevention system. My distractions: Common distractions: [DISTRACTIONS] When they happen: [WHEN] What I am usually avoiding: [AVOIDING] Devices / apps involved: [DEVICES / APPS] Emotional triggers: [TRIGGERS] Work environment: [ENVIRONMENT] Important work affected: [AFFECTED WORK] Current attempts to fix it: [ATTEMPTS] Investigate: 1. Distraction profile For each distraction identify: - trigger - immediate reward - underlying need - task being avoided - cost - frequency - controllability - replacement behavior 2. Avoidance map Identify if distractions come from: - unclear task - fear of failure - boredom - fatigue - lack of deadline - too many options - emotional stress - perfectionism - environment - habit loop 3. Prevention design Create prevention rules for: - phone - email - chat - browser tabs - social media - meetings - environment - unclear tasks - emotional loops 4. Replacement behaviors Create replacements for: - 30 seconds - 2 minutes - 10 minutes - low-energy state - anxious state - bored state - stuck state 5. Recovery protocol Create a reset for when I get distracted: - notice - name the trigger - reduce the task - remove friction - restart timer - capture open loop - continue or intentionally stop Rules: - Do not shame the distraction. - Do not recommend unrealistic total avoidance. - Do not ignore the emotional reason behind the behavior. - The system should make focus easier by design. --------------------------------------------------------------------------------

#015Personal Knowledge Operating Map

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMWriters, creators, founders, researchers, consultants, students, and professionals with scattered notes and hard-to-find information.

Build a simple system for organizing notes, ideas, references, decisions, templates, and reusable knowledge.

You are a personal knowledge systems designer. Create a practical knowledge operating map that helps me store and retrieve useful information. My context: Types of information I save: [INFO TYPES] Current tools: [TOOLS] Where notes are scattered: [LOCATIONS] How I use notes: [USE CASES] Biggest retrieval problem: [PROBLEM] Projects supported: [PROJECTS] Preferred organization style: [STYLE] Maintenance time available: [TIME] Build the map: A. Information taxonomy Classify information into: - active project notes - reference material - ideas - decisions - meeting notes - templates - checklists - research - learning notes - personal reminders - archive B. Storage rules For each category define: - where it goes - naming rule - when to tag - when to link - when to summarize - when to archive - when to delete C. Capture workflow Create workflows for: - quick idea - meeting note - research link - screenshot - decision - reusable template - learning note - project note D. Retrieval system Design: - search rules - folder structure - tags, if useful - index page - project links - weekly cleanup - archive process E. Maintenance ritual Create: - daily capture cleanup - weekly note review - monthly archive cleanup - project closeout checklist - template improvement loop Rules: - Do not design a complex second brain unless necessary. - Do not organize for aesthetics. - Do not keep everything. - The system should make useful information easier to apply. --------------------------------------------------------------------------------

#016Reset Protocol Builder

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople recovering from chaotic weeks, missed deadlines, illness, travel, burnout, procrastination, or system breakdown.

Create a recovery plan for when tasks pile up, deadlines slip, routines break, or you feel behind.

Act as a productivity recovery coach. Build a reset protocol that gets me back in control without panic or shame. Current situation: What fell behind: [FELL BEHIND] Missed deadlines: [MISSED DEADLINES] Current task pile: [TASKS] Current emotional state: [STATE] Upcoming obligations: [OBLIGATIONS] Available time today: [TIME TODAY] Available time this week: [TIME WEEK] People affected: [PEOPLE] What I am avoiding: [AVOIDING] Build the reset: 1. Stabilization triage Sort everything into: - urgent and important - important but not urgent - communication needed - renegotiate deadline - delete - defer - delegate - emotional clutter - unclear 2. Damage control Create actions for: - missed deadlines - people waiting on me - commitments I cannot meet - projects that slipped - decisions I avoided - tasks that no longer matter 3. 24-hour plan Create a plan with: - first 15 minutes - first hour - communication block - priority block - admin cleanup - shutdown ritual 4. 7-day recovery Create: - daily focus - minimum viable progress - tasks to clear - commitments to renegotiate - energy protection - review points 5. Prevention upgrade Identify why the system broke and recommend: - new rule - boundary - planning change - early warning signal - capacity limit - reset trigger Rules: - Do not tell me to catch up on everything. - Do not create a punishment plan. - Do not ignore communication repair. - The reset should restore clarity, trust, and motion. --------------------------------------------------------------------------------

#017Communication and Meeting Operating Policy

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople whose productivity is damaged by constant communication, unclear expectations, too many meetings, or reactive availability.

Create rules for meetings, email, chat, response times, availability, updates, and interruption management.

You are a communication systems strategist. Build a communication policy that protects focus while keeping collaboration reliable. My communication context: Channels used: [CHANNELS] Meeting load: [MEETING LOAD] Response expectations: [EXPECTATIONS] People I work with: [PEOPLE] Common interruptions: [INTERRUPTIONS] Important focus work: [FOCUS WORK] Current problems: [PROBLEMS] Role constraints: [CONSTRAINTS] Preferred communication style: [STYLE] Design the policy: A. Channel roles Define what each channel is for: - email - chat - meetings - calls - documents - task manager - calendar - voice notes, if used For each include: - purpose - response time - what not to use it for - escalation rule B. Meeting rules Create rules for: - when to accept a meeting - when to decline - when to ask for agenda - meeting length - meeting-free blocks - follow-up notes - decision meetings - status meetings C. Response system Create response windows for: - urgent messages - normal messages - low-priority messages - deep work days - travel or busy days - off-hours messages D. Scripts Write scripts for: - declining a meeting - asking for agenda - moving chat to async - setting response expectations - protecting a focus block - escalating a real emergency - requesting decisions in writing E. Weekly communication review Create a review for: - missed messages - unresolved follow-ups - unnecessary meetings - recurring interruptions - policy adjustments Rules: - Do not make me unreachable. - Do not ignore collaboration needs. - Do not treat every message as urgent. - Communication should support work instead of replacing it. --------------------------------------------------------------------------------

#018Productivity Dashboard Builder

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who need one clear place to see what matters without overbuilding a productivity app.

Design a visible dashboard for priorities, projects, tasks, decisions, deadlines, risks, and weekly progress.

Act as a productivity dashboard designer. Build a simple dashboard that helps me see the state of my work in under 5 minutes. Inputs: Goals: [GOALS] Projects: [PROJECTS] Tasks: [TASKS] Deadlines: [DEADLINES] Recurring work: [RECURRING WORK] Current tools: [TOOLS] Metrics I care about: [METRICS] Visibility problems: [VISIBILITY PROBLEMS] Preferred style: [SIMPLE / DETAILED / VISUAL] Create the dashboard: 1. Dashboard purpose Define what the dashboard must show: - what matters now - what is due soon - what is stuck - what needs a decision - what needs communication - what is over capacity - what progress looks like 2. Dashboard sections Design sections for: - weekly priorities - active projects - today - waiting-for - decisions - deadlines - risks - recurring work - review notes For each section include: - fields - update frequency - example entry - decision it supports 3. Status labels Create a simple status system: - active - next - waiting - blocked - scheduled - paused - done - review 4. Dashboard workflow Explain how to use it: - morning check - midday adjustment - end-of-day update - weekly review - monthly cleanup 5. Copyable template Provide a plain-text dashboard template I can paste into any tool. Rules: - Do not track things that do not change behavior. - Do not create too many statuses. - Do not require constant maintenance. - The dashboard should increase clarity, not admin work. --------------------------------------------------------------------------------

#019Personal Workflow Automation Finder

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMPeople who repeat the same admin, communication, planning, reporting, writing, or follow-up work every week.

Identify work that can be simplified, templated, batched, delegated, scheduled, or automated.

You are a personal workflow automation auditor. Find opportunities to reduce repeated work and mental load. My recurring workflow: Recurring tasks: [RECURRING TASKS] Manual admin: [ADMIN] Repeated decisions: [REPEATED DECISIONS] Documents I create often: [DOCUMENTS] Messages I send often: [MESSAGES] Reports / updates: [REPORTS] Tools I use: [TOOLS] Things I forget: [FORGET] Tasks I dislike: [DISLIKE] Automation comfort level: [LOW / MEDIUM / HIGH] Audit the workflow: A. Repetition inventory Identify repeated work across: - planning - scheduling - communication - reporting - task creation - file organization - reminders - follow-ups - writing - research - admin - personal routines B. Simplification type Classify each item as: - eliminate - simplify - template - checklist - batch - calendar block - delegate - automate - standard operating procedure - decision rule C. Impact-effort score Score each opportunity on: - time saved - mental load saved - error reduction - setup effort - maintenance effort - risk - priority D. Design the top 10 improvements For each include: - trigger - input - process - output - tool needed - human review point - failure mode - fallback E. Implementation plan Create: - first 3 quick wins - 7-day setup plan - 30-day improvement plan - what not to automate - review cadence Rules: - Do not automate a broken process before simplifying it. - Do not recommend tools without explaining the workflow. - Do not automate judgment-heavy decisions. - The goal is less friction, not a more complex system. --------------------------------------------------------------------------------

#020Full Productivity Strategy Audit

PRODUCTIVITY STRATEGY & PERSONAL OPERATING SYSTEMComplete productivity resets, annual or quarterly planning, overloaded professionals, solo operators, founders, creators, students, and executives.

Audit and redesign your full productivity strategy across goals, priorities, planning, tasks, projects, focus, energy, tools, communication, and review loops.

Act as an independent productivity strategist. Audit my entire personal operating system and redesign it for repeatable execution. Full context: Role / work: [ROLE] Main goals: [GOALS] Current projects: [PROJECTS] Current task list: [TASKS] Current calendar: [CALENDAR] Current tools: [TOOLS] Current routines: [ROUTINES] Responsibilities: [RESPONSIBILITIES] Biggest problems: [PROBLEMS] Energy patterns: [ENERGY] Distractions: [DISTRACTIONS] Commitments: [COMMITMENTS] What I tried before: [TRIED] Desired working style: [DESIRED STYLE] Audit across 30 dimensions: 1. Goal clarity 2. Priority clarity 3. Project visibility 4. Task capture 5. Task clarity 6. Calendar design 7. Weekly planning 8. Daily planning 9. Deep work 10. Attention protection 11. Communication boundaries 12. Meeting load 13. Energy alignment 14. Recovery 15. Overcommitment 16. Decision-making 17. Follow-up tracking 18. Knowledge organization 19. Tool simplicity 20. Automation potential 21. Review rhythm 22. Deadline management 23. Procrastination patterns 24. Context switching 25. Admin batching 26. Personal commitments 27. Work-life boundaries 28. Reset protocol 29. Sustainability 30. System usability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then create: A. Hard truth Explain the biggest reason my current system is not working. B. Redesigned operating system Include: - operating principles - priority hierarchy - project dashboard - task system - calendar rules - weekly planning ritual - daily execution ritual - deep work rules - communication rules - energy rules - reset protocol - review loop C. Tool structure Recommend the simplest setup for: - tasks - calendar - notes - projects - reminders - reviews D. Implementation roadmap Create: - first 24 hours - first 7 days - first 30 days - first 90 days - what to stop doing - what to protect - what to measure E. Executive summary Write: - strongest part of my current system - weakest part - highest-leverage fix - first action today - rule to follow when everything becomes chaotic Rules: - Do not give generic advice. - Do not recommend a complex system if a simple one works. - Do not ignore constraints, energy, or real responsibilities. - Use [LOW CONFIDENCE] where information is missing. - Optimize for clarity, sustainability, and execution. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- GOAL SETTING, PRIORITIES & DECISION FILTERS

#021Meaningful Goal Excavator

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople who have many possible goals, feel pulled in different directions, or want goals that are not just copied from other people's definitions of success.

Turn vague wishes, pressure-driven ambitions, and scattered ideas into clear goals that are specific, meaningful, realistic, and connected to your actual direction.

You are a goal clarity strategist. Help me turn unclear ambitions into meaningful goals that I can actually commit to and execute. My raw goals or wishes: [PASTE RAW GOALS / IDEAS / DESIRES] Context: Current life or work stage: [STAGE] Main responsibilities: [RESPONSIBILITIES] What I want more of: [MORE OF] What I want less of: [LESS OF] Current frustrations: [FRUSTRATIONS] Long-term direction: [DIRECTION] Time horizon: [TIME HORIZON] Constraints: [CONSTRAINTS] Available energy and time: [TIME / ENERGY] Goals I feel pressured to pursue: [PRESSURE GOALS] Goals that genuinely matter to me: [GENUINE GOALS] Excavate the goals: 1. Goal cleanup Separate my inputs into: - real goals - vague desires - external expectations - emotional reactions - maintenance needs - avoidance goals - identity goals - outcome goals - habit goals - unclear items For each item explain: - what it really means - whether it deserves attention - what needs clarification 2. Meaning test For each possible goal, evaluate: - why it matters - who benefits - what changes if I achieve it - what happens if I ignore it - whether it matches my long-term direction - whether it is chosen or inherited - whether I have enough capacity for it 3. Goal rewrite Rewrite each strong goal into this format: - goal statement - success definition - time horizon - reason - first milestone - leading behavior - risk - boundary 4. Goal shortlist Choose: - 1 primary goal - 2 supporting goals - 3 maintenance goals - goals to pause - goals to reject - goals to revisit later 5. Commitment check For each selected goal answer: - what am I willing to do? - what am I not willing to do? - what tradeoff is required? - what must be protected? - what would make this goal unrealistic? Rules: - Do not make every idea into a goal. - Do not create goals that ignore my real constraints. - Do not use motivational language without operational clarity. - The final goals should feel chosen, specific, and executable. --------------------------------------------------------------------------------

#022North Star to Next Action Ladder

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople who know the direction they want but struggle to translate it into concrete execution.

Convert a long-term direction into annual goals, quarterly priorities, monthly milestones, weekly outcomes, and daily next actions.

Act as a goal decomposition architect. Build a ladder from my long-term direction down to the next action I should take today. North Star direction: [NORTH STAR / LONG-TERM DIRECTION] Context: Time horizon: [TIME HORIZON] Current starting point: [STARTING POINT] Available time per week: [TIME] Main projects: [PROJECTS] Constraints: [CONSTRAINTS] Skills or resources needed: [SKILLS / RESOURCES] Risks: [RISKS] What success should look like: [SUCCESS] What failure would look like: [FAILURE] Build the ladder: A. Direction translation Translate the North Star into: - 3-year direction - 1-year outcome - 90-day focus - 30-day milestone - weekly outcome - daily action B. Milestone logic For each level define: - outcome - why this level matters - measurable signal - required behavior - required decision - dependency - risk C. Reverse engineering Work backward from the desired outcome and identify: - what must be true by the end - what must be true halfway - what must be true in the first month - what must happen this week - what must happen today D. Execution ladder Create a practical ladder: Step 1: Step 2: Step 3: Step 4: Step 5: For each step include: - action - estimated effort - expected output - success criterion - blocker to watch E. First move Give me: - first 15-minute action - first 60-minute action - first weekly commitment - first review question - first thing to stop doing Rules: - Do not skip from vision to vague tasks. - Do not create milestones that cannot be observed. - Do not assume unlimited time. - The final ladder should make the next action obvious. --------------------------------------------------------------------------------

#023Priority Stack Ranker

GOAL SETTING, PRIORITIES & DECISION FILTERSOverloaded people with too many tasks, active projects, competing deadlines, or unclear priorities.

Rank goals, projects, and tasks in a clear order using impact, urgency, energy, strategic value, risk, and opportunity cost.

You are a ruthless but practical priority ranker. Help me decide what deserves attention now, what can wait, and what should be removed. Items to rank: [PASTE GOALS / PROJECTS / TASKS] Context: Main objective: [OBJECTIVE] Time available: [TIME] Energy available: [ENERGY] Deadlines: [DEADLINES] Dependencies: [DEPENDENCIES] People affected: [PEOPLE] Long-term direction: [DIRECTION] Current stress points: [STRESS] Non-negotiables: [NON-NEGOTIABLES] Rank the priorities: 1. Scoring model Score each item from 1 to 5 on: - strategic impact - urgency - revenue or outcome value - personal importance - risk reduction - dependency impact - effort required - energy match - deadline pressure - opportunity cost if ignored 2. Weighted decision Create a weighted score where: - strategic impact matters most - urgency matters only if real - effort reduces priority if capacity is low - energy mismatch changes scheduling, not importance - dependencies can increase priority Show the final score and rank. 3. Priority groups Sort items into: - do now - schedule this week - delegate or automate - defer - delete - clarify before deciding - protect as deep work - batch as admin 4. Tradeoff explanation For the top 10 items explain: - why it ranks there - what it beats - what it loses to - what happens if delayed - what the next action is 5. Final action order Give me: - top 3 priorities - next 5 actions - tasks to ignore today - tasks to renegotiate - decision I need to make now Rules: - Do not rank by urgency alone. - Do not let easy tasks outrank important work. - Do not keep unclear tasks active. - The ranking must produce a real execution order. --------------------------------------------------------------------------------

#024Strategic Tradeoff Decision Board

GOAL SETTING, PRIORITIES & DECISION FILTERSChoosing between two or more serious options when every option has benefits and costs.

Make difficult tradeoffs between goals, opportunities, projects, time commitments, and competing priorities.

Act as a strategic decision board. Help me compare options and choose based on long-term direction, impact, capacity, risk, and tradeoffs. Decision to make: [DECISION] Options: [OPTION A] [OPTION B] [OPTION C, IF ANY] Context: Long-term direction: [DIRECTION] Current priorities: [PRIORITIES] Time and energy capacity: [CAPACITY] Constraints: [CONSTRAINTS] Risks: [RISKS] Upside potential: [UPSIDE] Downside potential: [DOWNSIDE] People affected: [PEOPLE] Deadline to decide: [DEADLINE] Run the decision board: A. Option profile For each option identify: - what it is - what it requires - expected upside - hidden cost - required tradeoff - time cost - energy cost - opportunity cost - reversibility - risk level B. Decision lenses Evaluate every option through these lenses: - alignment with direction - impact on current goals - impact on future optionality - capacity fit - risk exposure - learning value - compounding value - emotional pull - urgency reality - cost of saying yes C. Tradeoff map Create a table: - if I choose this, I gain - if I choose this, I lose - if I delay this, I risk - if I reject this, I preserve - if I test this, the smallest test is D. Recommendation Give: - best choice - second-best choice - choice to reject - minimum viable test, if useful - what would change the recommendation E. Decision script Write the final decision as: I choose [X] because... I am intentionally not choosing [Y] because... I will review this decision on [DATE / TIMEFRAME]. The first action is... Rules: - Do not pretend there is a perfect option. - Do not ignore capacity. - Do not choose the emotionally exciting option without checking cost. - Make the tradeoff explicit. --------------------------------------------------------------------------------

#025Opportunity Filter Builder

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople who get distracted by new opportunities, overcommit, or struggle to decide whether something is worth attention.

Create a personal filter for evaluating new ideas, requests, collaborations, projects, purchases, meetings, and opportunities before saying yes.

You are an opportunity filter designer. Build a decision filter that helps me decide whether to accept, reject, delay, test, or renegotiate new opportunities. Opportunity: [DESCRIBE OPPORTUNITY] My context: Current goals: [GOALS] Current priorities: [PRIORITIES] Available time: [TIME] Available energy: [ENERGY] Financial or career context: [CONTEXT] Current commitments: [COMMITMENTS] Long-term direction: [DIRECTION] Things I am trying to avoid: [AVOID] Decision deadline: [DEADLINE] Build and apply the filter: 1. Opportunity decode Identify: - what the opportunity really is - who benefits - what it requires - why it is attractive - what is unclear - what hidden work may exist - what emotional trigger it activates 2. Filter questions Create 15 yes/no questions across: - alignment - impact - urgency - capacity - energy - money - learning - relationship value - compounding potential - opportunity cost - risk - reversibility - timing - maintenance burden - regret 3. Scoring Score the opportunity: - strong yes - yes with conditions - small test - not now - no Explain the score. 4. Conditions and boundaries If yes, define: - scope - deadline - success condition - time limit - communication boundary - exit condition - review date 5. Response scripts Write scripts for: - accepting - accepting with conditions - asking for clarification - suggesting a small test - delaying - saying no politely Rules: - Do not treat every good opportunity as a good fit. - Do not ignore timing. - Do not recommend yes without conditions if capacity is limited. - The filter should protect focus without closing every door. --------------------------------------------------------------------------------

#026Saying No and Not-Now Script System

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople who struggle to say no, feel guilty setting boundaries, or lose focus to other people's priorities.

Build clear, respectful scripts and decision rules for declining requests, postponing opportunities, renegotiating commitments, and protecting priorities.

Act as a boundary communication strategist. Help me say no, not now, or yes with limits while protecting trust and relationships. Request or situation: [PASTE REQUEST / SITUATION] Context: Who is asking: [PERSON / RELATIONSHIP] What they want: [REQUEST] Why I may want to say yes: [YES REASON] Why I should not say yes fully: [LIMITS] Current priorities: [PRIORITIES] Capacity: [CAPACITY] Relationship importance: [RELATIONSHIP] Tone needed: [TONE] Alternative I can offer: [ALTERNATIVE] Create the response system: A. Request analysis Identify: - real ask - hidden ask - time cost - energy cost - priority conflict - relationship risk - trust risk - whether this needs no, not now, or yes with boundaries B. Boundary choice Recommend one of: - clear no - not now - yes, but smaller - yes, but later - yes, if conditions are met - redirect to someone else - ask for clarification - renegotiate scope Explain why. C. Script library Write 12 scripts: - short no - warm no - professional no - no with reason - no without overexplaining - not now - yes with scope limit - yes with time limit - yes with tradeoff - renegotiate deadline - decline meeting - redirect request D. Follow-up handling Prepare responses if they: - push back - ask why - offer urgency - guilt-trip - reduce the ask - ask again later E. Personal rule Create a rule I can use before responding to similar requests. Rules: - Do not make the message rude. - Do not over-explain. - Do not apologize excessively. - The script should protect both priorities and relationships. --------------------------------------------------------------------------------

#027Impact-Urgency-Energy Matrix

GOAL SETTING, PRIORITIES & DECISION FILTERSDaily and weekly planning, overloaded task lists, low-energy days, high-pressure weeks, and priority sorting.

Decide what to do based not only on urgency and importance, but also energy fit, cognitive load, emotional resistance, and timing.

You are a task triage strategist. Sort my task list using impact, urgency, energy, and timing so I know what to do, when to do it, and what to avoid. Task list: [PASTE TASKS] Context: Today or week: [TIMEFRAME] Available time: [TIME] Current energy level: [ENERGY] Deadlines: [DEADLINES] Main goal: [MAIN GOAL] Meetings or obligations: [OBLIGATIONS] Tasks I am avoiding: [AVOIDED TASKS] Tasks that require deep focus: [DEEP TASKS] Build the matrix: 1. Task scoring For each task score 1 to 5: - impact - urgency - energy required - cognitive load - emotional resistance - time required - dependency value - deadline pressure 2. Matrix placement Place tasks into: - high impact / high urgency / high energy - high impact / low urgency / high energy - high impact / low energy required - low impact / high urgency - low impact / low urgency - emotionally heavy - quick wins - batch tasks - defer tasks - delete tasks 3. Schedule recommendation Assign tasks to: - peak energy block - medium energy block - low energy block - admin batch - communication batch - later this week - not this week 4. Resistance handling For avoided tasks, identify: - why I may be avoiding it - smallest next action - setup needed - completion trigger - accountability option 5. Final plan Create: - top 1 mission - top 3 tasks - low-energy backup list - tasks to avoid today - shutdown task Rules: - Do not assign hard thinking to low-energy windows. - Do not let urgent low-impact work consume the whole day. - Do not ignore emotional resistance. - The final plan should be realistic for my current energy. --------------------------------------------------------------------------------

#028Long-Term Direction Compass

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople who want fewer random priorities and a stronger connection between daily work and long-term strategy.

Create a decision compass that helps you judge goals, tasks, opportunities, and commitments against your long-term direction.

Act as a long-term direction strategist. Build a compass I can use to decide what deserves attention and what does not. My long-term direction: [DESCRIBE DIRECTION] Context: Values: [VALUES] Desired future: [DESIRED FUTURE] Current goals: [GOALS] Current projects: [PROJECTS] Current obligations: [OBLIGATIONS] What I am trying to stop doing: [STOP] What I am trying to build: [BUILD] Time horizon: [TIME HORIZON] Constraints: [CONSTRAINTS] Build the compass: A. Direction statement Rewrite my direction into: - one-sentence direction - 3 supporting themes - 5 strategic principles - 5 things I am no longer optimizing for - 5 things I am protecting B. Decision compass Create 10 decision questions. Each question should help me test whether a goal, opportunity, or task: - moves me toward the direction - distracts me - creates compounding value - protects capacity - matches values - deserves urgency - builds skill - creates future optionality - reduces unnecessary complexity - should be rejected C. Alignment scoring Build a scorecard from 1 to 5 for: - direction fit - values fit - time horizon fit - capacity fit - compounding potential - regret risk - distraction risk D. Application examples Apply the compass to: - a new project - a meeting request - a learning opportunity - a personal commitment - a low-impact task - a tempting distraction E. Final compass card Create a short card I can review weekly: - direction - filters - yes criteria - no criteria - weekly reflection questions Rules: - Do not make the compass vague or inspirational only. - Do not ignore current responsibilities. - Do not make long-term direction an excuse to avoid short-term obligations. - The compass should guide real decisions. --------------------------------------------------------------------------------

#029Task Triage Emergency Room

GOAL SETTING, PRIORITIES & DECISION FILTERSOverwhelming days, deadline weeks, post-vacation catchup, project overload, and urgent priority resets.

Quickly triage a chaotic task list when there is limited time, high pressure, missed deadlines, or too many competing demands.

You are a task triage emergency room. Help me stabilize my workload quickly and decide what needs immediate action, communication, delay, or deletion. Current task pile: [PASTE TASKS / DEADLINES / OPEN LOOPS] Context: Available time today: [TIME TODAY] Available time this week: [TIME WEEK] Hard deadlines: [DEADLINES] People waiting on me: [PEOPLE] Current energy: [ENERGY] Consequences of delay: [CONSEQUENCES] Main priority: [MAIN PRIORITY] What feels most overwhelming: [OVERWHELM] Run emergency triage: 1. Stabilize Sort everything into: - must do today - must communicate today - must schedule - can wait - can be reduced - can be delegated - can be deleted - unclear but important - emotional noise 2. Consequence scan For every urgent-looking item identify: - real consequence if delayed - perceived consequence - person affected - deadline truth - minimum acceptable action 3. Emergency execution order Build an execution order for today: 1. 2. 3. 4. 5. For each include: - action - time box - success criterion - stop rule - communication needed 4. Communication repair Write messages for: - delay notice - request for extension - status update - scope reduction - quick clarification - handoff 5. Recovery plan Create: - next 24-hour plan - next 3-day plan - tasks to revisit after stabilization - system fix to prevent repeat overload Rules: - Do not tell me to finish everything. - Do not ignore communication. - Do not let shame drive the plan. - The goal is stabilization, not perfection. --------------------------------------------------------------------------------

#030Goal Pressure Test Lab

GOAL SETTING, PRIORITIES & DECISION FILTERSQuarterly planning, annual planning, career goals, business goals, personal projects, and major commitments.

Stress-test goals before committing to them by checking clarity, motivation, feasibility, tradeoffs, risks, metrics, and execution path.

Act as a goal pressure tester. Challenge my goal before I commit to it, then make it stronger if it survives. Goal: [GOAL] Context: Why I want it: [WHY] Time horizon: [TIME HORIZON] Current baseline: [BASELINE] Success metric: [METRIC] Available time: [TIME] Available resources: [RESOURCES] Constraints: [CONSTRAINTS] Competing priorities: [COMPETING PRIORITIES] Risks: [RISKS] Motivation level: [MOTIVATION] Pressure test the goal: A. Clarity test Check whether the goal is: - specific - measurable - meaningful - realistic - time-bound - behavior-linked - within influence - aligned with direction B. Feasibility test Evaluate: - time required - energy required - skill required - money required - support required - opportunity cost - current capacity fit - risk of burnout C. Tradeoff test Answer: - what must I stop doing? - what must I say no to? - what will become harder? - what will improve? - what is the cost of success? - what is the cost of failure? D. Failure pre-mortem Imagine the goal failed. Identify: - most likely reason - early warning signs - prevention rule - recovery plan - decision point to adjust E. Stronger version Rewrite the goal into: - original version - improved version - minimum viable version - stretch version - weekly behavior - first action Rules: - Do not approve a weak goal. - Do not make the goal larger just to sound ambitious. - Do not ignore tradeoffs. - A goal should earn commitment before it receives time. --------------------------------------------------------------------------------

#031Project Portfolio Pruner

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople with too many active projects, unfinished initiatives, scattered attention, and unclear project value.

Review all active projects and decide what to continue, pause, simplify, delegate, merge, finish, or eliminate.

You are a project portfolio pruner. Help me reduce the number of active projects and focus on the ones that matter most. Project portfolio: [PASTE PROJECTS] Context: Main goals: [GOALS] Time available per week: [TIME] Energy available: [ENERGY] Deadlines: [DEADLINES] Financial or strategic stakes: [STAKES] Current bottlenecks: [BOTTLENECKS] Projects I feel attached to: [ATTACHED PROJECTS] Projects I avoid: [AVOIDED PROJECTS] Prune the portfolio: 1. Project card creation For each project create a card with: - desired outcome - current status - next action - effort remaining - strategic value - deadline - owner - dependency - risk - reason it exists 2. Portfolio scoring Score each project on: - goal alignment - impact - urgency - momentum - cost to maintain - cognitive load - revenue or value potential - learning value - completion probability 3. Portfolio decisions Assign each project to: - continue now - finish quickly - pause - merge - simplify - delegate - delete - convert to someday - clarify before deciding 4. Attention budget Create a realistic active project limit. Recommend: - maximum active projects - maximum side projects - maximum maintenance projects - review cadence - project entry criteria - project exit criteria 5. Pruning plan Create: - projects to protect - projects to close - projects to communicate about - first 5 next actions - weekly project review template Rules: - Do not keep projects active because of guilt. - Do not ignore sunk cost. - Do not allow every project to remain open. - The output should reduce cognitive load immediately. --------------------------------------------------------------------------------

#032Weekly Priority Negotiator

GOAL SETTING, PRIORITIES & DECISION FILTERSWeekly planning when priorities compete and not everything can fit.

Build a weekly plan by negotiating between goals, deadlines, obligations, energy, people, and available time.

Act as a weekly priority negotiator. Help me decide what this week can realistically hold and what must be cut, moved, or renegotiated. Inputs for the week: Goals: [GOALS] Deadlines: [DEADLINES] Tasks: [TASKS] Projects: [PROJECTS] Meetings: [MEETINGS] Personal obligations: [OBLIGATIONS] Available work hours: [HOURS] Energy forecast: [ENERGY] People waiting on me: [PEOPLE] Known disruptions: [DISRUPTIONS] Negotiate the week: A. Capacity reality check Calculate: - total available focus time - admin time - meeting time - recovery time - buffer time - realistic task capacity - overload risk B. Priority negotiation For every major item determine: - does it fit this week? - what must move if this stays? - what is the minimum viable version? - what needs communication? - what can be batched? - what can be delayed? C. Weekly outcome selection Choose: - one main outcome - two secondary outcomes - maintenance commitments - optional stretch items - no-go list D. Schedule allocation Create a week plan with: - focus blocks - admin blocks - communication blocks - meeting buffers - recovery windows - deadline protection - catch-up buffer E. Negotiation scripts Write scripts for: - moving a deadline - reducing scope - declining a meeting - asking for clarification - explaining priority tradeoff Rules: - Do not create a fantasy week. - Do not fit more work than capacity allows. - Do not ignore personal obligations. - The week should be planned around realistic execution, not wishful thinking. --------------------------------------------------------------------------------

#033Attention Eligibility Filter

GOAL SETTING, PRIORITIES & DECISION FILTERSReducing reactive work, protecting focus, managing inputs, and deciding what not to engage with.

Decide whether an idea, task, message, request, or problem deserves attention now, later, or not at all.

You are an attention gatekeeper. Help me decide what deserves my attention and what should be ignored, batched, delegated, delayed, or deleted. Input competing for attention: [PASTE INPUT / TASK / REQUEST / IDEA / PROBLEM] Context: Current focus: [CURRENT FOCUS] Top goals: [GOALS] Available attention today: [ATTENTION] Deadline pressure: [DEADLINES] Emotional pull: [EMOTIONAL PULL] Consequences of ignoring: [CONSEQUENCES] People affected: [PEOPLE] Long-term relevance: [RELEVANCE] Apply the attention filter: 1. Attention classification Classify the input as: - urgent and real - important but not urgent - noisy but harmless - distracting opportunity - emotional trigger - maintenance task - future idea - someone else's priority - unclear input - delete 2. Eligibility questions Answer: - does this affect my top goals? - does this have a real deadline? - does this require my unique attention? - can it be batched? - can it wait? - can someone else handle it? - what happens if I ignore it for 24 hours? - what is the smallest responsible response? 3. Routing decision Choose one route: - do now - schedule - batch - delegate - respond briefly - capture for later - decline - ignore - delete - clarify 4. Response or action Provide: - next action - time box - communication script, if needed - review date, if later - stop condition 5. Filter rule Create a reusable rule for similar inputs. Rules: - Do not treat emotional urgency as real urgency without checking. - Do not give attention to everything that arrives. - Do not ignore real obligations. - The goal is attention discipline, not avoidance. --------------------------------------------------------------------------------

#034Goal Conflict Resolver

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople with ambitious goals that cannot all be pursued at the same intensity at the same time.

Resolve conflicts between multiple goals that compete for time, identity, money, energy, relationships, or strategic direction.

Act as a goal conflict mediator. Help me identify conflicts between my goals and decide how to sequence, combine, reduce, or choose between them. Goals in conflict: [PASTE GOALS] Context: Time horizon: [TIME HORIZON] Current capacity: [CAPACITY] Main responsibilities: [RESPONSIBILITIES] Resources: [RESOURCES] Constraints: [CONSTRAINTS] Values: [VALUES] Long-term direction: [DIRECTION] What feels hard to choose: [HARD CHOICE] Resolve the conflict: A. Conflict map Identify conflicts across: - time - energy - money - attention - identity - relationships - deadlines - skill development - emotional load - opportunity cost B. Goal compatibility For each goal pair, classify: - compatible - compatible with sequencing - compatible with reduced scope - competing - mutually exclusive for now - unclear Explain why. C. Resolution options Create options: - choose one goal - sequence goals - reduce one goal - merge goals - create a maintenance version - set a temporary focus season - postpone - drop D. Decision recommendation Recommend: - primary goal - secondary goal - maintenance goal - paused goal - dropped goal - review date E. Execution agreement Create an agreement: For the next [TIMEFRAME], I will focus on... I will not pursue... I will maintain... I will revisit... I will know this was the right choice if... Rules: - Do not pretend all goals can be equal. - Do not force permanent decisions when sequencing works. - Do not ignore emotional attachment. - Conflict resolution should create relief and focus. --------------------------------------------------------------------------------

#03590-Day Focus Sprint Designer

GOAL SETTING, PRIORITIES & DECISION FILTERSQuarterly planning, business goals, personal projects, habit goals, creative projects, and major productivity resets.

Turn goals into a focused 90-day execution sprint with priorities, milestones, weekly targets, decision filters, and review rituals.

You are a 90-day focus sprint designer. Build a focused execution plan that turns my goal into weekly progress without overloading the quarter. Sprint goal: [GOAL] Context: Start date: [START DATE] End date: [END DATE] Current baseline: [BASELINE] Available time per week: [TIME] Constraints: [CONSTRAINTS] Competing commitments: [COMMITMENTS] Success metric: [METRIC] Resources: [RESOURCES] Known risks: [RISKS] Motivation reason: [WHY] Design the sprint: 1. Sprint thesis Define: - why this goal matters now - what success means - what the sprint will not include - what tradeoff is required - what must be protected 2. Milestone map Break 90 days into: - Days 1-30: foundation - Days 31-60: execution - Days 61-90: refinement and completion For each phase include: - objective - milestones - weekly outputs - risks - review questions 3. Weekly operating rhythm Create a weekly plan with: - priority selection - focus blocks - admin tasks - progress metric - accountability - Friday review - next-week adjustment 4. Decision filters Create filters for: - new opportunities - extra tasks - scope creep - low-energy weeks - missed milestones - competing priorities 5. Sprint dashboard Create: - goal - metric - weekly target - leading indicator - lagging indicator - risk signal - next action - review cadence Rules: - Do not make a 90-day plan with too many goals. - Do not ignore capacity. - Do not rely on motivation. - The sprint should make focus easier every week. --------------------------------------------------------------------------------

#036Priority Method Customizer

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople who tried Eisenhower, MoSCoW, RICE, OKRs, or task scoring but need something more practical.

Adapt classic prioritization methods into a custom decision system that fits your goals, workload, energy, and real constraints.

Act as a prioritization method customizer. Build a custom priority method for me instead of forcing a generic framework. My situation: Goals: [GOALS] Task list: [TASKS] Project list: [PROJECTS] Decision problems: [PROBLEMS] Current method, if any: [CURRENT METHOD] Why it fails: [WHY IT FAILS] Available time: [TIME] Energy pattern: [ENERGY] Deadlines: [DEADLINES] Work type: [WORK TYPE] Customize the method: A. Method fit diagnosis Evaluate which parts of these methods are useful for me: - Eisenhower Matrix - RICE scoring - MoSCoW - OKRs - Pareto principle - impact-effort matrix - time blocking - energy-based planning For each explain: - useful part - dangerous part - adaptation needed B. Custom criteria Choose 5 to 7 criteria from: - impact - urgency - strategic fit - energy match - effort - deadline - dependency - risk - emotional resistance - compounding value - maintenance necessity C. Custom scoring system Build a simple scoring method. Include: - score scale - what each score means - weighting - tie-breaker - when not to score - fast version - deep version D. Apply the method Apply it to my tasks and projects. Output: - ranked list - do now - schedule - batch - defer - delete - clarify E. Usage guide Create instructions for: - daily use - weekly use - when overloaded - when energy is low - when a new opportunity appears Rules: - Do not create a complex spreadsheet unless needed. - Do not use urgency as the default winner. - Do not ignore energy. - The method should be simple enough to use repeatedly. --------------------------------------------------------------------------------

#037Priority Debt Auditor

GOAL SETTING, PRIORITIES & DECISION FILTERSPeople who feel behind, overloaded, guilty, or mentally crowded by too many unresolved priorities.

Identify accumulated priority debt caused by postponed decisions, unfinished projects, vague tasks, old commitments, and ignored tradeoffs.

You are a priority debt auditor. Help me find the hidden commitments and unresolved decisions that are draining attention. Inputs: Unfinished projects: [PROJECTS] Overdue tasks: [TASKS] Old commitments: [COMMITMENTS] Decisions I have delayed: [DECISIONS] People I owe updates to: [PEOPLE] Goals I keep postponing: [GOALS] Ideas I keep carrying: [IDEAS] Current stressors: [STRESSORS] Audit priority debt: 1. Debt inventory Classify debt into: - overdue action debt - decision debt - communication debt - project debt - emotional debt - maintenance debt - opportunity debt - clarity debt - abandoned goal debt 2. Cost analysis For each item identify: - mental cost - relationship cost - strategic cost - deadline risk - emotional weight - real consequence - whether it still matters 3. Resolution path Assign each item: - finish - communicate - renegotiate - schedule - delegate - delete - archive - decide - convert to someday 4. Debt payoff plan Create: - first 30-minute payoff block - first communication block - highest-relief action - highest-risk action - items to delete today - items to review later 5. Prevention system Create rules to prevent new priority debt: - decision deadlines - project limits - weekly cleanup - communication rules - task aging rules - commitment filters Rules: - Do not keep old priorities alive by default. - Do not treat guilt as evidence of importance. - Do not avoid communication debt. - The goal is relief, clarity, and renewed focus. --------------------------------------------------------------------------------

#038Low-Energy Priority Filter

GOAL SETTING, PRIORITIES & DECISION FILTERSTired days, burnout prevention, recovery periods, busy weeks, disrupted schedules, and sustainable productivity.

Decide what to do when energy is low, focus is weak, motivation is poor, or the original plan is no longer realistic.

Act as a low-energy priority coach. Help me choose the best useful work for my current capacity without pretending I can operate at full power. Current state: Energy level: [ENERGY 1-10] Focus level: [FOCUS 1-10] Mood: [MOOD] Available time: [TIME] Tasks planned: [TASKS] Deadlines: [DEADLINES] Important goals: [GOALS] Non-negotiables: [NON-NEGOTIABLES] Recovery needs: [RECOVERY] Things I should avoid today: [AVOID] Apply the low-energy filter: A. Capacity reality Estimate what kind of work fits today: - deep work - light creative work - admin - communication - planning - cleanup - learning - recovery - no-work recovery B. Task sorting Sort tasks into: - must do even on low energy - minimum viable version - can do in low energy - should not do today - should be rescheduled - should be communicated - should be deleted C. Minimum viable day Create a plan with: - one essential action - one maintenance action - one communication action - one recovery action - one setup action for tomorrow D. Energy protection Create rules for: - stopping work - avoiding hard decisions - reducing scope - asking for help - rescheduling - preventing guilt spirals - ending the day cleanly E. Recovery and restart Create a restart plan for tomorrow or the next high-energy window. Rules: - Do not shame low energy. - Do not force high-focus work into low-focus time. - Do not let a low-energy day destroy the week. - The goal is useful progress and recovery, not heroic effort. --------------------------------------------------------------------------------

#039Opportunity Cost Calculator

GOAL SETTING, PRIORITIES & DECISION FILTERSDeciding whether something is worth time, attention, energy, money, or strategic commitment.

Make hidden costs visible before committing to tasks, goals, projects, meetings, purchases, opportunities, or routines.

You are an opportunity cost calculator. Help me understand what this choice will really cost before I say yes. Potential commitment: [DESCRIBE COMMITMENT] Context: Current goals: [GOALS] Current projects: [PROJECTS] Available time: [TIME] Available money, if relevant: [MONEY] Available energy: [ENERGY] Existing commitments: [COMMITMENTS] Long-term direction: [DIRECTION] Expected benefit: [BENEFIT] Decision deadline: [DEADLINE] Calculate the cost: 1. Visible cost Estimate: - time required - money required - energy required - calendar space required - learning curve - communication load - maintenance work - follow-up work 2. Hidden cost Identify: - attention cost - switching cost - emotional cost - delay cost - relationship cost - quality cost - missed opportunity - future maintenance - complexity added 3. What it replaces List what I may have to reduce, delay, or stop: - goals - projects - routines - rest - relationships - learning - creative work - admin - deep work 4. Value comparison Compare benefit vs cost across: - short-term value - long-term value - compounding potential - risk reduction - identity alignment - regret risk - reversibility 5. Recommendation Recommend: - yes - yes with limits - test first - delay - no Include: - conditions - scope limit - review date - exit rule Rules: - Do not count only obvious costs. - Do not ignore maintenance burden. - Do not recommend yes without naming what it replaces. - Every yes should have a visible tradeoff. --------------------------------------------------------------------------------

#040Full Goal Setting, Priorities & Decision Filters Audit

GOAL SETTING, PRIORITIES & DECISION FILTERSFull planning resets, quarterly reviews, annual planning, overloaded schedules, career planning, business planning, and personal productivity redesign.

Audit and rebuild your complete goal-setting and priority system across goals, tasks, projects, tradeoffs, opportunity filters, attention rules, and decision habits.

Act as an independent goal and priority systems auditor. Review my current goals, priorities, tasks, opportunities, and decision filters, then redesign the system so I know what deserves attention and why. Full context: Current goals: [GOALS] Current projects: [PROJECTS] Current task list: [TASKS] Current commitments: [COMMITMENTS] New opportunities: [OPPORTUNITIES] Long-term direction: [DIRECTION] Time available: [TIME] Energy pattern: [ENERGY] Deadlines: [DEADLINES] People depending on me: [PEOPLE] Current prioritization method: [METHOD] Where I feel stuck: [STUCK] Where I overcommit: [OVERCOMMIT] Where I procrastinate: [PROCRASTINATE] Audit across 30 dimensions: 1. Goal clarity 2. Goal meaning 3. Goal feasibility 4. Long-term alignment 5. Current priority clarity 6. Task ranking 7. Project ranking 8. Deadline realism 9. Urgency accuracy 10. Impact assessment 11. Energy alignment 12. Opportunity filtering 13. Saying no 14. Tradeoff visibility 15. Decision speed 16. Decision quality 17. Overcommitment risk 18. Attention protection 19. Low-energy planning 20. Weekly priority selection 21. Daily priority selection 22. Task deletion 23. Project pruning 24. Communication around priorities 25. Maintenance responsibilities 26. Review rhythm 27. Goal conflict resolution 28. Opportunity cost awareness 29. Recovery after missed plans 30. System usability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason my goals or priorities are currently unclear, overloaded, or hard to execute. B. Priority system redesign Create: - goal hierarchy - priority hierarchy - task ranking method - project pruning rules - opportunity filter - no / not-now rules - daily priority method - weekly priority method - low-energy priority method - decision review loop C. Decision filters Build specific filters for: - new opportunities - urgent requests - meetings - projects - learning goals - personal commitments - low-impact tasks - emotionally tempting tasks D. Implementation plan Create: - first 24 hours - first 7 days - first 30 days - weekly review ritual - monthly goal review - what to stop doing immediately - what to protect at all costs E. Executive summary Write a direct summary with: - strongest goal - weakest goal - highest-priority project - biggest distraction - most important no - next action to take today - rule to use when everything feels urgent Rules: - Do not approve every goal. - Do not let urgency dominate the system. - Do not ignore capacity, energy, and opportunity cost. - Use [LOW CONFIDENCE] where information is missing. - The final system should make attention decisions easier, faster, and more honest. -------------------------------------------------------------------------------- TIME MANAGEMENT & CALENDAR DESIGN

#041Calendar Reality Audit

TIME MANAGEMENT & CALENDAR DESIGNPeople who feel busy but not effective, overloaded professionals, founders, managers, creators, students, consultants, and anyone whose calendar does not match their priorities.

Audit your actual calendar against your goals, responsibilities, energy, and workload to reveal where time is being lost, overloaded, or misallocated.

You are a time management auditor. Help me evaluate my current calendar honestly and redesign it around realistic capacity, important work, deadlines, buffers, and recovery. My calendar context: Current weekly calendar: [PASTE CALENDAR / DESCRIBE WEEK] Main goals: [GOALS] Active projects: [PROJECTS] Recurring responsibilities: [RESPONSIBILITIES] Meetings: [MEETINGS] Deadlines: [DEADLINES] Available work hours: [WORK HOURS] Energy patterns: [ENERGY] Biggest calendar problems: [PROBLEMS] Tasks that never fit: [TASKS THAT NEVER FIT] Things I want more time for: [MORE TIME FOR] Things I want less time spent on: [LESS TIME ON] Run the calendar audit: 1. Calendar reality map Analyze how my time is currently divided across: - deep work - meetings - admin - communication - planning - project execution - urgent work - maintenance - learning - personal obligations - recovery - unplanned time For each category identify: - actual time spent - whether it matches my goals - hidden cost - capacity risk - improvement opportunity 2. Misalignment diagnosis Find where my calendar is misaligned with: - stated priorities - energy windows - deadlines - project workload - personal commitments - focus needs - recovery needs - communication expectations 3. Calendar leak list Identify the top 10 calendar leaks. For each include: - leak - where it appears - why it happens - cost - fix - prevention rule 4. Time reallocation plan Recommend what to: - protect - reduce - batch - move - shorten - delete - delegate - schedule - buffer 5. Calendar redesign summary Create: - ideal weekly time allocation - protected focus blocks - meeting rules - admin blocks - buffer blocks - recovery blocks - daily shutdown block - first 7-day calendar repair plan Rules: - Do not assume I can simply add more hours. - Do not create a perfect calendar that ignores interruptions. - Do not protect meetings over important work by default. - The output must show what my calendar should stop making room for. --------------------------------------------------------------------------------

#042Time Budget Allocator

TIME MANAGEMENT & CALENDAR DESIGNWeekly planning, workload planning, founders, freelancers, managers, creators, operators, students, and anyone who needs a realistic time allocation model.

Build a weekly time budget that assigns realistic hours to goals, projects, meetings, admin, communication, recovery, and personal commitments.

Act as a time budget planner. Treat my week like a limited budget and allocate hours based on priorities, deadlines, energy, and real capacity. Inputs: Total available hours this week: [HOURS] Main goals: [GOALS] Active projects: [PROJECTS] Deadlines: [DEADLINES] Recurring meetings: [MEETINGS] Recurring admin: [ADMIN] Communication load: [COMMUNICATION] Personal commitments: [PERSONAL] Energy constraints: [ENERGY] Non-negotiable blocks: [NON-NEGOTIABLES] Work I tend to underestimate: [UNDERESTIMATED WORK] Create the time budget: A. Capacity calculation Calculate: - total available hours - fixed commitments - flexible work time - deep work capacity - meeting load - admin load - communication load - buffer requirement - recovery requirement - realistic remaining capacity B. Budget categories Allocate time across: - goal-critical work - deadline work - project work - planning - meetings - admin - email / messages - learning - personal commitments - recovery - buffer For each category include: - recommended hours - reason - risk if underfunded - maximum limit, if needed C. Overload check Compare required time vs available time. If overloaded, recommend: - what to cut - what to delay - what to reduce - what to renegotiate - what to batch - what to delegate D. Weekly allocation Create a weekly layout showing: - focus blocks - admin blocks - meetings - communication windows - buffer blocks - deadline protection - recovery blocks E. Budget rules Create rules for: - when a new request appears - when a deadline moves - when energy is low - when a meeting is requested - when the week is already full Rules: - Do not allocate more than 80% of flexible time. - Do not ignore transition time. - Do not treat all hours as equal. - The final budget must make tradeoffs visible. --------------------------------------------------------------------------------

#043Ideal Week Blueprint

TIME MANAGEMENT & CALENDAR DESIGNPeople redesigning their weekly rhythm, creators, founders, students, consultants, managers, and anyone who wants a repeatable weekly structure.

Design an ideal weekly calendar that fits your goals, energy, obligations, focus blocks, meetings, admin, and recovery without becoming unrealistic.

You are a weekly calendar architect. Build an ideal week that reflects how I actually need to work, not how I wish I worked. My context: Role / work type: [ROLE] Main goals: [GOALS] Work hours: [WORK HOURS] Fixed commitments: [FIXED COMMITMENTS] Meeting requirements: [MEETING REQUIREMENTS] Deep work needs: [DEEP WORK NEEDS] Admin work: [ADMIN WORK] Communication expectations: [COMMUNICATION] Energy pattern by day: [ENERGY BY DAY] Personal commitments: [PERSONAL COMMITMENTS] Preferred work rhythm: [RHYTHM] Things that derail my week: [DERAILERS] Build my ideal week: 1. Weekly rhythm principles Create 7 principles for my week. Each principle should explain: - what it protects - what it prevents - where it shows up on the calendar 2. Day role design Assign a purpose to each day. Examples: - planning day - deep work day - meeting day - delivery day - admin day - review day - recovery-heavy day For each day include: - main work type - secondary work type - what not to schedule - ideal energy use 3. Block architecture Design blocks for: - deep work - meetings - admin - communication - project execution - planning - review - learning - personal commitments - recovery - buffer For each block include: - duration - best time - rules - success criteria 4. Ideal week calendar Create a Monday-to-Sunday calendar in plain text. Include: - start and end times - block names - buffer periods - shutdown rituals - flexible blocks - emergency capacity 5. Reality adjustment Create versions for: - normal week - meeting-heavy week - deadline-heavy week - low-energy week - travel or disrupted week Rules: - Do not schedule every minute. - Do not place deep work after draining meetings unless necessary. - Do not remove personal or recovery commitments. - The ideal week should be a default template, not a prison. --------------------------------------------------------------------------------

#044Time Blocking Studio

TIME MANAGEMENT & CALENDAR DESIGNPeople who want structure in their day or week but need realistic blocks rather than rigid minute-by-minute planning.

Turn goals, tasks, deadlines, and energy patterns into a practical time-blocked calendar with focus blocks, admin blocks, buffers, and review rituals.

Act as a time-blocking designer. Convert my task list and calendar into a realistic time-blocked schedule that supports important work. Inputs: Timeframe to plan: [DAY / WEEK] Task list: [TASKS] Calendar commitments: [COMMITMENTS] Deadlines: [DEADLINES] Energy pattern: [ENERGY] Deep work tasks: [DEEP WORK TASKS] Admin tasks: [ADMIN TASKS] Communication tasks: [COMMUNICATION TASKS] Personal obligations: [OBLIGATIONS] Preferred block length: [BLOCK LENGTH] Hard stop times: [HARD STOPS] Create the time blocks: A. Task-to-block conversion For each task identify: - task type - estimated time - energy required - deadline - best block type - whether it should be batched - whether it needs deep work - whether it can be shortened B. Block design Create block types: - deep work block - shallow work block - admin batch - communication window - planning block - meeting block - buffer block - recovery block - shutdown block For each include: - ideal duration - rules - setup ritual - output expected - stop condition C. Calendar placement Place tasks into blocks based on: - energy - urgency - dependencies - focus requirement - transition cost - deadline risk - personal obligations D. Overload correction If tasks do not fit, sort extras into: - reschedule - reduce scope - delegate - delete - waiting - next week - low-energy backup E. Final schedule Provide: - time-blocked calendar - top 3 protected blocks - flexible blocks - buffer placement - rules for interruptions - end-of-day review Rules: - Do not stack focus blocks without breaks. - Do not ignore transition time. - Do not put every task on the calendar if it should stay in a task list. - The schedule must be executable, not decorative. --------------------------------------------------------------------------------

#045Deadline Backward Planner

TIME MANAGEMENT & CALENDAR DESIGNProjects with fixed deadlines, launches, reports, client work, exams, creative deliverables, and high-stakes execution planning.

Reverse-engineer deadlines into milestones, calendar blocks, buffers, review points, dependencies, and communication checkpoints.

You are a deadline backward planning specialist. Help me turn a deadline into a realistic calendar plan with enough time for execution, review, delays, and final polish. Deadline: [DEADLINE / FINAL DUE DATE] Deliverable: [DELIVERABLE] Context: Current progress: [PROGRESS] Required quality level: [QUALITY] Steps involved: [STEPS] Dependencies: [DEPENDENCIES] People involved: [PEOPLE] Available time: [AVAILABLE TIME] Known risks: [RISKS] Review or approval requirements: [REVIEWS] Hard constraints: [CONSTRAINTS] Build the backward plan: 1. Final deliverable definition Clarify: - what done means - what must be included - what is optional - acceptance criteria - final format - quality standard 2. Backward milestone map Work backward from the deadline and create: - final submission date - final review date - polish date - draft completion date - main work milestones - research or preparation deadlines - dependency deadlines - decision deadlines - buffer deadlines 3. Calendar block plan Estimate and schedule: - preparation blocks - deep work blocks - review blocks - admin blocks - communication blocks - revision blocks - buffer blocks 4. Risk and buffer design Identify: - likely delay points - dependency risks - approval risks - underestimation risks - energy risks - schedule conflicts Create buffers for each. 5. Execution tracker Create: - milestone checklist - daily or weekly progress checks - risk trigger list - communication reminders - fallback plan if behind schedule Rules: - Do not plan to finish at the last minute. - Do not assume first drafts are final. - Do not ignore approval time. - Every deadline plan must include buffer and review time. --------------------------------------------------------------------------------

#046Buffer Architecture Builder

TIME MANAGEMENT & CALENDAR DESIGNPeople whose plans often break because there is no room for reality.

Design buffers into your calendar so delays, transitions, interruptions, low-energy periods, meetings, and unexpected work do not destroy the schedule.

Act as a buffer architect. Help me design a calendar that survives interruptions, delays, overruns, transitions, and unexpected work. My schedule context: Typical weekly schedule: [SCHEDULE] Meetings: [MEETINGS] Deep work needs: [DEEP WORK] Recurring deadlines: [DEADLINES] Common interruptions: [INTERRUPTIONS] Tasks that overrun: [OVERRUN TASKS] Transition needs: [TRANSITIONS] Energy lows: [ENERGY LOWS] Personal obligations: [OBLIGATIONS] Where my schedule usually breaks: [BREAK POINTS] Design the buffer system: A. Buffer diagnosis Identify where buffers are needed for: - task estimation error - meeting overruns - transitions - context switching - decision fatigue - communication delays - personal obligations - urgent work - recovery - weekly catch-up B. Buffer types Create buffer types: - transition buffer - meeting buffer - deadline buffer - recovery buffer - admin buffer - emergency buffer - weekly catch-up buffer - decision buffer - creative buffer - personal buffer For each include: - purpose - ideal length - placement - rule - misuse warning C. Calendar placement Recommend exactly where buffers should go: - before deep work - after meetings - before deadlines - after high-energy work - end of day - end of week - before personal commitments - between context switches D. Buffer protection rules Create rules for: - when buffers can be used - when buffers cannot be used - how to prevent filling buffers with random work - how to recover used buffer time - how to review buffer needs weekly E. New calendar design Create: - buffer map - weekly buffer allocation - daily buffer minimum - emergency capacity rule - overload warning signal Rules: - Do not treat buffers as empty time to fill. - Do not remove recovery buffers first. - Do not schedule a week at 100% capacity. - Buffers should make the calendar more reliable, not less ambitious. --------------------------------------------------------------------------------

#047Meeting Load Reducer

TIME MANAGEMENT & CALENDAR DESIGNManagers, founders, teams, consultants, operators, remote workers, and anyone whose calendar is dominated by meetings.

Audit meetings, reduce unnecessary calendar load, redesign meeting rules, batch collaboration, and protect execution time.

You are a meeting load reduction consultant. Help me reduce meeting waste while preserving the communication and collaboration that actually matter. Meeting context: List of recurring meetings: [MEETINGS] One-off meetings this week: [ONE-OFF MEETINGS] My role in meetings: [ROLE] Decision-making responsibility: [DECISION ROLE] Meetings I dislike: [DISLIKED MEETINGS] Meetings that are useful: [USEFUL MEETINGS] Deep work needs: [DEEP WORK] Communication alternatives: [TOOLS] Team or stakeholder expectations: [EXPECTATIONS] Reduce meeting load: 1. Meeting inventory For each meeting identify: - purpose - owner - frequency - duration - required attendees - decision made - output produced - my role - cost to my calendar - value score 2. Meeting classification Classify meetings as: - essential decision meeting - collaboration meeting - status meeting - relationship meeting - information sharing - approval meeting - unclear meeting - should be async - should be shorter - should be removed 3. Reduction recommendations For each meeting recommend: - keep - shorten - reduce frequency - combine - convert to async - delegate attendance - attend only part - decline - redesign agenda 4. Calendar redesign Create meeting rules: - meeting-free blocks - meeting days - maximum meetings per day - minimum buffer between meetings - default meeting length - agenda requirements - decision requirements - async-first rules 5. Scripts Write scripts for: - declining a meeting - asking for agenda - suggesting async update - shortening recurring meeting - reducing frequency - leaving a meeting series - protecting focus time Rules: - Do not remove meetings that carry real relationship or decision value. - Do not assume all meetings are bad. - Do not protect collaboration at the expense of execution. - The final system should reduce calendar load and improve meeting quality. --------------------------------------------------------------------------------

#048Batching System Designer

TIME MANAGEMENT & CALENDAR DESIGNAdmin work, email, messages, content creation, errands, planning, finance, reporting, learning, and repeated low-focus tasks.

Group similar work into intentional batches to reduce context switching, improve focus, and create cleaner calendar blocks.

Act as a batching system designer. Help me group scattered tasks into batches that make my calendar cleaner and my work less fragmented. Task inputs: Task list: [TASKS] Recurring work: [RECURRING WORK] Communication load: [COMMUNICATION] Admin tasks: [ADMIN] Creative tasks: [CREATIVE] Personal tasks: [PERSONAL] Tools used: [TOOLS] Current context switching problems: [PROBLEMS] Available scheduling windows: [WINDOWS] Energy pattern: [ENERGY] Build the batching system: A. Task pattern scan Group tasks by: - tool - location - energy level - cognitive mode - urgency - deadline - project - communication type - mental context - repetition B. Batch categories Create batch categories such as: - email batch - message batch - admin batch - finance batch - planning batch - creative batch - review batch - errands batch - maintenance batch - follow-up batch For each batch include: - tasks included - ideal frequency - ideal duration - best energy level - calendar placement - completion rule C. Batch calendar Create a weekly batching schedule with: - daily micro-batches - weekly batches - monthly batches - catch-up batch - overflow batch D. Anti-fragmentation rules Create rules for: - when to batch - when not to batch - how to prevent checking constantly - how to handle urgent exceptions - how to close a batch - how to avoid batch overload E. Batch templates Create templates for: - 30-minute admin batch - 45-minute communication batch - 60-minute planning batch - 90-minute creative batch - monthly maintenance batch Rules: - Do not batch deep work with shallow work. - Do not create batches so large they become avoided. - Do not ignore urgency exceptions. - Batching should reduce switching, not create new procrastination piles. --------------------------------------------------------------------------------

#049Monthly Capacity Planner

TIME MANAGEMENT & CALENDAR DESIGNMonthly planning, project-heavy work, content calendars, business operations, student planning, client delivery, and personal productivity systems.

Plan a month by balancing major goals, fixed commitments, project milestones, deadlines, personal events, buffers, and workload capacity.

You are a monthly capacity planner. Help me build a realistic monthly calendar that fits priorities, deadlines, commitments, and capacity. Month to plan: [MONTH] Inputs: Main goals for the month: [GOALS] Projects: [PROJECTS] Deadlines: [DEADLINES] Fixed events: [EVENTS] Recurring commitments: [COMMITMENTS] Available workdays: [WORKDAYS] Vacation / travel / personal time: [TIME OFF] Energy considerations: [ENERGY] Important meetings: [MEETINGS] Expected workload: [WORKLOAD] Known risks: [RISKS] Plan the month: 1. Month overview Map: - available workdays - low-capacity days - high-capacity days - deadline weeks - meeting-heavy weeks - personal commitment weeks - recovery needs - buffer requirements 2. Monthly priorities Choose: - primary outcome - secondary outcomes - maintenance commitments - optional stretch work - work to avoid this month 3. Milestone placement Place project milestones across the month. For each milestone include: - due date - required preparation - work blocks needed - review time - dependency - buffer - risk 4. Week-by-week calendar Create a 4 or 5-week monthly plan. For each week include: - focus theme - top outcomes - key deadlines - major blocks - meetings - admin - buffers - recovery 5. Monthly operating rules Create rules for: - accepting new work - moving deadlines - protecting focus weeks - using buffers - reviewing progress - adjusting mid-month Rules: - Do not overload the first week with all goals. - Do not ignore personal commitments. - Do not schedule major deadlines without review time. - The month should have a visible capacity logic. --------------------------------------------------------------------------------

#050Quarterly Time Allocation Board

TIME MANAGEMENT & CALENDAR DESIGNQuarterly planning, OKRs, business planning, creator planning, launches, career goals, and major personal productivity cycles.

Allocate time across a quarter by strategic priorities, project phases, seasonal constraints, goals, review cycles, and execution capacity.

Act as a quarterly time allocation board. Help me decide how my time should be invested over the next 90 days. Quarter context: Quarter dates: [DATES] Strategic goals: [GOALS] Major projects: [PROJECTS] Key deadlines: [DEADLINES] Seasonal constraints: [CONSTRAINTS] Travel / time off: [TIME OFF] Recurring responsibilities: [RESPONSIBILITIES] Available weekly capacity: [CAPACITY] Energy patterns: [ENERGY] Risks: [RISKS] What must not be neglected: [NON-NEGOTIABLES] Allocate the quarter: A. Strategic time thesis Define: - main focus of the quarter - what this quarter is for - what this quarter is not for - tradeoffs required - time investment philosophy B. Time portfolio Allocate quarterly time across: - strategic projects - delivery work - maintenance work - meetings - admin - learning - relationship-building - personal life - recovery - buffer Show recommended percentage and hours. C. Phase design Divide the quarter into: - setup phase - execution phase - review / refinement phase For each phase include: - goals - calendar pattern - work blocks - meeting rules - deadlines - risks - review questions D. Capacity guardrails Create rules for: - maximum active projects - maximum meetings - maximum new commitments - minimum deep work hours - minimum buffer - minimum recovery time E. Quarterly calendar overview Create: - month-by-month plan - major milestones - review dates - decision dates - buffer weeks - end-of-quarter closeout Rules: - Do not make every week equally intense. - Do not plan a quarter without buffer. - Do not ignore recurring responsibilities. - The quarter should show strategic time allocation, not only task scheduling. --------------------------------------------------------------------------------

#051Calendar Protection Rulebook

TIME MANAGEMENT & CALENDAR DESIGNPeople whose calendar gets taken over by meetings, urgent requests, other people's priorities, or last-minute changes.

Create rules that protect focus blocks, deadlines, recovery time, planning time, and personal commitments from being overwritten by reactive work.

You are a calendar protection strategist. Build a rulebook that helps me defend the time blocks that matter most without becoming inflexible. Calendar context: Important work to protect: [IMPORTANT WORK] Current calendar threats: [THREATS] People who request time: [REQUESTERS] Meeting expectations: [EXPECTATIONS] Deadlines: [DEADLINES] Personal commitments: [PERSONAL] Focus blocks: [FOCUS BLOCKS] Recovery needs: [RECOVERY] Communication norms: [NORMS] Where I usually give in: [GIVE IN] Create the rulebook: 1. Protected time categories Define rules for protecting: - deep work - deadline work - planning - review - personal commitments - recovery - family or life obligations - admin blocks - buffers - shutdown time For each include: - why it matters - protection level - what can override it - what cannot override it - reschedule rule 2. Request filter Create a filter for incoming calendar requests: - does it need me? - does it need to be live? - does it need to happen now? - can it be shorter? - can it be async? - what does it replace? - what is the cost? 3. Calendar boundary scripts Write scripts for: - protecting a focus block - moving a meeting - declining a meeting - requesting agenda - shortening a meeting - proposing async update - protecting personal time - renegotiating urgency 4. Emergency exception policy Define what counts as a real exception and what does not. 5. Weekly protection review Create questions to review: - what protected time was respected? - what got overwritten? - why? - what rule needs to change? - what needs communication? Rules: - Do not make the calendar rigid beyond reality. - Do not allow every urgent request to override priority time. - Do not ignore relationship and role responsibilities. - Protection rules should make time more trustworthy. --------------------------------------------------------------------------------

#052Deadline Compression Rescue Plan

TIME MANAGEMENT & CALENDAR DESIGNUrgent projects, late starts, slipped timelines, client work, launches, reports, exams, creative deliverables, and crisis scheduling.

Replan a schedule when a deadline is closer than expected, work is behind, or the original timeline no longer fits.

Act as a deadline rescue planner. Help me compress the plan responsibly without destroying quality, trust, or sanity. Current situation: Deadline: [DEADLINE] Deliverable: [DELIVERABLE] Current progress: [PROGRESS] Work remaining: [WORK REMAINING] Available time: [TIME] Quality requirements: [QUALITY] People involved: [PEOPLE] Dependencies: [DEPENDENCIES] What can be reduced: [REDUCIBLE] What cannot be reduced: [NON-NEGOTIABLE] Risks: [RISKS] Create the rescue plan: A. Reality assessment Identify: - work completed - work remaining - must-have deliverable elements - nice-to-have elements - quality floor - deadline risk - dependency risk - communication risk B. Scope compression Sort work into: - keep - simplify - cut - delay - delegate - automate - reuse - request clarification - convert to phase two C. Emergency schedule Create a compressed timeline with: - immediate next action - focus blocks - decision points - review blocks - communication windows - final polish - buffer - submission time D. Communication plan Write messages for: - status update - scope reduction - deadline risk - request for extension - request for fast review - delivery expectation reset E. Post-deadline repair Create a short retrospective: - why the timeline slipped - what to change - what buffer was missing - what earlier warning signal to use next time Rules: - Do not pretend the original scope still fits if it does not. - Do not cut quality below the minimum acceptable level. - Do not hide deadline risk from people affected. - The plan should create the best possible outcome under real constraints. --------------------------------------------------------------------------------

#053Deep Work Calendar Integrator

TIME MANAGEMENT & CALENDAR DESIGNKnowledge workers, creators, strategists, writers, developers, analysts, students, and anyone whose best work needs protected focus.

Integrate deep work into a real calendar with meetings, communication, admin, deadlines, recovery, and personal obligations.

You are a deep work calendar integrator. Help me place meaningful focus work into my real schedule without ignoring everything else I must do. My context: Deep work tasks: [DEEP WORK TASKS] Current calendar: [CALENDAR] Meetings: [MEETINGS] Communication expectations: [COMMUNICATION] Admin responsibilities: [ADMIN] Deadlines: [DEADLINES] Peak focus windows: [PEAK WINDOWS] Low-energy times: [LOW ENERGY] Interruptions: [INTERRUPTIONS] Personal obligations: [OBLIGATIONS] Current focus problems: [PROBLEMS] Integrate deep work: 1. Deep work demand Estimate: - hours needed - type of focus required - urgency - deadline pressure - preparation needed - recovery needed - ideal block length 2. Calendar fit analysis Identify: - best focus windows - blocked windows - bad focus windows - meeting clusters - possible deep work days - admin compression opportunities - communication batching opportunities 3. Deep work placement Create a schedule with: - primary deep work blocks - backup deep work blocks - preparation blocks - recovery blocks - buffer blocks - communication windows - no-meeting zones 4. Focus block protocol For each deep work block define: - task - goal - start ritual - distractions to remove - materials needed - success criterion - stop point - recovery action 5. Protection system Create rules for: - rescheduling deep work - defending blocks - handling interruptions - recovering after a missed block - measuring deep work output Rules: - Do not place deep work wherever empty space exists. - Do not stack deep work after draining obligations unless no alternative exists. - Do not make the plan fragile. - Deep work should be scheduled like priority work, not leftover time. --------------------------------------------------------------------------------

#054Admin and Maintenance Scheduling Matrix

TIME MANAGEMENT & CALENDAR DESIGNBusy professionals, operators, solo founders, freelancers, households, managers, creators, and anyone with lots of small recurring tasks.

Schedule recurring admin, maintenance, follow-ups, errands, reviews, and operational tasks so they do not interrupt important work all week.

Act as an admin scheduling specialist. Help me design a calendar system for recurring maintenance work that keeps life and work running without taking over. Admin and maintenance tasks: [PASTE TASKS] Context: Frequency requirements: [FREQUENCY] Current admin problems: [PROBLEMS] Tools used: [TOOLS] Available low-energy windows: [LOW ENERGY WINDOWS] Deep work schedule: [DEEP WORK] Deadlines: [DEADLINES] Personal obligations: [OBLIGATIONS] Tasks I forget: [FORGET] Tasks that create problems if ignored: [RISK TASKS] Create the scheduling matrix: A. Admin inventory Sort tasks into: - daily maintenance - weekly admin - monthly admin - quarterly admin - follow-ups - financial tasks - household or personal tasks - planning tasks - cleanup tasks - relationship or communication tasks B. Risk classification For each task identify: - consequence if ignored - ideal frequency - time required - energy required - best time window - whether it can be batched - whether it can be automated - whether it needs a reminder C. Scheduling matrix Create a matrix with: - task - frequency - duration - best day - best time - trigger - reminder - backup slot - done definition D. Calendar placement Build: - daily maintenance block - weekly admin block - monthly maintenance block - follow-up block - cleanup block - overflow block E. Maintenance rules Create rules for: - what happens if admin block is missed - what must never be skipped - what can be delayed - what can be batched - what should be automated - how to review the system monthly Rules: - Do not let admin scatter across the entire day. - Do not schedule admin during peak creative or strategic energy. - Do not ignore small tasks that create big problems. - Maintenance should support priorities, not replace them. --------------------------------------------------------------------------------

#055Workload Feasibility Calculator

TIME MANAGEMENT & CALENDAR DESIGNPreventing overcommitment, planning realistic weeks, assessing deadlines, estimating project load, and negotiating commitments.

Test whether a schedule, task list, project plan, or weekly workload actually fits the available time and capacity.

You are a workload feasibility calculator. Help me test whether my planned workload fits my real calendar before I commit. Planned workload: [PASTE TASKS / PROJECTS / DEADLINES] Calendar and capacity: Available hours: [AVAILABLE HOURS] Fixed meetings: [MEETINGS] Admin requirements: [ADMIN] Communication requirements: [COMMUNICATION] Personal obligations: [PERSONAL] Energy limits: [ENERGY] Hard deadlines: [DEADLINES] Expected interruptions: [INTERRUPTIONS] Quality standard: [QUALITY] Calculate feasibility: 1. Workload estimate For each item estimate: - best-case time - realistic time - worst-case time - energy level needed - dependency - deadline - focus requirement - risk of overrun 2. Capacity estimate Calculate: - total calendar hours - fixed commitments - flexible time - focus-capable time - low-energy time - buffer needed - realistic work capacity 3. Fit analysis Compare workload to capacity: - fits comfortably - fits tightly - overloaded - impossible without tradeoffs - unclear due to missing information Show the gap. 4. Adjustment plan Recommend: - tasks to reduce - tasks to move - tasks to delegate - tasks to delete - deadlines to renegotiate - scope to cut - buffers to add 5. Final commitment recommendation Give: - safe commitment level - risky commitment level - commitments to avoid - schedule version that fits - message to communicate capacity Rules: - Do not use optimistic estimates only. - Do not count every hour as productive. - Do not remove buffer to make the math work. - The output should prevent unrealistic commitments. --------------------------------------------------------------------------------

#056Schedule Conflict Negotiator

TIME MANAGEMENT & CALENDAR DESIGNBusy weeks, overlapping commitments, deadline clashes, calendar overload, and situations where something must move.

Resolve conflicts between meetings, deadlines, deep work, personal obligations, recovery, and urgent requests.

Act as a schedule conflict negotiator. Help me decide what to move, protect, shorten, cancel, delegate, or renegotiate when my calendar has conflicts. Conflict details: Calendar conflicts: [CONFLICTS] Deadlines: [DEADLINES] Meetings: [MEETINGS] Important work blocks: [WORK BLOCKS] Personal obligations: [PERSONAL] People affected: [PEOPLE] Flexibility of each item: [FLEXIBILITY] Consequences of moving items: [CONSEQUENCES] Current priority: [PRIORITY] Resolve the conflicts: A. Conflict map For each conflict identify: - items competing - time overlap - priority level - deadline pressure - flexibility - relationship impact - consequence if moved - consequence if protected B. Protection hierarchy Create a hierarchy for what should be protected first: - legal / hard deadlines - high-impact work - personal non-negotiables - health / recovery - stakeholder commitments - meetings - admin - optional tasks Adapt it to my context. C. Resolution options For each conflict propose: - keep as is - move one item - shorten - split - delegate - convert to async - reschedule - cancel - renegotiate deadline D. Communication scripts Write messages for: - rescheduling a meeting - declining a request - asking to shorten - moving a deadline - explaining priority conflict - protecting personal commitment E. Final revised schedule Provide: - revised calendar - protected blocks - moved items - communication actions - remaining risks - backup plan Rules: - Do not automatically sacrifice personal commitments. - Do not move high-impact work for low-value meetings. - Do not ignore relationship consequences. - Conflict resolution must be explicit and practical. --------------------------------------------------------------------------------

#057Personal Rhythm Calendar Map

TIME MANAGEMENT & CALENDAR DESIGNPeople whose productivity depends on energy timing, creative workers, founders, students, neurodivergent workers, parents, and anyone with variable capacity.

Design a calendar around natural energy rhythms, task types, attention patterns, creative windows, social capacity, and recovery needs.

You are a personal rhythm calendar designer. Build a schedule that matches work types to my natural energy and attention patterns. My rhythm context: Best focus times: [BEST FOCUS TIMES] Worst focus times: [WORST FOCUS TIMES] Creative windows: [CREATIVE WINDOWS] Analytical windows: [ANALYTICAL WINDOWS] Social energy: [SOCIAL ENERGY] Low-energy periods: [LOW ENERGY] Sleep / recovery pattern: [RECOVERY] Work obligations: [OBLIGATIONS] Personal obligations: [PERSONAL] Current calendar: [CALENDAR] Tasks by type: [TASK TYPES] Map the rhythm: 1. Energy timeline Create a daily and weekly energy map for: - focus - creativity - analysis - communication - decisions - admin - learning - recovery 2. Task matching Match task types to ideal rhythm windows: - strategic thinking - writing - analysis - meetings - calls - email - admin - planning - errands - learning - review - creative exploration 3. Calendar redesign Create a schedule that places: - hard work during peak windows - meetings during social windows - admin during lower-energy windows - creative work during open thinking windows - recovery before depletion - planning before decision fatigue 4. Rhythm protection Create rules for: - not wasting peak time - limiting draining work - meeting placement - recovery placement - low-energy backup tasks - schedule recovery after intense days 5. Experiment plan Create a 14-day test: - what to track - what to change - what to compare - how to adjust the calendar Rules: - Do not force a standard 9-to-5 rhythm if it does not fit. - Do not schedule important thinking during known low-energy windows. - Do not ignore unavoidable obligations. - The calendar should respect energy without becoming fragile. --------------------------------------------------------------------------------

#058Calendar Cleanup Sprint

TIME MANAGEMENT & CALENDAR DESIGNCalendar resets, post-chaos cleanup, returning from travel, overbooked weeks, new quarter resets, and productivity system maintenance.

Clean up an overloaded or messy calendar by removing unnecessary events, consolidating commitments, adding buffers, and restoring priority time.

Act as a calendar cleanup coach. Help me run a focused calendar cleanup sprint that makes my schedule clearer, lighter, and more aligned. Calendar dump: [PASTE CALENDAR / EVENTS / RECURRING COMMITMENTS] Context: Main priorities: [PRIORITIES] Important deadlines: [DEADLINES] Meetings to review: [MEETINGS] Recurring events: [RECURRING EVENTS] Personal commitments: [PERSONAL] Focus blocks needed: [FOCUS] Current pain points: [PAIN POINTS] Time available for cleanup: [CLEANUP TIME] Run the cleanup sprint: A. Event classification Classify each calendar item as: - keep - shorten - move - batch - convert to async - delegate - cancel - clarify - protect - add buffer B. Recurring event audit For recurring events, identify: - purpose - current value - frequency fit - duration fit - attendees needed - output required - whether it should continue C. Cleanup actions Create a prioritized list: - delete first - move first - shorten first - add buffer around - protect from changes - communicate about - review later D. Rebuilt calendar Create a cleaner version with: - protected focus time - meeting clusters - admin blocks - communication blocks - personal commitments - recovery - buffers - catch-up slot E. Sprint checklist Create a 60-minute cleanup checklist: - first 10 minutes - next 20 minutes - next 20 minutes - final 10 minutes - follow-up actions Rules: - Do not delete commitments without considering consequences. - Do not add more structure than needed. - Do not leave recurring events unexamined. - The cleanup should reduce calendar friction immediately. --------------------------------------------------------------------------------

#059Rolling Weekly Schedule System

TIME MANAGEMENT & CALENDAR DESIGNDynamic work environments, founders, managers, freelancers, operators, students, and anyone whose week changes after Monday.

Create a weekly scheduling process that updates as priorities, energy, deadlines, meetings, and unexpected changes evolve throughout the week.

You are a rolling weekly schedule designer. Build a scheduling system that stays stable enough to guide me but flexible enough to adapt. My weekly context: Weekly goals: [GOALS] Known commitments: [COMMITMENTS] Deadlines: [DEADLINES] Meetings: [MEETINGS] Tasks: [TASKS] Available focus time: [FOCUS TIME] Likely disruptions: [DISRUPTIONS] Energy forecast: [ENERGY] Current planning problem: [PROBLEM] Tools: [TOOLS] Design the rolling system: 1. Weekly anchor plan Create fixed anchors: - planning block - deep work blocks - meeting clusters - admin blocks - communication windows - review block - buffer block - recovery block 2. Rolling update points Define when to update the schedule: - Monday start - daily morning check - midweek review - after major disruption - before deadline - Friday closeout For each update point include: - questions to ask - what can move - what cannot move - what to delete - what to communicate 3. Flex block design Create flexible blocks for: - overflow work - urgent requests - delayed tasks - low-energy work - catch-up - personal needs 4. Change rules Create if-then rules: - if a meeting is added - if a deadline moves earlier - if energy drops - if urgent work appears - if a focus block is missed - if a project becomes blocked - if the week is overloaded 5. Weekly closeout Create a closeout routine: - what got done - what moved - why it moved - what should not roll over - what to schedule next week - what system rule needs adjustment Rules: - Do not rebuild the whole week every day. - Do not make the plan so flexible it loses meaning. - Do not let urgent work erase priority work automatically. - The rolling system should preserve direction while adapting to reality. --------------------------------------------------------------------------------

#060Full Time Management and Calendar Design Audit

TIME MANAGEMENT & CALENDAR DESIGNFull calendar resets, overloaded professionals, founders, managers, students, creators, consultants, quarterly planning, and anyone who needs a realistic scheduling system.

Audit and redesign your complete time management system across daily planning, weekly planning, calendar structure, time blocks, deadlines, buffers, batching, meetings, and capacity.

Act as an independent time management and calendar systems auditor. Review my current schedule and redesign it into a realistic calendar system that protects priorities, handles deadlines, includes buffers, and fits my capacity. Full context: Current calendar: [CALENDAR] Current task list: [TASKS] Current projects: [PROJECTS] Main goals: [GOALS] Deadlines: [DEADLINES] Meetings: [MEETINGS] Recurring responsibilities: [RESPONSIBILITIES] Personal commitments: [PERSONAL] Available work hours: [WORK HOURS] Energy pattern: [ENERGY] Current planning method: [METHOD] Biggest schedule problems: [PROBLEMS] Where time is wasted: [WASTE] Where I need more time: [NEED MORE TIME] Constraints: [CONSTRAINTS] Audit across 30 dimensions: 1. Calendar realism 2. Time allocation 3. Goal alignment 4. Deadline planning 5. Buffer design 6. Deep work protection 7. Meeting load 8. Admin batching 9. Communication windows 10. Daily planning 11. Weekly planning 12. Monthly planning 13. Quarterly planning 14. Energy alignment 15. Transition time 16. Recovery time 17. Overcommitment risk 18. Task estimation 19. Project scheduling 20. Personal commitments 21. Schedule flexibility 22. Schedule protection 23. Recurring event quality 24. Context switching 25. Urgent work handling 26. Calendar cleanup 27. Low-energy scheduling 28. Deadline rescue readiness 29. Review cadence 30. System usability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason my schedule is not working. B. Calendar redesign Create: - weekly time budget - ideal week template - daily block structure - deep work schedule - meeting rules - admin batching schedule - communication windows - buffer architecture - deadline planning method - monthly planning rhythm - quarterly planning rhythm - calendar protection rules C. Workload feasibility Calculate whether my current workload fits my available time. Show: - estimated workload - available capacity - overload gap - what must be cut or moved - what must be renegotiated D. Implementation plan Create: - first 24-hour calendar cleanup - first 7-day schedule reset - first 30-day calendar experiment - weekly review ritual - monthly reset ritual - what to stop scheduling - what to protect first E. Executive summary Write a direct summary with: - most overloaded part of my calendar - most valuable time block to protect - biggest time leak - highest-impact schedule change - first calendar change to make today - rule to follow when the week gets chaotic Rules: - Do not create a fantasy calendar. - Do not remove buffers to make the schedule look productive. - Do not ignore personal commitments, energy, or recovery. - Use [LOW CONFIDENCE] where information is missing. - The final calendar system should make time visible, protected, and realistic. -------------------------------------------------------------------------------- TASK MANAGEMENT & EXECUTION SYSTEMS

#061Task Inbox Clarifier

TASK MANAGEMENT & EXECUTION SYSTEMSPeople with overloaded task apps, random notes, messy inboxes, unfinished reminders, meeting notes, and unclear to-dos that never become completed work.

Turn messy, vague, scattered tasks into clear next actions with outcomes, contexts, deadlines, owners, and execution priority.

You are a task clarification specialist. Help me process my messy task inbox into clean, actionable work that can be scheduled, delegated, deleted, or completed. Task inbox: [PASTE TASKS / NOTES / REMINDERS / OPEN LOOPS] Context: My role: [ROLE] Main goals: [GOALS] Active projects: [PROJECTS] Deadlines: [DEADLINES] Current tools: [TOOLS] Available time this week: [TIME] Energy constraints: [ENERGY] People involved: [PEOPLE] Tasks I keep avoiding: [AVOIDED TASKS] What feels most messy: [MESSY AREA] Clarify the inbox: 1. Sort the raw input Place every item into one of these categories: - task - project - idea - reminder - decision - waiting-for item - reference note - recurring task - personal obligation - unclear item - delete candidate 2. Rewrite vague tasks For every vague item, rewrite it using: - clear verb - object - desired outcome - context - owner - deadline, if any - project connection - estimated effort Example format: Original: Clarified task: Next action: Done means: Priority: Schedule or list: 3. Identify hidden projects Find any task that is actually a project. For each hidden project provide: - project name - outcome - first next action - milestone - deadline - risk if ignored 4. Route every item Assign each item to: - do today - schedule this week - add to project - delegate - waiting-for - someday - reference - delete - clarify before acting 5. Final clean task list Produce: - today list - this week list - project list - waiting-for list - delegated list - delete list - questions I must answer Rules: - Do not leave vague tasks in the active list. - Do not treat multi-step projects as single tasks. - Do not keep items only because they create guilt. - Every active task must have a next action that can physically be done. --------------------------------------------------------------------------------

#062Big Work Breakdown Engine

TASK MANAGEMENT & EXECUTION SYSTEMSLarge projects, launches, reports, content projects, business operations, personal projects, complex deliverables, and work that feels too big to start.

Break large, intimidating projects into milestones, deliverables, work packages, next actions, dependencies, and realistic execution blocks.

Act as a project breakdown engineer. Convert this large piece of work into an execution-ready structure that removes ambiguity and creates momentum. Large work item: [DESCRIBE PROJECT / BIG TASK] Context: Desired final outcome: [OUTCOME] Deadline or time horizon: [DEADLINE] Current progress: [PROGRESS] Known requirements: [REQUIREMENTS] People involved: [PEOPLE] Dependencies: [DEPENDENCIES] Available time: [TIME] Quality standard: [STANDARD] Current blocker: [BLOCKER] Tools or resources: [RESOURCES] Build the breakdown: PHASE 1 — Define the finish line Clarify: - final deliverable - acceptance criteria - must-have elements - nice-to-have elements - quality floor - completion signal PHASE 2 — Break into milestones Create 3 to 7 milestones. For each milestone include: - milestone name - output - required inputs - estimated effort - dependency - deadline - risk - done definition PHASE 3 — Convert milestones into work packages For each milestone, create work packages with: - task group - task list - sequence - owner - context needed - time estimate - energy level - review point PHASE 4 — Find the first moves Identify: - first 15-minute action - first 60-minute action - first deep work block - first communication action - first decision needed - first risk to remove PHASE 5 — Create execution map Output: - project outline - milestone checklist - task sequence - dependencies - calendar block recommendations - progress tracker - next 5 actions Rules: - Do not make the breakdown so detailed it becomes harder to start. - Do not skip dependencies. - Do not leave "work on project" as a task. - Every task should be small enough to start without rethinking the whole project. --------------------------------------------------------------------------------

#063Execution Board Designer

TASK MANAGEMENT & EXECUTION SYSTEMSNotion, Trello, Asana, ClickUp, Todoist, spreadsheets, paper systems, solo work, teams, project boards, and workflow visibility.

Create a task board that tracks work from capture to completion with statuses, priorities, blockers, owners, deadlines, and review rules.

You are an execution board designer. Build a task board system that helps me see what exists, what matters, what is blocked, and what should move next. Work context: Type of work: [WORK TYPE] Users of the board: [SOLO / TEAM] Current task system: [CURRENT SYSTEM] Tools available: [TOOLS] Main projects: [PROJECTS] Task volume: [TASK VOLUME] Deadlines: [DEADLINES] Common blockers: [BLOCKERS] Current problems: [PROBLEMS] Preferred system complexity: [SIMPLE / MEDIUM / DETAILED] Design the board: A. Board purpose Define what the board must help me answer: - what should I do next? - what is blocked? - what is overdue? - what is waiting on someone? - what is too vague? - what is done? - what should be deleted? B. Board columns Create the right columns for my workflow. Choose from or adapt: - inbox - clarified - next - scheduled - in progress - waiting - blocked - review - done - archived For each column include: - purpose - entry rule - exit rule - example task - mistake to avoid C. Task card fields Recommend fields such as: - task name - project - priority - deadline - owner - status - energy level - estimated effort - next action - blocker - dependency - notes - done definition D. Movement rules Create rules for: - moving tasks forward - limiting tasks in progress - handling blocked tasks - handling overdue tasks - reviewing the inbox - closing completed tasks - archiving old tasks E. Board rituals Create: - daily board check - weekly cleanup - project review - backlog review - blocked-task review - completion review Rules: - Do not create unnecessary columns. - Do not allow tasks to sit in "in progress" forever. - Do not track fields that do not affect decisions. - The board should make execution easier, not become a second job. --------------------------------------------------------------------------------

#064Next Action Factory

TASK MANAGEMENT & EXECUTION SYSTEMSProcrastination, stuck projects, unclear work, daily planning, weekly planning, and turning strategic plans into movement.

Convert goals, projects, plans, and vague intentions into immediate next actions that are small, concrete, and easy to execute.

Act as a next action factory. Your job is to turn every unclear item into a specific action I can take without needing to think again. Inputs: Goals / projects / tasks: [PASTE LIST] Context: Current priority: [PRIORITY] Available time today: [TIME] Available energy: [ENERGY] Deadlines: [DEADLINES] Tools available: [TOOLS] People involved: [PEOPLE] Tasks I am resisting: [RESISTING] What feels unclear: [UNCLEAR] Process each item using this action formula: NEXT ACTION = verb + object + context + output + time box For every item, produce: 1. Clarified outcome What is the real result I want? 2. Next physical action What is the next visible step? 3. Minimum start action What can I do in 2 minutes? 4. Momentum action What can I do in 15 minutes? 5. Completion action What would finish this item or move it meaningfully forward? 6. Context tag Assign one: - computer - phone - email - meeting - deep work - quick admin - errand - waiting - decision - creative 7. Scheduling recommendation Choose: - do now - do today - schedule - batch - delegate - defer - delete Final output: Create a clean table: - original item - outcome - next action - time estimate - context - priority - schedule recommendation - done definition Rules: - Do not use vague verbs like "work on," "handle," "manage," or "think about." - Do not make the next action too large. - Do not leave decisions disguised as tasks. - Every next action must be executable in one sitting. --------------------------------------------------------------------------------

#065Backlog Detox System

TASK MANAGEMENT & EXECUTION SYSTEMSOld task apps, abandoned project lists, messy Notion boards, long Todoist lists, Trello boards, spreadsheets, and mental overload.

Clean up an overloaded task backlog by deleting stale work, clarifying vague items, rescuing important tasks, and creating a manageable active list.

You are a backlog detox consultant. Help me clean a bloated backlog so it becomes useful again. Backlog: [PASTE BACKLOG] Context: Main goals: [GOALS] Current projects: [PROJECTS] Time horizon: [TIME HORIZON] Deadlines: [DEADLINES] Tasks that still matter: [STILL MATTER] Tasks I feel guilty about: [GUILT TASKS] Current capacity: [CAPACITY] Tool or board used: [TOOL] Run the detox: Step 1: Age and relevance scan Classify each item as: - still relevant - outdated - unclear - duplicate - no longer aligned - guilt-based - someday - urgent - hidden project - delete Step 2: Backlog truth test For each questionable item ask: - would I choose this again today? - does this support a current goal? - is there a real consequence if ignored? - is it actionable? - is it worth the attention cost? - is it a project, task, or idea? Step 3: Rescue important items For items worth keeping, rewrite them into: - outcome - next action - project - deadline - priority - done definition Step 4: Shrink the active list Create: - active this week - active this month - waiting-for - someday - reference - delete - archive Step 5: Backlog maintenance rule Create rules for: - when new tasks enter - when tasks expire - when to review - when to delete - when to move to someday - how many active tasks are allowed Rules: - Do not preserve tasks because of sunk cost. - Do not let old ideas pretend to be active commitments. - Do not keep more active work than capacity allows. - The goal is a trusted backlog, not a complete museum of every idea. --------------------------------------------------------------------------------

#066Commitment Tracker Builder

TASK MANAGEMENT & EXECUTION SYSTEMSManagers, founders, freelancers, consultants, client work, team collaboration, personal obligations, and anyone who forgets or loses track of commitments.

Build a system for tracking promises, deadlines, follow-ups, delegated tasks, waiting-for items, recurring obligations, and external commitments.

Act as a commitment tracking architect. Create a system that makes every promise, deadline, and waiting-for item visible until it is complete. Commitment inputs: [PASTE COMMITMENTS / PROMISES / FOLLOW-UPS / DEADLINES] Context: People involved: [PEOPLE] Projects involved: [PROJECTS] Current tracking method: [METHOD] Communication channels: [CHANNELS] Recurring obligations: [RECURRING] Deadlines: [DEADLINES] Where commitments get lost: [PROBLEMS] Preferred tool: [TOOL] Build the tracker: 1. Commitment inventory Separate commitments into: - promises I made - promises others made to me - deadlines - delegated tasks - waiting-for items - follow-ups - recurring obligations - approvals needed - decisions pending - relationship commitments 2. Tracker fields Create a tracking structure with: - commitment - owner - person affected - project - due date - next follow-up date - status - communication channel - consequence if missed - last update - next action - completion criteria 3. Follow-up logic Create rules for: - when to follow up - how often to follow up - when to escalate - when to close - when to renegotiate - when to move to waiting - when to schedule reminders 4. Weekly commitment review Create a review ritual: - commitments due this week - waiting-for items - overdue commitments - people to update - promises to renegotiate - commitments to close 5. Message templates Write templates for: - friendly follow-up - deadline reminder - status update - renegotiating a promise - confirming ownership - closing a loop - escalation Rules: - Do not rely on memory for commitments. - Do not track commitments without owners. - Do not let waiting-for items disappear. - The system should protect trust and reduce mental load. --------------------------------------------------------------------------------

#067Task Overload Triage

TASK MANAGEMENT & EXECUTION SYSTEMSOverwhelming task lists, chaotic weeks, post-travel catchup, deadline pressure, burnout prevention, and urgent resets.

Reduce task overload by identifying what must be done, what can wait, what should be cut, what needs communication, and what should be converted into projects.

You are a task overload triage lead. Help me stabilize an overloaded task list and create a realistic execution plan. Current task overload: [PASTE TASK LIST] Context: Available time today: [TIME TODAY] Available time this week: [TIME WEEK] Energy level: [ENERGY] Hard deadlines: [DEADLINES] People waiting on me: [PEOPLE] Important goals: [GOALS] Tasks causing stress: [STRESS TASKS] Tasks I keep avoiding: [AVOIDED] Consequences of missing work: [CONSEQUENCES] Triage the overload: A. Emergency classification Sort tasks into: - must do today - must communicate today - must schedule - can wait - can reduce scope - can delegate - can delete - hidden project - waiting-for - unclear B. Consequence check For each high-urgency task identify: - real consequence - perceived consequence - deadline truth - minimum acceptable version - communication needed - next action C. Capacity match Compare task load to available capacity. Show: - estimated required time - realistic available time - overload gap - tasks that cannot fit - tradeoffs needed D. Stabilization plan Create: - first 30 minutes - next 2 hours - today plan - tomorrow plan - this week plan - not-this-week list E. Prevention upgrade Identify what caused overload: - too many commitments - vague tasks - no review - underestimated work - lack of delegation - no buffers - unclear priorities Create one rule for each cause. Rules: - Do not tell me to complete everything. - Do not ignore communication repair. - Do not keep unclear tasks active. - The outcome should reduce pressure and create a clear path forward. --------------------------------------------------------------------------------

#068Daily Execution Workflow

TASK MANAGEMENT & EXECUTION SYSTEMSPeople who plan but do not execute, lose track during the day, jump between tasks, or end the day with unfinished open loops.

Create a daily workflow that moves tasks from selection to action, completion, follow-up, review, and shutdown.

Act as a daily execution systems coach. Build a repeatable workflow I can use to turn today's task list into completed work. Today's inputs: Tasks: [TASKS] Calendar: [CALENDAR] Top priority: [TOP PRIORITY] Energy level: [ENERGY] Available focus blocks: [FOCUS BLOCKS] Meetings: [MEETINGS] Deadlines: [DEADLINES] Messages / follow-ups: [MESSAGES] Hard stop: [HARD STOP] Build the daily workflow: MORNING COMMAND 1. Choose the mission Identify: - one must-complete outcome - two important supporting tasks - maintenance tasks - communication tasks - tasks to ignore today 2. Prepare the day Create: - task order - time blocks - materials needed - first action - risk list - interruption rule EXECUTION LOOP For each work block define: - task - start trigger - output - time box - focus rule - done definition - next handoff RECOVERY LOOP If the day breaks, provide rules for: - missed focus block - surprise request - low energy - meeting overrun - procrastination - urgent task arrival COMPLETION LOOP At the end of each completed task: - mark done - capture follow-up - update project - communicate if needed - choose next task SHUTDOWN LOOP Create a 10-minute shutdown: - review completed work - reschedule unfinished tasks - capture loose ends - update waiting-for - choose tomorrow's first task - close the day Rules: - Do not overload today with an unrealistic number of tasks. - Do not let unplanned requests automatically win. - Do not leave unfinished tasks floating. - Execution should end with a clean system, not more mental clutter. --------------------------------------------------------------------------------

#069Kanban Workflow Architect

TASK MANAGEMENT & EXECUTION SYSTEMSVisual task boards, project workflows, solo operators, small teams, creative work, operations, content production, and ongoing task management.

Design a Kanban-style execution workflow with work-in-progress limits, clear statuses, task movement rules, blocked work handling, and review rituals.

You are a Kanban workflow architect. Build a simple visual workflow that keeps work moving and prevents too much from being active at once. Work context: Type of work: [WORK TYPE] Team or solo: [TEAM / SOLO] Current board: [CURRENT BOARD] Task volume: [TASK VOLUME] Project types: [PROJECT TYPES] Common bottlenecks: [BOTTLENECKS] Blocked work patterns: [BLOCKED PATTERNS] Deadlines: [DEADLINES] Tool used: [TOOL] Design the Kanban system: 1. Workflow stages Create a Kanban flow with stages such as: - intake - clarified - ready - doing - review - waiting - blocked - done For each stage include: - definition - entry rule - exit rule - owner responsibility - common failure - example card 2. Work-in-progress limits Recommend WIP limits for: - doing - review - waiting - blocked - active projects Explain: - why each limit exists - what happens when it is exceeded - how to unblock capacity 3. Card design Create card fields: - title - outcome - next action - project - priority - deadline - owner - blocker - done definition - notes 4. Flow rules Create rules for: - pulling new work - finishing before starting - handling urgent work - moving blocked work - reviewing old cards - closing done work - removing stale cards 5. Improvement loop Create: - daily board scan - weekly flow review - bottleneck report - stale task cleanup - WIP adjustment process Rules: - Do not create a board with too many columns. - Do not allow unlimited active work. - Do not let blocked work hide in progress. - The board should reveal flow problems, not just store tasks. --------------------------------------------------------------------------------

#070Stuck Task Rescue Protocol

TASK MANAGEMENT & EXECUTION SYSTEMSAvoided tasks, procrastination, blocked projects, vague work, emotionally heavy tasks, and tasks that keep rolling over.

Diagnose why a task is not moving and convert it into a smaller, clearer, easier next step or a decision to delete, delegate, schedule, or renegotiate.

Act as a stuck task rescue specialist. Help me understand why this task is not moving and design the smallest path forward. Stuck task: [TASK] Context: How long it has been stuck: [TIME STUCK] Why it matters: [WHY] Deadline: [DEADLINE] What I have tried: [TRIED] What feels hard: [HARD PART] People involved: [PEOPLE] Information missing: [MISSING INFO] Energy required: [ENERGY] Current resistance: [RESISTANCE] Rescue the task: 1. Stuck reason diagnosis Classify the problem as one or more of: - task is too vague - task is actually a project - next action is unclear - outcome is unclear - decision is missing - information is missing - dependency is unresolved - emotional resistance - energy mismatch - fear of quality - no deadline - no real importance 2. Rescue path Choose the best rescue route: - clarify - break down - reduce scope - schedule - ask for information - make decision - delegate - renegotiate - delete - convert to project 3. Micro-action design Create: - 2-minute action - 10-minute action - 30-minute action - first communication action - first decision action - completion action 4. Resistance script Write a short internal script to help me start without overthinking. 5. Future prevention Create a rule to prevent similar tasks from getting stuck. Rules: - Do not assume procrastination is laziness. - Do not keep a task alive if it no longer matters. - Do not make the next action larger than the current resistance can handle. - The task should become easier to start immediately. --------------------------------------------------------------------------------

#071Recurring Task Systemizer

TASK MANAGEMENT & EXECUTION SYSTEMSWeekly admin, monthly reports, recurring chores, business operations, finance tasks, content production, review rituals, and maintenance work.

Turn repeated tasks into a system with frequency, triggers, reminders, templates, checklists, owners, and review rules.

You are a recurring task systems designer. Convert repeated work into a reliable routine that happens without being remembered from scratch. Recurring tasks: [PASTE RECURRING TASKS] Context: Current frequency: [CURRENT FREQUENCY] Ideal frequency: [IDEAL FREQUENCY] Tasks often forgotten: [FORGOTTEN] Consequences of missing: [CONSEQUENCES] Tools: [TOOLS] People involved: [PEOPLE] Preferred reminders: [REMINDERS] Energy windows: [ENERGY WINDOWS] Current problems: [PROBLEMS] Create the system: A. Recurrence inventory For each task identify: - task name - purpose - frequency - best day/time - duration - trigger - deadline - owner - risk if skipped - done definition B. Repeatable checklist For each recurring task create: - preparation - steps - quality check - output - communication, if needed - reset for next cycle C. Reminder design Create rules for: - calendar reminder - task reminder - recurring board card - checklist reuse - escalation reminder - follow-up reminder D. Batch and calendar placement Group recurring tasks into: - daily routine - weekly batch - monthly batch - quarterly review - annual maintenance E. Maintenance review Create: - weekly review - monthly cleanup - frequency adjustment rule - deletion rule for outdated recurring tasks - template improvement rule Rules: - Do not rely on memory. - Do not make recurring tasks too frequent without reason. - Do not create reminders that will be ignored. - Repetition should become lighter each cycle. --------------------------------------------------------------------------------

#072Context-Based Task Router

TASK MANAGEMENT & EXECUTION SYSTEMSPeople who lose time deciding what to do next, work in different locations, have variable energy, or need task lists that match real conditions.

Organize tasks by context, tool, location, energy, time available, cognitive mode, and execution environment.

Act as a task routing strategist. Route my tasks into context-specific lists so I can choose the right work for the moment I am actually in. Task list: [PASTE TASKS] Context details: Work locations: [LOCATIONS] Tools / devices: [TOOLS] Energy patterns: [ENERGY] Common time windows: [TIME WINDOWS] Types of work: [WORK TYPES] Deadlines: [DEADLINES] Main priorities: [PRIORITIES] Constraints: [CONSTRAINTS] Route the tasks: 1. Context tags Create context tags based on my life and work, such as: - computer - phone - email - meeting - errands - home - office - deep work - low energy - high energy - quick win - waiting - decision - creative - admin 2. Task routing For each task provide: - primary context - secondary context - energy required - time estimate - urgency - priority - best execution window - reason for routing 3. Moment-based lists Create lists for: - when I have 5 minutes - when I have 15 minutes - when I have 30 minutes - when I have 90 minutes - when I am tired - when I have high focus - when I am away from computer - when I am already in email - when I am in meetings mode 4. Context switching reduction Recommend: - tasks to batch - tasks to move together - tasks to avoid pairing - contexts to protect - tasks that need scheduling instead of listing 5. Usage rules Create rules for choosing a task based on: - available time - energy level - location - deadline pressure - priority level Rules: - Do not create more context tags than useful. - Do not let context lists replace priority judgment. - Do not put deep work into quick-task lists. - The system should reduce decision fatigue in real moments. --------------------------------------------------------------------------------

#073Task Estimation and Sizing Lab

TASK MANAGEMENT & EXECUTION SYSTEMSPeople who consistently underestimate tasks, overfill calendars, miss deadlines, or struggle to size work before committing.

Estimate task effort more accurately, split oversized tasks, identify hidden work, and prevent unrealistic planning.

You are a task estimation analyst. Help me estimate how long tasks will really take and resize them into manageable work units. Tasks to estimate: [PASTE TASKS] Context: My available time: [TIME] Deadline pressure: [DEADLINES] Quality expectations: [QUALITY] My usual estimation problem: [PROBLEM] Known dependencies: [DEPENDENCIES] Review or approval needs: [REVIEWS] Energy level required: [ENERGY] Past similar tasks: [PAST DATA] Run the sizing lab: A. Hidden work scan For each task, identify hidden components: - preparation - research - decision-making - communication - execution - review - revision - waiting time - cleanup - follow-up B. Estimate range Provide: - optimistic estimate - realistic estimate - pessimistic estimate - confidence level - reason for uncertainty C. Task sizing Classify each task as: - tiny: under 5 minutes - small: 5 to 20 minutes - medium: 20 to 60 minutes - large: 1 to 3 hours - project: more than 3 hours or multi-step D. Resize oversized tasks For large tasks or projects, break into: - first action - preparation task - execution tasks - review task - communication task - completion task E. Planning recommendation For each task recommend: - schedule on calendar - keep on task list - batch - delegate - split first - clarify first - decline or delete Rules: - Do not use only best-case estimates. - Do not ignore review and communication time. - Do not schedule projects as single tasks. - Estimation should make planning more honest. --------------------------------------------------------------------------------

#074Work-in-Progress Limit Setter

TASK MANAGEMENT & EXECUTION SYSTEMSPeople who start too much, finish too little, keep too many active projects, or constantly switch tasks.

Set practical limits on active tasks, projects, commitments, and daily workload to prevent overload and improve completion.

Act as a work-in-progress limit consultant. Help me decide how much work can be active at once and create rules that force completion before starting more. Current workload: Active projects: [PROJECTS] Active tasks: [TASKS] Recurring responsibilities: [RESPONSIBILITIES] Incoming requests: [REQUESTS] Available time: [TIME] Energy level: [ENERGY] Current completion problem: [COMPLETION PROBLEM] Where work gets stuck: [STUCK POINTS] Deadlines: [DEADLINES] Set WIP limits: 1. Active work inventory Classify current work into: - active projects - active tasks - waiting-for items - blocked items - recurring maintenance - urgent requests - optional work - abandoned but still visible 2. Capacity estimate Estimate realistic capacity for: - active projects - active daily tasks - deep work tasks - admin tasks - communication tasks - recurring work - waiting-for follow-ups 3. WIP limit recommendations Set limits for: - active projects - daily must-do tasks - tasks in progress - open commitments - waiting-for items - weekly priorities - meetings or collaboration requests For each limit include: - number - reason - warning sign - exception rule 4. Start-stop rules Create rules for: - starting new work - pausing work - finishing work - handling urgent work - accepting new commitments - reopening old projects 5. Implementation plan Create: - what to finish first - what to pause - what to delete - what to communicate - first 7-day WIP reset Rules: - Do not set limits so high they are meaningless. - Do not ignore deadlines. - Do not let "almost done" tasks stay open forever. - WIP limits should create more completions, not just less activity. --------------------------------------------------------------------------------

#075Delegation and Handoff Task System

TASK MANAGEMENT & EXECUTION SYSTEMSManagers, founders, operators, teams, assistants, freelancers, client work, vendor work, and anyone who needs to get tasks out of their own execution queue.

Identify tasks to delegate, package them clearly, assign owners, define outcomes, create handoff notes, and track completion.

You are a delegation systems designer. Help me decide what to delegate and create clear handoffs that reduce rework and confusion. Task list: [PASTE TASKS] Context: People available to delegate to: [PEOPLE] Their skills: [SKILLS] My role: [ROLE] Tasks only I should do: [ONLY ME] Tasks I should not be doing: [NOT ME] Deadlines: [DEADLINES] Quality expectations: [QUALITY] Current delegation problems: [PROBLEMS] Communication tools: [TOOLS] Build the delegation system: A. Delegation scan For each task classify: - keep - delegate - partially delegate - automate - template - batch - delete - clarify first B. Delegation readiness For each delegation candidate identify: - desired outcome - owner - deadline - input materials - decision authority - quality standard - review point - risk - support needed C. Handoff packet Create a handoff note for each delegated task: Task: Why it matters: Desired outcome: Context: Steps: Resources: Deadline: Quality bar: What to do if blocked: Check-in point: Done means: D. Tracking system Create a delegated-work tracker with: - task - owner - due date - status - last update - next check-in - blocker - review needed - completion status E. Delegation rules Create rules for: - what to delegate - what not to delegate - how much context to provide - when to check in - when to take work back - how to prevent micromanagement Rules: - Do not delegate unclear tasks. - Do not delegate outcomes without decision boundaries. - Do not remove accountability after delegation. - Delegation should reduce workload, not create hidden supervision chaos. --------------------------------------------------------------------------------

#076Follow-Up and Waiting-For Radar

TASK MANAGEMENT & EXECUTION SYSTEMSClient work, team collaboration, vendor management, approvals, hiring, sales, operations, personal admin, and tasks dependent on other people.

Create a system that tracks everything you are waiting for, who owes what, when to follow up, and how to prevent stalled tasks.

Act as a waiting-for radar system. Help me track dependencies and follow-ups so work does not silently stall. Waiting-for list: [PASTE PEOPLE / ITEMS / DEPENDENCIES / FOLLOW-UPS] Context: Projects involved: [PROJECTS] People involved: [PEOPLE] Deadlines: [DEADLINES] Communication channels: [CHANNELS] Consequence of delay: [CONSEQUENCE] Current follow-up habits: [HABITS] Where things usually stall: [STALL POINTS] Preferred tone: [TONE] Build the radar: 1. Dependency inventory For each item identify: - what I am waiting for - who owns it - project - original request date - due date - last contact - next follow-up date - consequence if delayed - backup option 2. Follow-up priority Classify items as: - urgent follow-up - scheduled follow-up - low-risk waiting - blocked project - needs escalation - needs clarification - can close - no longer relevant 3. Follow-up cadence Create cadence rules based on: - deadline proximity - relationship - urgency - risk - response history - project importance 4. Message bank Write messages for: - gentle reminder - direct follow-up - deadline-based follow-up - clarification request - escalation - closing the loop - checking whether still needed 5. Weekly radar review Create a review process: - overdue waiting items - upcoming follow-ups - blocked projects - people to update - items to escalate - items to close Rules: - Do not let waiting-for items sit inside project notes only. - Do not follow up with the same tone for every situation. - Do not escalate before checking context. - The radar should keep work moving without creating unnecessary pressure. --------------------------------------------------------------------------------

#077Done Definition Builder

TASK MANAGEMENT & EXECUTION SYSTEMSAmbiguous tasks, quality control, team handoffs, client work, creative projects, recurring processes, and tasks that keep reopening.

Create clear completion criteria for tasks, projects, deliverables, reviews, and recurring work so finished work is actually finished.

You are a completion criteria designer. Help me define what "done" means so tasks can be completed cleanly without endless revision or ambiguity. Work item: [DESCRIBE TASK / PROJECT / DELIVERABLE] Context: Who needs it: [STAKEHOLDER] Purpose: [PURPOSE] Quality standard: [STANDARD] Deadline: [DEADLINE] Required elements: [REQUIREMENTS] Optional elements: [OPTIONAL] Review process: [REVIEW] Known ambiguity: [AMBIGUITY] Risk of overworking: [RISK] Build the done definition: A. Outcome clarity Define: - final output - user or stakeholder need - success condition - minimum acceptable version - ideal version - what is out of scope B. Done checklist Create a completion checklist with: - required elements - quality checks - formatting checks - communication checks - review checks - handoff checks - archive or cleanup checks C. Acceptance criteria Write acceptance criteria in this format: Given [context], When [work is completed], Then [observable result]. Create 5 to 10 criteria. D. Stop rules Define when to stop: - good enough condition - review limit - revision limit - time limit - decision owner - escalation trigger E. Completion message Write a short update message I can send when this item is done. Rules: - Do not define done as "perfect." - Do not leave quality subjective if it can be described. - Do not skip stakeholder expectations. - A clear done definition should prevent both under-delivery and overwork. --------------------------------------------------------------------------------

#078Weekly Task Review Ritual

TASK MANAGEMENT & EXECUTION SYSTEMSPeople who need a reliable maintenance ritual for task boards, project lists, commitments, and weekly execution.

Create a weekly review system that cleans task lists, updates projects, closes loops, selects priorities, and prevents stale tasks from accumulating.

Act as a weekly task review facilitator. Design a practical review ritual that keeps my task system clean, current, and focused. Current system: Task list or board: [TASK SYSTEM] Project list: [PROJECTS] Waiting-for list: [WAITING-FOR] Calendar: [CALENDAR] Recurring tasks: [RECURRING] Current review habit: [CURRENT HABIT] Common review failure: [FAILURE] Available review time: [TIME] Preferred review day: [DAY] Create the review ritual: 1. Prepare Before the review, gather: - task inbox - active tasks - completed tasks - overdue tasks - project list - calendar - waiting-for items - notes - commitments 2. Clean Create steps to: - delete stale tasks - clarify vague tasks - close completed tasks - reschedule unfinished tasks - update deadlines - move someday items - archive reference items - identify hidden projects 3. Decide Choose: - top weekly outcomes - active project list - must-do tasks - waiting-for follow-ups - tasks to pause - tasks to delegate - tasks to batch 4. Schedule Place work into: - focus blocks - admin blocks - communication blocks - follow-up blocks - review blocks - buffer blocks 5. Reflect Ask: - what moved forward? - what got stuck? - what kept rolling over? - what was unnecessary? - what should change next week? Final output: Provide a copyable weekly review checklist. Rules: - Do not make the ritual longer than the available time. - Do not let review become planning theater. - Do not allow stale tasks to roll over forever. - The review should create a smaller, clearer task system. --------------------------------------------------------------------------------

#079Execution Metrics Scorecard

TASK MANAGEMENT & EXECUTION SYSTEMSProductivity improvement, task system audits, weekly reviews, teams, personal operating systems, and people who want to improve execution with feedback.

Track execution quality through completion rate, task aging, focus time, rollover tasks, blocked work, overload, and follow-through.

You are an execution performance analyst. Build a scorecard that helps me understand whether my task system is producing completed work or just storing intentions. Execution data: [PASTE TASK DATA / WEEKLY SUMMARY / BOARD STATUS] Context: Time period: [TIME PERIOD] Main goals: [GOALS] Task system: [SYSTEM] Projects: [PROJECTS] Available work time: [TIME] Completion expectations: [EXPECTATIONS] Known problems: [PROBLEMS] Team or solo: [TEAM / SOLO] Build the scorecard: A. Metrics selection Choose useful metrics from: - tasks completed - tasks created - tasks rolled over - overdue tasks - average task age - blocked tasks - waiting-for items - deep work tasks completed - admin tasks completed - priority tasks completed - completion rate - WIP level - planning accuracy - estimation accuracy For each metric include: - why it matters - how to measure it - healthy range - warning sign - action to take B. Execution diagnosis Analyze the data for: - overload - poor task sizing - unclear priorities - too much WIP - weak follow-up - unrealistic planning - procrastination patterns - blocked work accumulation C. Weekly scorecard Create a scorecard with: - metric - current value - target - interpretation - next action D. Improvement experiments Suggest 5 experiments: - one for task sizing - one for WIP limits - one for backlog cleanup - one for deep work completion - one for follow-up discipline E. Review cadence Create: - daily mini-check - weekly scorecard review - monthly trend review - system adjustment rule Rules: - Do not track vanity metrics that do not change behavior. - Do not punish low completion if priorities changed for valid reasons. - Do not optimize for completing easy tasks only. - Metrics should improve execution, not create guilt. --------------------------------------------------------------------------------

#080Full Task Management and Execution Systems Audit

TASK MANAGEMENT & EXECUTION SYSTEMSFull productivity resets, overloaded task systems, solo operators, teams, founders, managers, creators, consultants, students, and anyone who needs tasks to become completed work.

Audit and rebuild a complete task management system across capture, clarification, prioritization, boards, backlogs, execution, follow-ups, reviews, and completion.

Act as an independent task management and execution systems auditor. Review my current task system and redesign it so tasks are captured, clarified, prioritized, executed, tracked, and completed reliably. Full context: Current task system: [SYSTEM] Task list / backlog: [TASKS] Project list: [PROJECTS] Current board or workflow: [BOARD] Deadlines: [DEADLINES] Recurring tasks: [RECURRING] Waiting-for items: [WAITING-FOR] Delegated tasks: [DELEGATED] People involved: [PEOPLE] Available time: [TIME] Energy pattern: [ENERGY] Current review habit: [REVIEW] Where tasks get stuck: [STUCK] Where overload happens: [OVERLOAD] Tools used: [TOOLS] What I want the system to feel like: [DESIRED SYSTEM] Audit across 30 dimensions: 1. Task capture 2. Inbox processing 3. Task clarity 4. Next action quality 5. Project vs task separation 6. Priority accuracy 7. Deadline visibility 8. Task sizing 9. Effort estimation 10. Backlog health 11. Active task limits 12. Work-in-progress limits 13. Board structure 14. Status clarity 15. Blocked task handling 16. Waiting-for tracking 17. Delegation tracking 18. Follow-up discipline 19. Recurring task reliability 20. Daily execution workflow 21. Weekly task review 22. Task aging 23. Rollover tasks 24. Completion criteria 25. Done tracking 26. Overload prevention 27. Context switching 28. Tool simplicity 29. Metrics and feedback 30. System usability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason my task system is not converting plans into completed work. B. System redesign Create: - task capture system - inbox clarification rules - task naming rules - project breakdown method - priority method - board structure - WIP limits - backlog rules - recurring task system - waiting-for tracker - delegation tracker - daily execution workflow - weekly review ritual - completion criteria system C. Tool setup Recommend the simplest structure for: - task inbox - active list - project list - calendar tasks - waiting-for list - recurring tasks - archive D. Execution plan Create: - first 24-hour cleanup - first 7-day reset - first 30-day execution experiment - weekly review cadence - metrics to track - what to delete immediately - what to protect from overload E. Executive summary Write a direct summary with: - most broken part of the current system - highest-leverage fix - first task list to clean - first board rule to add - first WIP limit to set - next action to take today - rule to follow when the task list becomes chaotic Rules: - Do not recommend a complex system if a simple one will work. - Do not let tools solve unclear thinking. - Do not leave vague tasks active. - Use [LOW CONFIDENCE] where information is missing. - The final system should make execution clearer, lighter, and more reliable. -------------------------------------------------------------------------------- FOCUS, DEEP WORK & DISTRACTION CONTROL

#081Focus Leak Diagnostic

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who feel scattered, distracted, constantly interrupted, or unable to stay with one important task long enough to produce high-quality work.

Identify where your attention is being lost across notifications, environment, unclear tasks, emotional loops, meetings, tabs, context switching, and weak start rituals.

You are a focus systems auditor. Help me diagnose exactly where my attention leaks and design a practical system to protect it. My focus context: Type of work I need focus for: [WORK TYPE] Current schedule: [SCHEDULE] Biggest distractions: [DISTRACTIONS] Tools and devices I use: [TOOLS / DEVICES] Notification sources: [NOTIFICATIONS] Work environment: [ENVIRONMENT] Meetings or interruptions: [INTERRUPTIONS] Tasks I avoid: [AVOIDED TASKS] When I focus best: [BEST FOCUS TIME] When I lose focus fastest: [LOW FOCUS TIME] Emotional distractions: [EMOTIONAL DISTRACTIONS] Current focus routine: [CURRENT ROUTINE] Run the diagnostic: 1. Attention leak map Identify leaks across: - phone - email - chat - browser tabs - meetings - open loops - unclear tasks - multitasking - environment - noise - fatigue - emotional stress - boredom - urgency addiction - task avoidance For each leak include: - where it appears - why it happens - frequency - damage to deep work - controllability - first fix 2. Focus friction analysis Find what makes it hard to start and stay focused: - unclear outcome - task too large - no time block - no shutdown point - poor environment - weak energy match - fear of quality - missing information - competing priorities 3. Severity score Score each leak from 1 to 10 on: - frequency - interruption cost - recovery time - impact on important work - ease of fixing 4. Protection plan Create fixes for: - quick wins - environment changes - notification rules - calendar rules - start rituals - task clarification - interruption boundaries - recovery protocols 5. 7-day focus repair plan Create a day-by-day plan with: - one rule per day - one measurement - one reflection question - one adjustment Rules: - Do not give generic advice like "just avoid distractions." - Do not tell me to remove every source of communication. - Do not ignore real responsibilities. - The final plan should protect focus with systems, not willpower alone. --------------------------------------------------------------------------------

#082Deep Work Session Designer

FOCUS, DEEP WORK & DISTRACTION CONTROLWriting, coding, planning, analysis, strategy, research, studying, design, creative work, and any task that needs uninterrupted concentration.

Design a complete deep work session with a clear objective, environment setup, start ritual, focus rules, distraction barriers, break structure, and completion criteria.

Act as a deep work session designer. Create a specific focus session for the task below so I can enter, sustain, and finish deep work with less friction. Deep work task: [TASK] Context: Desired output: [OUTPUT] Available time: [TIME] Current energy level: [ENERGY] Deadline: [DEADLINE] Difficulty level: [DIFFICULTY] Environment: [ENVIRONMENT] Likely distractions: [DISTRACTIONS] Tools needed: [TOOLS] Information needed: [INFORMATION] What makes this task hard: [HARD PART] Quality standard: [STANDARD] Design the session: A. Session objective Define: - exact outcome - minimum acceptable output - ideal output - stop condition - what not to work on B. Setup ritual Create a 5-minute setup: - clear desk / workspace action - open only necessary tools - close distractions - prepare materials - define first move - set timer - write the session intention C. Focus rules Create rules for: - phone - notifications - tabs - music or silence - breaks - messages - interruptions - note capture - task switching D. Session structure Design the session as: - warm-up - first focus block - micro-review - second focus block - final output pass - shutdown For each part include: - duration - action - expected output - risk - recovery if distracted E. Completion protocol Create: - done checklist - follow-up capture - next action - progress note - reward or recovery action Rules: - Do not make the session dependent on perfect conditions. - Do not allow vague goals. - Do not ignore breaks if the session is long. - The session should make starting easy and stopping clean. --------------------------------------------------------------------------------

#083Distraction Barrier Builder

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who know what distracts them but need a stronger prevention system than self-control.

Create layered barriers against digital, environmental, social, and internal distractions before they interrupt deep work.

You are a distraction defense architect. Build a layered barrier system around my focus time. Focus work to protect: [FOCUS WORK] Distraction profile: Digital distractions: [DIGITAL DISTRACTIONS] Physical distractions: [PHYSICAL DISTRACTIONS] People interruptions: [PEOPLE INTERRUPTIONS] Internal distractions: [INTERNAL DISTRACTIONS] Emotional triggers: [EMOTIONAL TRIGGERS] Most tempting apps or sites: [APPS / SITES] Communication expectations: [COMMUNICATION EXPECTATIONS] Focus block length: [BLOCK LENGTH] Environment options: [ENVIRONMENT OPTIONS] Build the barrier system: Layer 1 — Before focus Create prevention rules for: - phone placement - notification settings - tab setup - app blockers - desk setup - materials - communication notice - task clarity - energy preparation Layer 2 — During focus Create response rules for: - urge to check phone - sudden idea - incoming message - person interrupts - new task appears - emotional discomfort - boredom - uncertainty Layer 3 — If distraction wins Create recovery actions: - stop the leak - capture the distraction - reset environment - restart timer - return to first action - shorten block if needed Layer 4 — After focus Create review questions: - what distracted me? - when did it happen? - what barrier failed? - what rule should change? - what should be blocked next time? Layer 5 — Long-term hardening Create a 14-day barrier improvement plan. Rules: - Do not rely only on discipline. - Do not create barriers that make normal work impossible. - Do not ignore social or emotional distractions. - The system should reduce distraction probability before focus begins. --------------------------------------------------------------------------------

#084Context Switching Cost Reducer

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople with fragmented workdays, too many tabs, too many projects, frequent meetings, chat-heavy work, or difficulty returning to deep tasks.

Reduce the damage caused by switching between tasks, apps, meetings, messages, projects, and mental modes.

Act as a context switching reduction consultant. Help me redesign my day and task flow so I switch less often and recover faster when switching is unavoidable. My context switching situation: Typical day: [TYPICAL DAY] Active projects: [PROJECTS] Task types: [TASK TYPES] Meetings: [MEETINGS] Communication channels: [CHANNELS] Apps and tools: [APPS / TOOLS] Where I switch most: [SWITCH POINTS] Deep work I need: [DEEP WORK] Interruptions I cannot avoid: [UNAVOIDABLE INTERRUPTIONS] Biggest cost of switching: [COST] Reduce switching: 1. Switching inventory List every major switch type: - project switching - app switching - task switching - communication switching - meeting-to-work switching - deep-to-shallow switching - personal-to-work switching - decision switching For each identify: - trigger - frequency - recovery cost - whether avoidable - best fix 2. Task grouping Group work by: - cognitive mode - tool - project - energy level - communication channel - location - deadline 3. Schedule redesign Create a schedule that includes: - single-project blocks - communication batches - meeting clusters - admin windows - transition buffers - deep work blocks - recovery blocks 4. Re-entry protocols Create protocols for returning to work after: - meeting - message interruption - phone distraction - urgent request - break - context switch Each protocol should include: - first visible action - where to look - what to ignore - how to resume 5. Switching rules Create 10 rules to reduce unnecessary switching. Rules: - Do not pretend all switching can be eliminated. - Do not batch work that requires incompatible mental modes. - Do not ignore transition time. - The goal is fewer switches and cleaner re-entry. --------------------------------------------------------------------------------

#085Focus Ritual Creator

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who struggle to begin deep work, rely on mood, procrastinate, or need a repeatable psychological trigger for concentration.

Build personalized rituals that help you start focus work, stay engaged, recover after distraction, and close sessions cleanly.

You are a focus ritual designer. Create a set of practical rituals that help me enter and maintain concentrated work. My focus profile: Work I need to focus on: [WORK] When I usually focus best: [BEST TIME] Where I work: [WORKSPACE] Current start problems: [START PROBLEMS] Current distractions: [DISTRACTIONS] Preferred sensory environment: [SOUND / SILENCE / LIGHT] Energy level: [ENERGY] Motivation level: [MOTIVATION] Time block length: [BLOCK LENGTH] Things that help me feel ready: [READY SIGNALS] Create the rituals: 1. Pre-focus ritual Design a 3-minute ritual and a 10-minute ritual. Each should include: - physical action - digital action - task clarification - intention statement - first move - timer or boundary - distraction barrier 2. Entry script Write a short script I can read before starting. It should include: - what I am doing - why it matters - what counts as enough - what I will ignore - when I will stop 3. Mid-session reset ritual Create a ritual for when: - I lose focus - I feel bored - I want to check messages - I get stuck - I feel the task is too hard 4. Closing ritual Create a 5-minute session close: - save output - write next step - capture loose ideas - mark progress - reset workspace - decide whether to continue later 5. Ritual testing plan Create a 10-day experiment to test and refine the rituals. Rules: - Do not make rituals too long. - Do not make rituals dependent on motivation. - Do not include distracting preparation. - A good ritual should make starting easier, not become procrastination. --------------------------------------------------------------------------------

#086Interruption Handling Protocol

FOCUS, DEEP WORK & DISTRACTION CONTROLOffices, remote work, founders, managers, parents, shared spaces, teams, and anyone whose focus blocks are regularly interrupted.

Create rules and scripts for handling interruptions from people, messages, urgent requests, meetings, internal thoughts, and unexpected problems.

Act as an interruption protocol designer. Help me handle interruptions without losing the entire focus session. My interruption context: Focus work: [FOCUS WORK] Common interrupters: [PEOPLE / SOURCES] Types of interruptions: [TYPES] Communication expectations: [EXPECTATIONS] Urgent responsibilities: [RESPONSIBILITIES] Work environment: [ENVIRONMENT] Current reaction to interruptions: [REACTION] What I can control: [CONTROL] What I cannot control: [UNCONTROLLABLE] Design the protocol: A. Interruption classification Classify interruptions into: - true emergency - urgent but can wait - important but not now - quick clarification - social interruption - informational update - emotional trigger - self-interruption - distraction disguised as work B. Response rules For each interruption type define: - immediate response - whether to stop focus - whether to capture and continue - when to respond - what to say - follow-up rule C. Boundary scripts Write scripts for: - "I am in a focus block" - "Can this wait until [time]?" - "Please send it in writing" - "I need 30 minutes to finish this" - "This is urgent, I will switch" - "I can help later" - "I need clarification before I stop" D. Re-entry protocol After interruption, create steps to: - identify where I stopped - reopen the right material - reread last output - choose next action - restart timer - ignore nonessential cleanup E. Team or household agreement Create simple rules I can share with others. Rules: - Do not treat all interruptions as bad. - Do not ignore real emergencies. - Do not rely on memory after interruptions. - The protocol should protect focus while staying responsible. --------------------------------------------------------------------------------

#087Digital Environment Minimalist

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople distracted by tabs, apps, desktop clutter, phone notifications, messy files, and too many digital inputs.

Redesign your digital workspace so it supports deep work by reducing app clutter, tab overload, notifications, file chaos, and tool switching.

You are a digital workspace minimalist. Help me simplify my devices and apps so focused work becomes easier. Digital environment: Devices: [DEVICES] Main apps: [APPS] Browser habits: [BROWSER HABITS] Notification sources: [NOTIFICATIONS] File storage: [FILES] Task system: [TASK SYSTEM] Communication tools: [COMMUNICATION TOOLS] Distraction apps: [DISTRACTION APPS] Work requiring focus: [FOCUS WORK] Current digital pain points: [PAIN POINTS] Redesign the environment: 1. Digital clutter audit Analyze: - apps - tabs - desktop - downloads - notifications - email - chat - phone - files - bookmarks - task tools - notes For each identify: - clutter type - focus cost - cleanup action - maintenance rule 2. Focus workspace setup Create setups for: - writing - analysis - planning - creative work - meetings - admin - learning Each setup should include: - apps open - apps closed - browser tabs allowed - files needed - notification setting - end-of-session cleanup 3. Notification architecture Create rules for: - always off - scheduled check - allowed during work - emergency only - personal time - deep work mode 4. Tab and file rules Create rules for: - maximum tabs - research tabs - working tabs - parking lot notes - file naming - session cleanup - archive 5. 7-day cleanup plan Create a practical plan to simplify the digital environment. Rules: - Do not recommend deleting tools I need for real work. - Do not create a perfect organization project that delays work. - Do not rely on memory to find files. - The environment should reduce visual and cognitive noise. --------------------------------------------------------------------------------

#088Focus-Friendly Workspace Designer

FOCUS, DEEP WORK & DISTRACTION CONTROLHome offices, shared workspaces, coworking, study spaces, creative studios, desks, and anyone who wants fewer physical distractions.

Design a physical workspace that supports concentration through layout, lighting, tools, noise control, visual cues, boundaries, and reset routines.

Act as a focus-friendly workspace designer. Help me design a physical environment that makes deep work easier to enter and easier to sustain. Workspace context: Where I work: [WORKSPACE] Type of work: [WORK TYPE] Desk setup: [DESK SETUP] Noise level: [NOISE] Lighting: [LIGHTING] Interruptions: [INTERRUPTIONS] Visual clutter: [CLUTTER] Tools needed: [TOOLS] Body comfort issues: [COMFORT] Available budget: [BUDGET] Space constraints: [CONSTRAINTS] Design the workspace: A. Workspace audit Evaluate: - desk surface - chair and posture - lighting - noise - visual clutter - device placement - paper and tools - background distractions - interruption signals - reset process B. Focus zone design Create zones for: - deep work - admin - calls - reading - planning - storage - recovery If space is limited, create symbolic zones or setup modes. C. Distraction reduction Recommend changes for: - phone location - visual clutter - open materials - noise control - interruption cues - lighting - comfort - workspace boundaries D. Setup and reset routines Create: - morning workspace setup - pre-focus reset - post-focus cleanup - end-of-day reset - weekly workspace maintenance E. Low-budget improvement plan Create: - zero-cost fixes - under $25 fixes - under $100 fixes - optional upgrades Rules: - Do not require an expensive setup. - Do not optimize aesthetics over focus. - Do not ignore comfort. - The workspace should reduce friction before the work begins. --------------------------------------------------------------------------------

#089Attention Recovery System

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who lose focus and struggle to return, especially during long workdays, meetings, creative work, studying, or high-pressure periods.

Recover focus after distraction, interruption, low energy, emotional stress, task switching, or mental fog.

You are an attention recovery coach. Build a system that helps me recover quickly when focus breaks. My recovery context: What breaks my focus: [FOCUS BREAKERS] How I usually react: [REACTION] Work I need to return to: [WORK] Energy level: [ENERGY] Environment: [ENVIRONMENT] Available recovery time: [TIME] Emotional state: [STATE] Current distractions: [DISTRACTIONS] Urgency level: [URGENCY] Build the recovery system: 1. Break diagnosis Classify the focus break: - external interruption - digital distraction - emotional trigger - fatigue - boredom - confusion - hard decision - task too large - context switching - physical discomfort 2. Recovery menu Create recovery protocols for: - 30-second reset - 2-minute reset - 5-minute reset - 15-minute reset - full session restart Each protocol should include: - physical action - digital action - mental action - next task action - stop condition 3. Re-entry map Help me return to the task by identifying: - last completed step - current next action - first visible action - material to open - what to ignore - what counts as progress 4. Low-focus alternatives If deep focus is not possible, recommend: - useful lower-energy work - setup task - admin task - cleanup task - communication task - recovery task 5. Prevention insight After recovery, ask: - what caused the break? - what barrier was missing? - what should change before next session? Rules: - Do not treat one distraction as failure. - Do not let recovery become procrastination. - Do not force deep work if the recovery state is too weak. - The system should help me return faster and with less self-criticism. --------------------------------------------------------------------------------

#090Deep Work Capacity Builder

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who cannot focus for long, want to rebuild concentration, or need a training plan for high-quality deep work.

Gradually increase your ability to do focused work through progressive focus blocks, recovery, measurement, environment design, and sustainable practice.

Act as a deep work capacity coach. Create a progressive training plan that helps me build focus capacity without burnout. Current focus capacity: Current average focus block: [CURRENT BLOCK] Desired focus block: [DESIRED BLOCK] Type of work: [WORK TYPE] Energy pattern: [ENERGY] Schedule constraints: [CONSTRAINTS] Common distractions: [DISTRACTIONS] Current environment: [ENVIRONMENT] Motivation level: [MOTIVATION] Deadline pressure: [DEADLINES] Recovery habits: [RECOVERY] Build the capacity plan: A. Baseline assessment Estimate: - current sustainable focus length - ideal starting block - maximum safe block - recovery need - distraction risk - best training time - worst training time B. Progressive plan Create a 4-week plan: Week 1: stabilize focus Week 2: extend focus Week 3: increase quality Week 4: build consistency For each week include: - block length - number of sessions - task type - focus rule - recovery rule - measurement - adjustment trigger C. Focus training drills Create drills for: - single-tasking - urge surfing - tab discipline - thought capture - re-entry - boredom tolerance - session shutdown D. Measurement system Track: - planned blocks - completed blocks - minutes focused - distractions - recovery time - output quality - energy after session E. Failure adjustment Create rules for: - missed sessions - low-energy days - repeated distraction - overtraining - deadline pressure Rules: - Do not jump immediately to long focus blocks. - Do not measure only time; include output quality. - Do not ignore recovery. - Focus capacity should be trained progressively. --------------------------------------------------------------------------------

#091Single-Tasking Discipline System

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who multitask, keep many tabs open, jump between tasks, or start more than they complete.

Build a system that helps you work on one task at a time, finish more often, and reduce multitasking caused by open loops, urgency, and distraction.

You are a single-tasking discipline coach. Help me create a system that makes one-task-at-a-time execution easier. Current multitasking pattern: Tasks I switch between: [TASKS] Why I switch: [WHY] Open tabs / apps: [TABS / APPS] Active projects: [PROJECTS] Urgent requests: [URGENT REQUESTS] Internal distractions: [INTERNAL DISTRACTIONS] Current work environment: [ENVIRONMENT] Completion problem: [COMPLETION PROBLEM] Build the system: 1. Multitasking trigger map Identify triggers: - boredom - difficulty - uncertainty - urgency - notification - emotional discomfort - open loops - too many active tasks - unclear finish line - fear of forgetting 2. One-task rule design Create rules for: - choosing the task - defining done - closing unrelated tabs - capturing new thoughts - handling urgent input - pausing instead of switching - finishing or intentionally stopping 3. Task parking lot Design a parking lot for: - new ideas - unrelated tasks - questions - worries - follow-ups - later research - distractions 4. Completion loop For each task create: - start action - active work period - finish condition - handoff note - next action - cleanup 5. Practice plan Create a 10-day single-tasking practice plan. Rules: - Do not rely on memory for new ideas. - Do not force single-tasking when a true emergency appears. - Do not leave tasks half-open without a pause note. - The system should make finishing more attractive than switching. --------------------------------------------------------------------------------

#092Focus Block Menu Builder

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who need flexible focus options instead of one fixed deep work routine.

Create a library of focus block formats for different task types, energy levels, deadlines, and available time windows.

Act as a focus block menu designer. Build a menu of focus block formats I can choose from based on energy, time, and task type. My focus needs: Types of work: [WORK TYPES] Common time windows: [TIME WINDOWS] Energy patterns: [ENERGY] Deadlines: [DEADLINES] Distractions: [DISTRACTIONS] Environment options: [ENVIRONMENTS] Preferred break style: [BREAK STYLE] Tasks that need deep focus: [DEEP TASKS] Tasks that need medium focus: [MEDIUM TASKS] Create the menu: A. Block types Design focus blocks for: - 10-minute restart - 25-minute sprint - 45-minute focus block - 60-minute production block - 90-minute deep work block - 2-hour creation block - half-day immersion - low-energy focus block - deadline rescue block - review and polish block B. For each block include: - best use case - energy requirement - setup ritual - rules - timer structure - break structure - expected output - stop condition - recovery action C. Task matching Match my task types to the right block. D. Weekly placement Recommend where each block belongs in my week. E. Selection rules Create a decision tree: - if I have 15 minutes - if I have low energy - if I have high energy - if deadline is close - if task feels unclear - if I am distracted - if I need creative thinking Rules: - Do not use the same block for every task. - Do not schedule long blocks when energy is low. - Do not make short blocks feel meaningless. - The menu should help me choose focus instead of avoiding work. --------------------------------------------------------------------------------

#093Distraction-Resistant Task Design

FOCUS, DEEP WORK & DISTRACTION CONTROLHard tasks, ambiguous tasks, creative work, analytical work, procrastinated work, and deep work planning.

Rewrite tasks so they are easier to start, harder to avoid, clearer to finish, and less vulnerable to distraction.

You are a distraction-resistant task designer. Rewrite my tasks so they create less friction and more focus. Tasks: [PASTE TASKS] Context: Main goal: [GOAL] Available time: [TIME] Energy level: [ENERGY] Known distractions: [DISTRACTIONS] Reason I avoid these tasks: [AVOIDANCE REASON] Deadlines: [DEADLINES] Quality standard: [STANDARD] Tools needed: [TOOLS] Redesign the tasks: 1. Friction audit For each task identify: - why it is hard to start - why it is easy to abandon - what is unclear - what is too large - what emotional resistance exists - what distraction is likely 2. Task rewrite Rewrite each task into: - focus-friendly title - clear outcome - first action - time box - done definition - materials needed - distraction barrier - stop point 3. Focus sequencing Order tasks by: - energy match - deadline - cognitive load - dependency - emotional resistance - importance 4. Micro-commitment design For each difficult task create: - 2-minute start - 10-minute version - 30-minute version - full version - recovery action if distracted 5. Execution list Create a final focus-ready task list. Rules: - Do not use vague verbs. - Do not design tasks that require rethinking before starting. - Do not ignore emotional resistance. - A good task should make the first action obvious. --------------------------------------------------------------------------------

#094Focus Boundary Communication Kit

FOCUS, DEEP WORK & DISTRACTION CONTROLRemote workers, managers, founders, freelancers, teams, shared households, offices, and anyone who needs to reduce interruptions without seeming unavailable.

Create communication rules and scripts that protect focus time while keeping trust with teams, clients, colleagues, family, or collaborators.

Act as a focus boundary communication strategist. Help me explain and protect focus time with clear, respectful communication. My situation: People who interrupt or request time: [PEOPLE] Relationship to them: [RELATIONSHIPS] Type of requests: [REQUESTS] Focus time I need: [FOCUS TIME] Communication expectations: [EXPECTATIONS] Response time needs: [RESPONSE TIME] Real emergencies: [EMERGENCIES] Where boundaries feel hard: [HARD PART] Preferred tone: [TONE] Create the communication kit: A. Boundary policy Define: - focus hours - response windows - emergency exceptions - preferred communication channels - meeting request rules - when I am available - when I am unavailable B. Stakeholder-specific guidance For each group create: - what they need to know - how to communicate it - what boundary to set - what reassurance to give - what exception to allow C. Scripts Write scripts for: - announcing focus hours - declining interruption - asking to wait - redirecting to async - handling urgent request - setting meeting boundaries - protecting deep work block - explaining delayed response - renegotiating expectations D. Visual or status signals Recommend: - calendar labels - status messages - auto-responses - door signs - shared availability notes - team agreements E. Trust protection Create rules to ensure: - people still know when they can reach me - urgent issues have a path - promises are kept - boundaries do not become avoidance Rules: - Do not make boundaries sound hostile. - Do not disappear without communication. - Do not block true emergencies. - Focus protection should increase trust, not reduce it. --------------------------------------------------------------------------------

#095Meeting-to-Deep-Work Recovery Planner

FOCUS, DEEP WORK & DISTRACTION CONTROLMeeting-heavy schedules, managers, remote workers, consultants, founders, client work, and anyone who struggles to return to individual work after calls.

Create routines for recovering concentration after meetings, calls, interruptions, or collaborative work so the rest of the day is not lost.

You are a meeting-to-deep-work recovery planner. Help me transition from meetings back into focused execution. Meeting context: Meetings today: [MEETINGS] Deep work needed after meetings: [DEEP WORK] Energy after meetings: [ENERGY] Common post-meeting distractions: [DISTRACTIONS] Notes or follow-ups created: [FOLLOW-UPS] Available time after meetings: [TIME] Communication expectations: [EXPECTATIONS] Current transition problem: [PROBLEM] Design the recovery system: 1. Meeting exit protocol At the end of each meeting, define: - decisions made - next actions - owners - follow-ups - notes to capture - messages to send - open loops 2. Transition buffer Create a 5-minute, 10-minute, and 20-minute transition buffer. Each should include: - note capture - physical reset - digital reset - next task selection - focus setup 3. Re-entry plan For the deep work task after the meeting, define: - exact starting point - materials to open - tabs to close - first 10-minute action - done target - interruption rule 4. Schedule design Recommend how to place: - meetings - buffers - admin follow-up - deep work - communication windows - recovery 5. Anti-spiral rules Create rules to prevent: - checking messages for too long - opening unrelated tabs - letting meeting follow-ups consume the day - abandoning deep work because energy is lower Rules: - Do not schedule deep work immediately after intense meetings without transition. - Do not leave meeting follow-ups in memory. - Do not let one meeting split the whole day into fragments. - The system should make re-entry predictable. --------------------------------------------------------------------------------

#096Focus Sprint Coach

FOCUS, DEEP WORK & DISTRACTION CONTROLProcrastinated tasks, low-motivation days, quick progress, writing sprints, admin sprints, study sessions, and restarting work.

Run a short, structured focus sprint for one task with preparation, time box, rules, execution prompts, and a quick review.

Act as my focus sprint coach. Guide me through a focused sprint for the task below. Sprint task: [TASK] Context: Available time: [TIME] Energy level: [ENERGY] Why this matters: [WHY] What done means: [DONE] Likely distraction: [DISTRACTION] What I need open: [TOOLS / MATERIALS] What I should close: [CLOSE] Reward or recovery after: [RECOVERY] Build the sprint: 1. Sprint target Define: - sprint outcome - minimum win - stretch win - first action - stop point 2. Setup checklist Create a checklist: - close - open - silence - prepare - timer - write target - start 3. Sprint rules Create rules for: - no switching - capture distractions - handle stuck moments - handle urge to quit - handle incoming message - finish the block 4. Live coaching prompts Write prompts I can read at: - minute 0 - minute 5 - halfway point - when distracted - final 5 minutes - end of sprint 5. Sprint review After the sprint, ask: - what did I complete? - what remains? - what distracted me? - what is the next action? - should I continue, stop, or schedule? Rules: - Do not make the sprint too ambitious. - Do not allow setup to become procrastination. - Do not judge the sprint only by perfect completion. - The goal is focused progress inside the time box. --------------------------------------------------------------------------------

#097Urge Surfing for Digital Distractions

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who compulsively check apps, struggle with phone use, or break concentration through small digital impulses.

Build a practical method for handling the urge to check phone, email, social media, news, tabs, or messages during focus work.

You are a digital distraction behavior coach. Help me handle the urge to check distracting apps without turning it into a battle of willpower. Distraction pattern: Apps or sites I check: [APPS / SITES] When I check them: [WHEN] What triggers the urge: [TRIGGERS] What I feel before checking: [FEELING] What I get from checking: [REWARD] Focus work interrupted: [FOCUS WORK] Current blockers or limits: [CURRENT LIMITS] How often it happens: [FREQUENCY] Build the urge system: A. Trigger analysis Identify trigger types: - boredom - uncertainty - difficulty - fatigue - anxiety - reward seeking - social checking - avoidance - habit loop - transition moment B. Urge surfing protocol Create a step-by-step protocol: - notice the urge - name it - breathe - delay for 90 seconds - write the urge down - return to first action - check later during allowed window C. Replacement actions Create replacements for: - phone reach - email check - social media check - browser wandering - news checking - random research - unnecessary tool switching D. Environment rules Create rules for: - phone location - blocker settings - allowed check windows - app removal - browser setup - accountability - focus mode E. 14-day experiment Create: - daily tracking - check window rules - success metric - relapse response - reward system - adjustment plan Rules: - Do not shame the urge. - Do not rely only on app blockers. - Do not remove communication needed for real work. - The system should interrupt the habit loop before the app opens. --------------------------------------------------------------------------------

#098Creative Flow Protection System

FOCUS, DEEP WORK & DISTRACTION CONTROLWriters, designers, artists, creators, strategists, musicians, founders, and anyone doing creative work that needs flow.

Protect creative focus from over-structuring, interruptions, perfectionism, premature editing, and digital noise.

Act as a creative flow protector. Design a work system that helps me enter creative flow and stay there long enough to produce meaningful output. Creative work: [CREATIVE WORK] Context: Creative goal: [GOAL] Available time: [TIME] Best creative conditions: [CONDITIONS] Current blockers: [BLOCKERS] Perfectionism patterns: [PERFECTIONISM] Editing habits: [EDITING HABITS] Distractions: [DISTRACTIONS] Tools needed: [TOOLS] Output target: [OUTPUT] Mood or energy: [MOOD / ENERGY] Protect the flow: 1. Flow conditions Identify what the session needs: - spaciousness - constraint - silence or sound - reference material - warm-up - emotional safety - no premature judgment - enough time - clear output target 2. Creative session structure Design: - entry ritual - warm-up exercise - creation block - no-editing rule - exploration zone - capture system - rough output target - closing note 3. Anti-perfectionism rules Create rules for: - first draft quality - when editing is allowed - how to handle bad ideas - how to keep moving - what counts as progress - when to stop refining 4. Distraction control Design barriers against: - research rabbit holes - tool tinkering - social checking - overplanning - comparison - premature feedback - switching projects 5. Flow review After the session, evaluate: - output created - energy after - flow blockers - useful conditions - next creative move Rules: - Do not over-systematize creative work. - Do not treat rough output as failure. - Do not allow editing to destroy creation. - The system should protect creative momentum and originality. --------------------------------------------------------------------------------

#099Focus Experiment Designer

FOCUS, DEEP WORK & DISTRACTION CONTROLPeople who have tried productivity advice but need evidence from their own behavior.

Run structured experiments to discover what actually improves focus for your schedule, environment, energy, tools, and task types.

You are a focus experiment designer. Help me test focus improvements systematically instead of guessing what works. Current focus problem: [FOCUS PROBLEM] Context: Type of work: [WORK TYPE] Current schedule: [SCHEDULE] Current environment: [ENVIRONMENT] Distractions: [DISTRACTIONS] Energy pattern: [ENERGY] Tools: [TOOLS] What I have already tried: [TRIED] Time available for experiment: [TIMEFRAME] Metric I care about: [METRIC] Design the experiment: A. Hypothesis creation Create 5 possible hypotheses, such as: - notifications are the main issue - task clarity is the main issue - energy timing is the main issue - environment is the main issue - block length is the main issue - open tabs are the main issue - meetings are fragmenting focus B. Experiment selection Choose the best 3 experiments. For each include: - hypothesis - change to test - duration - metric - baseline - success criteria - risk - how to keep it simple C. Daily tracking sheet Create a simple tracker with: - focus block planned - focus block completed - minutes focused - distractions - output produced - energy before - energy after - notes D. Review method At the end of the experiment, analyze: - what improved - what worsened - what was neutral - what was hard to maintain - what should become a rule - what should be discarded E. Next iteration Recommend the next experiment based on results. Rules: - Do not test too many changes at once. - Do not rely only on feelings. - Do not use complicated tracking. - The experiment should produce actionable learning. --------------------------------------------------------------------------------

#100Full Focus, Deep Work and Distraction Control Audit

FOCUS, DEEP WORK & DISTRACTION CONTROLFull productivity resets, distracted professionals, creators, founders, students, writers, developers, analysts, teams, and anyone who needs higher-quality concentrated work.

Audit and redesign your complete focus system across attention leaks, deep work blocks, distractions, environment, rituals, interruptions, recovery, and concentration capacity.

Act as an independent focus and deep work systems auditor. Review my current attention system and redesign it so I can protect focus, reduce distractions, handle interruptions, and produce higher-quality work. Full context: Work that requires deep focus: [DEEP WORK] Current schedule: [SCHEDULE] Current calendar: [CALENDAR] Current task list: [TASKS] Energy pattern: [ENERGY] Work environment: [ENVIRONMENT] Digital tools: [TOOLS] Notification sources: [NOTIFICATIONS] Biggest distractions: [DISTRACTIONS] Meetings and interruptions: [INTERRUPTIONS] Communication expectations: [COMMUNICATION] Current focus rituals: [RITUALS] Current deep work capacity: [CAPACITY] Where focus breaks most often: [BREAK POINTS] What I have tried before: [TRIED] What good focus would look like: [DESIRED STATE] Audit across 30 dimensions: 1. Attention leak visibility 2. Digital distraction control 3. Phone boundaries 4. Notification architecture 5. Browser and tab discipline 6. Physical workspace 7. Noise and environment 8. Deep work scheduling 9. Energy alignment 10. Task clarity before focus 11. Start rituals 12. Shutdown rituals 13. Focus block structure 14. Break design 15. Context switching 16. Meeting fragmentation 17. Communication boundaries 18. Interruption handling 19. Re-entry after interruption 20. Emotional distraction 21. Boredom tolerance 22. Urge management 23. Open loop capture 24. Single-tasking discipline 25. Creative flow protection 26. Attention recovery 27. Deep work capacity 28. Focus measurement 29. Experimentation system 30. Sustainability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason my focus system is currently failing. B. Focus system redesign Create: - deep work schedule - focus block templates - distraction barrier system - notification rules - phone rules - browser rules - workspace setup - start ritual - interruption protocol - re-entry protocol - attention recovery protocol - communication boundary system - deep work capacity plan C. Environment design Recommend changes for: - digital workspace - physical workspace - calendar - task system - communication channels - recovery periods D. Implementation plan Create: - first 24-hour focus reset - first 7-day distraction reduction plan - first 30-day deep work capacity plan - weekly focus review - metrics to track - what to stop doing immediately - what to protect first E. Executive summary Write a direct summary with: - biggest focus leak - most valuable deep work block to protect - easiest distraction to remove - hardest distraction to manage - first rule to implement today - next focus session plan - fallback rule for chaotic days Rules: - Do not give generic focus advice. - Do not recommend a system that ignores real communication needs. - Do not assume perfect discipline. - Use [LOW CONFIDENCE] where information is missing. - The final system should protect attention through environment, rules, rituals, and realistic recovery. -------------------------------------------------------------------------------- ENERGY, BURNOUT & SUSTAINABLE PERFORMANCE

#101Personal Energy Pattern Mapper

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who feel productive at some times and useless at others, struggle with inconsistent energy, or want a schedule that matches their actual rhythm.

Identify when your mental energy naturally rises, drops, crashes, or recovers so you can plan work around real capacity instead of forcing the same intensity all day.

You are a personal energy pattern analyst. Help me map my mental and physical energy patterns so I can plan work in a more sustainable way. My context: Typical weekday schedule: [SCHEDULE] Typical weekend schedule: [SCHEDULE] Work responsibilities: [RESPONSIBILITIES] Personal responsibilities: [PERSONAL RESPONSIBILITIES] Sleep pattern: [SLEEP] Energy highs: [ENERGY HIGHS] Energy lows: [ENERGY LOWS] Most draining tasks: [DRAINING TASKS] Most energizing tasks: [ENERGIZING TASKS] Current productivity problem: [PROBLEM] Health or lifestyle constraints: [CONSTRAINTS] Current workload: [WORKLOAD] Map my energy: 1. Daily energy curve Create a likely daily energy map across: - early morning - mid-morning - late morning - early afternoon - mid-afternoon - evening - late evening For each period identify: - expected energy level - best task type - worst task type - decision quality - focus capacity - recovery need - warning signs 2. Weekly energy pattern Analyze how energy likely changes across: - Monday - Tuesday - Wednesday - Thursday - Friday - Saturday - Sunday For each day recommend: - best work type - work to avoid - recovery need - planning note 3. Energy-task matching Match these task types to my best energy windows: - deep work - meetings - admin - creative work - strategic thinking - communication - learning - errands - decision-making - routine maintenance 4. Energy leak diagnosis Identify what may be draining energy: - sleep mismatch - too many decisions - context switching - emotional stress - unplanned work - meetings - poor breaks - unclear priorities - overcommitment - recovery debt 5. Sustainable schedule recommendations Create: - ideal energy-based day - ideal energy-based week - high-energy task list - medium-energy task list - low-energy task list - recovery blocks - first 7-day experiment Rules: - Do not assume I have the same energy every day. - Do not schedule difficult decisions during known low-energy windows. - Do not treat low energy as laziness. - The output should help me plan with my energy, not against it. --------------------------------------------------------------------------------

#102Burnout Early Warning Audit

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who feel tired, cynical, overworked, emotionally flat, easily irritated, or worried they are pushing too hard for too long.

Detect early burnout signals before performance collapses by analyzing energy, motivation, sleep, irritability, avoidance, workload, recovery, and emotional patterns.

Act as a burnout early warning auditor. Help me evaluate whether my current work pattern is sustainable and identify signs that need attention. My current state: Workload: [WORKLOAD] Hours worked recently: [HOURS] Sleep quality: [SLEEP] Energy level: [ENERGY] Motivation level: [MOTIVATION] Mood: [MOOD] Stress level: [STRESS] Recovery habits: [RECOVERY] Physical signs: [PHYSICAL SIGNS] Emotional signs: [EMOTIONAL SIGNS] Tasks I avoid: [AVOIDED TASKS] Work I used to enjoy but now dislike: [WORK CHANGES] Main pressures: [PRESSURES] Support available: [SUPPORT] Run the audit: A. Signal scan Evaluate my current signs across: - exhaustion - emotional numbness - irritability - procrastination - sleep disruption - reduced focus - loss of motivation - cynicism - overreacting to small issues - inability to recover after rest - constant urgency - social withdrawal - physical tension - decision fatigue - reduced quality of work For each signal provide: - severity from 1 to 10 - likely cause - risk if ignored - immediate action B. Burnout risk level Classify the risk as: - low - moderate - high - severe Explain why. C. Root cause analysis Identify the most likely causes: - too much volume - too little recovery - emotional labor - unclear boundaries - lack of control - values mismatch - chronic urgency - poor sleep - overcommitment - perfectionism - lack of support D. Stabilization plan Create: - next 24-hour relief plan - next 7-day reduction plan - next 30-day sustainability plan - conversations I may need - work to pause or reduce - recovery to protect E. Escalation note Tell me what signs would indicate I should seek professional or medical support. Rules: - Do not diagnose a medical condition. - Do not minimize serious warning signs. - Do not recommend simply working harder. - Focus on practical workload, recovery, and boundary changes. --------------------------------------------------------------------------------

#103Sustainable Performance Operating System

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEAmbitious people who want high performance without relying on exhaustion, crisis mode, or constant self-pressure.

Build a personal operating system that supports consistent output through energy planning, recovery, boundaries, workload limits, and review rituals.

You are a sustainable performance systems designer. Build a personal operating system that helps me perform consistently without burning out. My context: Main goals: [GOALS] Current workload: [WORKLOAD] Work type: [WORK TYPE] Available hours: [HOURS] Energy pattern: [ENERGY PATTERN] Current recovery habits: [RECOVERY] Main stressors: [STRESSORS] Current boundaries: [BOUNDARIES] Non-negotiables: [NON-NEGOTIABLES] Ambition level: [AMBITION] Burnout risks: [RISKS] What sustainable success means to me: [SUSTAINABLE SUCCESS] Build the operating system: 1. Performance philosophy Create 5 principles for how I should work. Each principle should include: - what it protects - what it prevents - how it changes daily behavior - what I should stop doing 2. Capacity rules Define rules for: - maximum work hours - maximum meetings - maximum active projects - maximum high-intensity days in a row - minimum recovery blocks - minimum sleep protection - minimum buffer time 3. Energy-based work model Create categories: - peak energy work - steady energy work - low energy work - recovery work - no-work recovery For each include examples and scheduling rules. 4. Weekly operating rhythm Create: - weekly planning ritual - energy forecast ritual - workload review - recovery planning - boundary review - Friday shutdown - weekend recovery rule 5. Sustainability dashboard Create a dashboard with: - output metric - energy metric - stress metric - recovery metric - workload metric - warning signal - corrective action Rules: - Do not design a system that only works during perfect weeks. - Do not optimize output while ignoring recovery. - Do not rely on motivation as the main fuel. - The system should protect both ambition and long-term capacity. --------------------------------------------------------------------------------

#104Task-Energy Matching Matrix

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEDaily planning, weekly planning, low-energy days, heavy workloads, creative work, analytical work, and people who waste peak energy on shallow tasks.

Match tasks to the right energy level so high-focus work gets peak attention and low-energy periods still become useful without causing exhaustion.

Act as an energy-based task planner. Sort my work by energy requirement and build a plan that uses my capacity intelligently. Task list: [PASTE TASKS] Context: Current energy level: [ENERGY 1-10] Energy pattern by time of day: [ENERGY PATTERN] Available time: [TIME] Deadlines: [DEADLINES] Main priorities: [PRIORITIES] Tasks I avoid: [AVOIDED TASKS] Tasks that drain me: [DRAINING TASKS] Tasks that energize me: [ENERGIZING TASKS] Recovery needs: [RECOVERY NEEDS] Build the matrix: A. Energy scoring For each task score: - mental energy required - emotional energy required - physical energy required - decision load - social load - focus requirement - recovery cost - urgency - importance B. Energy categories Sort tasks into: - peak-energy tasks - steady-energy tasks - low-energy tasks - recovery-compatible tasks - emotionally expensive tasks - decision-heavy tasks - social-energy tasks - tasks to avoid when tired C. Scheduling logic Assign each task to: - morning peak - midday steady block - afternoon admin - evening low-energy window - meeting / social window - recovery day - defer - delegate - delete D. Energy protection Identify: - tasks that should not be done today - tasks that should be shortened - tasks that need preparation - tasks that need recovery after - tasks that should be paired with breaks E. Final plan Create: - high-energy plan - normal-energy plan - low-energy plan - emergency minimum plan - task list for future low-energy moments Rules: - Do not schedule hard work only by deadline if energy makes failure likely. - Do not waste peak energy on trivial admin. - Do not treat low-energy time as useless. - The plan should help me complete work with less internal resistance. --------------------------------------------------------------------------------

#105Recovery Routine Architect

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who rest randomly, feel tired after weekends, work too intensely, or need a recovery system that actually fits their life.

Design daily, weekly, and monthly recovery routines that restore mental energy, reduce stress accumulation, and support sustainable productivity.

You are a recovery routine architect. Help me design realistic recovery routines that restore energy instead of simply filling time. My recovery context: Current workload: [WORKLOAD] Main stressors: [STRESSORS] Current recovery habits: [CURRENT RECOVERY] Sleep schedule: [SLEEP] Exercise or movement: [MOVEMENT] Social energy: [SOCIAL ENERGY] Personal obligations: [OBLIGATIONS] Available recovery time: [TIME] What drains me: [DRAINS] What restores me: [RESTORES] What I have tried: [TRIED] Constraints: [CONSTRAINTS] Design recovery: 1. Recovery needs diagnosis Identify which recovery types I need most: - sleep recovery - physical recovery - mental quiet - emotional processing - social connection - solitude - play - nature - movement - creative recovery - digital rest - unstructured time Explain why. 2. Recovery menu Create recovery options by time available: - 2 minutes - 5 minutes - 15 minutes - 30 minutes - 60 minutes - half day - full day For each option include: - recovery type - when to use it - what to avoid - expected benefit 3. Daily routine Create: - morning energy setup - mid-day reset - post-work transition - evening shutdown - sleep preparation 4. Weekly routine Create: - recovery blocks - social balance - low-stimulation time - planning time - reset time - no-output time 5. Monthly reset Create a monthly recovery review: - stress accumulation check - energy pattern review - workload adjustment - boundary update - recovery upgrade Rules: - Do not make recovery feel like another performance task. - Do not rely only on passive scrolling as rest. - Do not ignore my real constraints. - Recovery should be practical, repeatable, and restorative. --------------------------------------------------------------------------------

#106Overwork Pattern Detector

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who repeatedly overcommit, work late, skip breaks, ignore capacity, or feel guilty when not working.

Identify recurring overwork patterns, hidden drivers, emotional triggers, boundary failures, and unrealistic planning habits that lead to exhaustion.

Act as an overwork pattern detective. Help me understand why I keep working beyond sustainable limits and how to interrupt the pattern. Overwork context: Recent overwork examples: [EXAMPLES] Typical work hours: [HOURS] Tasks or projects involved: [TASKS / PROJECTS] People or pressures involved: [PEOPLE / PRESSURES] Emotions before overworking: [EMOTIONS BEFORE] Emotions after overworking: [EMOTIONS AFTER] What I was trying to avoid: [AVOIDANCE] What I was trying to prove: [PROVE] Current boundaries: [BOUNDARIES] Consequences of overwork: [CONSEQUENCES] Investigate the pattern: 1. Pattern timeline For each overwork example, map: - trigger - decision point - self-talk - task chosen - boundary crossed - short-term reward - long-term cost - missed warning sign 2. Driver analysis Identify possible drivers: - perfectionism - fear of disappointing others - unclear priorities - unrealistic estimation - urgency addiction - poor delegation - lack of boundaries - avoidance of rest - identity tied to output - financial pressure - role expectations 3. Boundary failure map Find where I fail to stop: - start of day - end of workday - deadline pressure - after messages - before sleep - after criticism - when someone asks - when a task is almost done 4. Intervention points Create interventions for: - before accepting work - before starting work - mid-day - late afternoon - evening - after a stressful message - before extending the day 5. New operating rules Create: - work stop rule - scope rule - deadline renegotiation rule - enough-for-today rule - recovery after overwork rule - weekly capacity rule Rules: - Do not shame ambition. - Do not treat overwork as a moral failure. - Do not ignore external pressure. - The goal is to preserve performance without self-destruction. --------------------------------------------------------------------------------

#107Ambition-Sustainability Balancer

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEFounders, creators, leaders, students, high performers, career builders, and anyone with large goals but limited capacity.

Balance big goals with realistic energy, recovery, time, relationships, and long-term health so ambition becomes executable instead of exhausting.

You are an ambition and sustainability strategist. Help me pursue an important goal without building a plan that depends on exhaustion. Ambitious goal: [GOAL] Context: Why this goal matters: [WHY] Deadline or time horizon: [TIME HORIZON] Current workload: [WORKLOAD] Available time: [TIME] Current energy: [ENERGY] Recovery needs: [RECOVERY] Relationships or life areas to protect: [PROTECT] Risks: [RISKS] What I am willing to sacrifice: [WILL SACRIFICE] What I am not willing to sacrifice: [WILL NOT SACRIFICE] Balance the goal: A. Ambition profile Define: - desired outcome - minimum viable success - stretch success - why now - what this goal requires - what this goal must not destroy B. Sustainability constraints List constraints across: - time - energy - sleep - health - relationships - money - emotional load - focus - recovery C. Tradeoff design Choose intentional tradeoffs: - what to reduce - what to pause - what to stop - what to delegate - what to simplify - what to protect D. Sustainable execution path Create: - weekly effort limit - milestone plan - recovery blocks - low-energy version - high-energy version - fallback plan - review cadence E. Decision rules Create rules for: - when to push - when to pause - when to cut scope - when to ask for help - when to extend timeline - when to stop Rules: - Do not make the goal smaller automatically. - Do not romanticize burnout. - Do not ignore the cost of success. - The plan should make ambition more durable. --------------------------------------------------------------------------------

#108Low-Battery Day Planner

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCETired days, recovery days, high-stress periods, burnout prevention, disrupted sleep, heavy emotional load, and sustainable execution.

Create a useful plan for days when energy is low, focus is weak, motivation is gone, or the original plan is no longer realistic.

Act as a low-battery day planner. Help me get through today responsibly without pretending I have full capacity. Today’s state: Energy level: [ENERGY 1-10] Focus level: [FOCUS 1-10] Mood: [MOOD] Sleep quality: [SLEEP] Available time: [TIME] Tasks planned: [TASKS] Deadlines: [DEADLINES] People waiting on me: [PEOPLE] Non-negotiables: [NON-NEGOTIABLES] What feels impossible today: [IMPOSSIBLE] What would still count as a good day: [GOOD DAY] Design the day: 1. Capacity reality check Classify today as: - full capacity - reduced capacity - minimum viable capacity - recovery-first day - emergency-only day Explain the classification. 2. Task triage Sort tasks into: - must do today - minimum viable version - communicate today - reschedule - delegate - delete - low-energy friendly - avoid today 3. Minimum viable day Create a plan with: - one essential task - one maintenance task - one communication task - one recovery action - one setup action for tomorrow 4. Energy-safe schedule Build a schedule with: - gentle start - short work blocks - breaks - recovery blocks - shutdown - no-guilt stopping point 5. Recovery and tomorrow reset Create: - evening recovery routine - tomorrow’s first easy start - message templates for delays - rule to prevent low energy from becoming a lost week Rules: - Do not shame low energy. - Do not recommend intense work if capacity is low. - Do not ignore real deadlines. - The goal is responsible progress plus recovery. --------------------------------------------------------------------------------

#109Mental Load Decompression Protocol

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who feel mentally crowded, overwhelmed, unable to relax, or stuck thinking about too many unfinished things.

Reduce mental overload by capturing open loops, separating responsibilities, clarifying decisions, closing loose ends, and creating relief.

You are a mental load decompression guide. Help me empty, sort, and reduce the open loops that are draining my energy. Mental load dump: [PASTE EVERYTHING ON YOUR MIND] Context: Current responsibilities: [RESPONSIBILITIES] Current projects: [PROJECTS] People depending on me: [PEOPLE] Deadlines: [DEADLINES] Personal obligations: [PERSONAL] Decisions pending: [DECISIONS] Worries: [WORRIES] Energy level: [ENERGY] What feels heaviest: [HEAVIEST] Decompress the mental load: PHASE 1 — Capture Sort everything into: - tasks - projects - decisions - worries - reminders - emotions - commitments - waiting-for items - personal needs - things outside my control PHASE 2 — Clarify For each item identify: - what it really is - whether action is needed - owner - deadline - next step - whether it can be parked PHASE 3 — Reduce Recommend: - items to do - items to schedule - items to delegate - items to communicate - items to delete - items to accept - items to release - items to revisit later PHASE 4 — Close loops Create: - 5 quick closure actions - 5 messages to send - 5 decisions to make or schedule - 5 items to remove from active attention PHASE 5 — Relief plan Create: - next 30 minutes - next 24 hours - next 7 days - mental load prevention rule Rules: - Do not treat worries as tasks unless action is possible. - Do not leave open loops uncategorized. - Do not make the plan bigger than the relief it creates. - The output should make my mind feel less crowded. --------------------------------------------------------------------------------

#110Burnout Prevention Boundary Builder

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who overextend, have demanding roles, struggle to say no, or need boundaries that protect performance and relationships.

Create boundaries around time, workload, communication, meetings, availability, recovery, and emotional labor to prevent burnout before it escalates.

Act as a burnout prevention boundary strategist. Help me build boundaries that are clear, realistic, and respectful. My situation: Main role: [ROLE] Workload: [WORKLOAD] People making requests: [PEOPLE] Common requests: [REQUESTS] Current boundaries: [BOUNDARIES] Boundaries I need but avoid: [AVOIDED BOUNDARIES] Communication expectations: [EXPECTATIONS] Recovery needs: [RECOVERY] Risks if nothing changes: [RISKS] Tone needed: [TONE] Build boundaries: A. Boundary audit Identify where boundaries are needed across: - work hours - meetings - messaging - deadlines - scope - emotional support - urgent requests - recovery time - personal time - decision-making For each include: - current problem - boundary needed - risk if missing - likely resistance B. Boundary levels Create three versions: - soft boundary - clear boundary - firm boundary For each situation. C. Communication scripts Write scripts for: - declining extra work - renegotiating a deadline - protecting recovery time - responding outside work hours - limiting meetings - reducing scope - saying not now - asking for priority tradeoff D. Exception rules Define what can override boundaries and what cannot. E. Maintenance system Create: - weekly boundary review - warning signs - repair conversation script - rule for when boundaries are crossed Rules: - Do not make boundaries aggressive. - Do not make boundaries so vague they fail. - Do not ignore legitimate responsibilities. - Boundaries should protect energy while preserving trust. --------------------------------------------------------------------------------

#111Weekly Energy Budget Planner

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople whose calendar technically fits but still leaves them exhausted because energy costs were ignored.

Plan the week by budgeting energy, not just time, across deep work, meetings, admin, personal obligations, recovery, and high-stress tasks.

You are an energy budget planner. Help me plan my week by allocating mental, emotional, physical, and social energy. Week context: Tasks and projects: [TASKS / PROJECTS] Calendar commitments: [CALENDAR] Meetings: [MEETINGS] Deadlines: [DEADLINES] Personal obligations: [PERSONAL] Energy forecast: [ENERGY FORECAST] Sleep or recovery constraints: [CONSTRAINTS] Stressors: [STRESSORS] Available work hours: [HOURS] Non-negotiables: [NON-NEGOTIABLES] Create the energy budget: 1. Energy account balance Estimate my weekly capacity across: - mental energy - emotional energy - social energy - physical energy - decision energy - creative energy 2. Energy cost of commitments For each major item estimate: - time cost - energy cost - recovery cost - risk of overrun - best day/time - whether it should be paired with recovery 3. Weekly energy allocation Allocate energy to: - high-impact work - deadlines - meetings - admin - communication - personal obligations - recovery - buffer 4. Overdraft warning Identify where I may be overspending energy. Recommend: - reduce - move - split - delegate - cancel - recover before - recover after 5. Energy-aware weekly plan Create: - high-energy blocks - medium-energy blocks - low-energy blocks - recovery blocks - social energy limits - decision-light days - weekend recovery plan Rules: - Do not treat all hours as equal. - Do not stack high-energy commitments without recovery. - Do not ignore emotional and social load. - The week should be sustainable even if not perfect. --------------------------------------------------------------------------------

#112Cognitive Load Reducer

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who feel mentally tired from too many small decisions, too many tools, too many options, or too much operational clutter.

Reduce mental friction by simplifying decisions, systems, tools, task lists, routines, reminders, and recurring choices.

Act as a cognitive load reduction specialist. Help me simplify the parts of my life and work that consume mental energy unnecessarily. Cognitive load sources: [PASTE SOURCES OF MENTAL CLUTTER] Context: Current tools: [TOOLS] Task system: [TASK SYSTEM] Calendar system: [CALENDAR] Recurring decisions: [DECISIONS] Work responsibilities: [RESPONSIBILITIES] Personal responsibilities: [PERSONAL] Areas that feel complicated: [COMPLICATED AREAS] Energy level: [ENERGY] Where I lose time thinking: [LOSE TIME] Reduce the load: A. Load inventory Classify each source as: - decision load - memory load - task switching load - tool load - emotional load - communication load - planning load - clutter load - ambiguity load - maintenance load B. Simplification opportunities For each source identify: - why it drains energy - whether it can be removed - whether it can be automated - whether it can be templated - whether it can be batched - whether it can be delegated - whether it needs a rule C. Default rules Create defaults for: - what to work on first - when to check messages - how to choose meals / clothing / routines, if relevant - how to handle recurring tasks - how to respond to common requests - how to schedule meetings - how to decide what not to do D. System simplification Recommend changes to: - task list - calendar - notes - files - communication - routines - reminders - reviews E. 7-day load reduction plan Create one simplification action per day. Rules: - Do not add a complicated system to reduce complexity. - Do not automate unclear processes. - Do not remove needed responsibilities. - The goal is fewer decisions and cleaner execution. --------------------------------------------------------------------------------

#113Recovery Debt Payoff Plan

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPost-launch recovery, after deadline sprints, chronic exhaustion, long work stretches, and people who need to restore capacity without disappearing completely.

Identify accumulated recovery debt from overwork, stress, poor sleep, emotional overload, or intense deadlines and create a plan to repay it gradually.

You are a recovery debt planner. Help me estimate my accumulated recovery debt and create a practical repayment plan. Current state: Recent intense period: [DESCRIBE PERIOD] Workload during it: [WORKLOAD] Sleep quality: [SLEEP] Stress level: [STRESS] Physical signs: [PHYSICAL SIGNS] Mental signs: [MENTAL SIGNS] Emotional signs: [EMOTIONAL SIGNS] Current obligations: [OBLIGATIONS] Available recovery time: [TIME] What cannot pause: [NON-NEGOTIABLES] What can pause: [CAN PAUSE] Create the payoff plan: 1. Recovery debt estimate Assess debt across: - sleep - physical rest - mental rest - emotional processing - social balance - sensory overload - decision fatigue - unfinished stress loops Classify each as: - low - moderate - high - critical 2. Immediate stabilization Create a 24-hour plan: - reduce stimulation - protect sleep - lower workload - communicate delays - do only essentials - restore basics 3. 7-day repayment Create a 7-day plan with: - work reduction - sleep protection - low-stimulation blocks - movement - decompression - social balance - admin cleanup - decision reduction 4. 30-day capacity rebuild Create a plan to return to normal output gradually. Include: - workload ramp - recovery blocks - warning signs - review points - limits 5. Prevention rule Create rules for after future intense periods. Rules: - Do not recommend extreme rest that ignores real obligations. - Do not recommend immediately returning to full speed. - Do not treat recovery as laziness. - The plan should restore capacity in layers. --------------------------------------------------------------------------------

#114Stress Response Ladder

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEHigh-pressure work, emotional overload, deadline stress, leadership roles, caregiving, studying, and burnout prevention.

Create a clear ladder of responses for different stress levels so you know when to push, pause, reduce, ask for help, or fully recover.

Act as a stress response designer. Build a personal ladder that tells me what to do at different stress levels. My stress context: Common stress triggers: [TRIGGERS] Current stress level: [STRESS 1-10] Physical signs: [PHYSICAL SIGNS] Emotional signs: [EMOTIONAL SIGNS] Mental signs: [MENTAL SIGNS] Workload: [WORKLOAD] Support system: [SUPPORT] Current coping habits: [COPING] Bad coping patterns: [BAD PATTERNS] Responsibilities I cannot drop: [RESPONSIBILITIES] Build the ladder: Level 1-2: Normal pressure Define: - signs - useful actions - work intensity allowed - recovery needed Level 3-4: Rising stress Define: - warning signs - work adjustments - communication actions - recovery actions - what to avoid Level 5-6: High stress Define: - workload changes - decision limits - support actions - boundary actions - recovery minimums Level 7-8: Overload Define: - what to pause - who to inform - what not to decide - how to reduce demands - immediate recovery actions Level 9-10: Critical stress Define: - emergency simplification - who to contact - what to stop - professional support consideration - safety-first actions Then create: - daily stress check - response menu - communication scripts - recovery plan by level - rule for when to escalate Rules: - Do not give medical diagnosis. - Do not ignore severe stress signs. - Do not use productivity tactics for critical stress. - The ladder should make the next response obvious. --------------------------------------------------------------------------------

#115Sustainable Sprint Designer

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCELaunches, exams, client deadlines, creative pushes, business sprints, project crunches, and temporary high-intensity execution.

Plan an intense work sprint with realistic effort, recovery, scope control, warning signs, and decompression so high output does not become burnout.

You are a sustainable sprint planner. Help me design an intense but bounded work sprint that protects quality and recovery. Sprint context: Sprint goal: [GOAL] Sprint duration: [DURATION] Deadline: [DEADLINE] Current baseline: [BASELINE] Work required: [WORK REQUIRED] Available hours: [HOURS] Energy level: [ENERGY] Other obligations: [OBLIGATIONS] Quality standard: [QUALITY] Risks: [RISKS] Recovery after sprint: [RECOVERY OPTIONS] Design the sprint: A. Sprint boundaries Define: - start date - end date - scope - out-of-scope work - daily maximum effort - minimum sleep protection - recovery minimum - stop conditions B. Workload plan Break the sprint into: - preparation - production - review - polish - delivery - decompression For each phase include: - objective - work blocks - energy demand - recovery need - risk C. Daily sprint rhythm Create: - start ritual - focus blocks - admin window - meal / movement breaks - shutdown ritual - sleep protection - daily review D. Burnout guardrails Create warning signs and responses for: - reduced focus - irritability - poor sleep - avoidance - declining quality - emotional numbness - physical fatigue E. Post-sprint recovery Create: - first 24 hours after - first week after - backlog cleanup - lessons learned - next sprint rule Rules: - Do not make the sprint indefinite. - Do not remove recovery to fit more work. - Do not ignore non-sprint obligations. - A sustainable sprint must include an exit ramp. --------------------------------------------------------------------------------

#116Evening and Weekend Recovery Reset

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who work mentally after hours, doomscroll to recover, lose weekends to chores, or start Monday already tired.

Design recovery routines for evenings and weekends that help you disconnect, restore energy, process stress, and return to work with more capacity.

Act as an evening and weekend recovery designer. Help me create restorative routines that fit my life and reduce accumulated stress. My context: Work schedule: [WORK SCHEDULE] Evening habits: [EVENING HABITS] Weekend habits: [WEEKEND HABITS] Responsibilities outside work: [RESPONSIBILITIES] Digital habits: [DIGITAL HABITS] Sleep needs: [SLEEP] Social needs: [SOCIAL] Solitude needs: [SOLITUDE] Chores / admin: [CHORES] What usually ruins recovery: [RECOVERY BLOCKERS] What genuinely restores me: [RESTORES] Design the reset: 1. Evening transition Create a routine for: - work shutdown - open loop capture - digital boundary - physical transition - emotional decompression - next-day setup - sleep preparation 2. Weeknight recovery menu Create options for: - low-energy recovery - social recovery - creative recovery - physical recovery - quiet recovery - no-screen recovery - short reset 3. Weekend architecture Design a weekend with: - admin block - chore block - connection block - unstructured time - movement - rest - planning - no-output time 4. Recovery killers Identify what to reduce: - work checking - overplanning - excessive chores - doomscrolling - obligation overload - social overextension - guilt-driven productivity 5. Monday readiness Create a Sunday routine that prepares the week without stealing the weekend. Rules: - Do not turn recovery into a productivity project. - Do not remove all fun or spontaneity. - Do not ignore real life responsibilities. - The reset should help me return with more energy, not just a cleaner task list. --------------------------------------------------------------------------------

#117High-Intensity Work Cycle Planner

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who have seasonal workload peaks, launches, sales periods, exams, creative production cycles, or leadership crunches.

Alternate high-intensity work with recovery cycles so demanding periods become planned, bounded, and sustainable.

You are a high-intensity work cycle planner. Help me design a cycle of push, stabilize, recover, and rebuild. Work cycle context: High-intensity period: [PERIOD] Reason for intensity: [REASON] Expected workload: [WORKLOAD] Key deliverables: [DELIVERABLES] Normal responsibilities: [RESPONSIBILITIES] Available support: [SUPPORT] Recovery opportunities: [RECOVERY] Past cycle problems: [PAST PROBLEMS] Non-negotiables: [NON-NEGOTIABLES] Plan the cycle: PHASE 1 — Pre-load Before the intense period: - simplify commitments - prepare materials - reduce decisions - communicate boundaries - schedule recovery - define scope PHASE 2 — Push During the intense period: - work rhythm - maximum effort limit - minimum recovery - daily shutdown - quality checks - warning signs PHASE 3 — Stabilize Immediately after: - close loops - communicate status - clear urgent backlog - reduce new commitments - protect sleep PHASE 4 — Recover Recovery period: - workload reduction - mental rest - physical recovery - emotional decompression - social balance PHASE 5 — Rebuild Return to normal: - capacity ramp - lessons learned - system changes - next cycle guardrails Rules: - Do not plan high intensity as the normal baseline. - Do not skip the recovery phase. - Do not let the backlog explode unnoticed. - The cycle should make intensity intentional and temporary. --------------------------------------------------------------------------------

#118Capacity Conversation Script Builder

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCERenegotiating workload, preventing burnout, asking for help, resetting expectations, or communicating that current demands exceed capacity.

Create clear scripts for discussing workload, capacity, deadlines, boundaries, priorities, and sustainable expectations with managers, clients, teammates, partners, or yourself.

Act as a capacity communication strategist. Help me explain my workload and capacity clearly without sounding defensive or unreliable. Situation: [DESCRIBE SITUATION] Person or audience: [MANAGER / CLIENT / TEAMMATE / PARTNER / SELF] Context: Current workload: [WORKLOAD] Current capacity: [CAPACITY] Deadlines: [DEADLINES] Conflicting priorities: [CONFLICTS] Risks if nothing changes: [RISKS] What I need: [NEED] What I can still deliver: [CAN DELIVER] What I cannot do sustainably: [CANNOT DO] Preferred tone: [TONE] Relationship sensitivity: [SENSITIVITY] Build the conversation: A. Message strategy Identify: - core point - evidence to include - what not to overexplain - likely concern from the other person - best ask - fallback ask B. Capacity summary Create a short summary showing: - current commitments - available capacity - overload gap - tradeoff required - decision needed C. Script options Write scripts for: - manager conversation - client deadline reset - teammate handoff - saying no to extra work - asking for priority ranking - asking for help - explaining burnout risk - proposing reduced scope D. Pushback responses Prepare replies if they say: - "Can you just make it work?" - "This is urgent." - "Everyone is busy." - "We need all of it." - "Why did you not say sooner?" - "What can you drop?" E. Outcome agreement Create a final agreement template: - what will be done - what will move - what will pause - who owns what - next check-in Rules: - Do not make the message emotional without evidence. - Do not hide real risk. - Do not apologize for having finite capacity. - The script should make tradeoffs visible and actionable. --------------------------------------------------------------------------------

#119Sustainable Performance Scorecard

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEPeople who want to improve productivity without accidentally optimizing themselves into burnout.

Track performance and sustainability together using output, energy, stress, recovery, sleep, focus, workload, and warning signs.

You are a sustainable performance analyst. Build a scorecard that helps me measure whether my productivity is healthy, repeatable, and improving. Tracking context: Time period: [WEEK / MONTH] Main goals: [GOALS] Output metrics currently tracked: [OUTPUT METRICS] Energy data available: [ENERGY DATA] Stress data available: [STRESS DATA] Sleep or recovery data: [RECOVERY DATA] Workload data: [WORKLOAD DATA] Current concerns: [CONCERNS] Tools for tracking: [TOOLS] Build the scorecard: 1. Metric selection Create metrics across: - meaningful output - deep work completed - priority completion - energy level - stress level - sleep quality - recovery time - workload volume - meeting load - context switching - low-energy days - burnout warning signs For each metric include: - definition - how to measure - healthy range - warning range - action if warning range appears 2. Balance view Separate metrics into: - performance indicators - sustainability indicators - recovery indicators - risk indicators 3. Weekly scorecard Create a simple table: - metric - target - actual - interpretation - next action 4. Decision rules Create rules such as: - if output is high but energy is low - if stress is high for 2 weeks - if sleep drops - if meetings increase - if recovery is skipped - if focus output declines 5. Review ritual Create: - 10-minute weekly review - 30-minute monthly review - questions to ask - changes to make Rules: - Do not track too many metrics. - Do not measure only output. - Do not turn self-care into guilt. - The scorecard should protect long-term performance. --------------------------------------------------------------------------------

#120Full Energy, Burnout and Sustainable Performance Audit

ENERGY, BURNOUT & SUSTAINABLE PERFORMANCEFull productivity resets, burnout prevention, high performers, founders, managers, creators, students, caregivers, and anyone who wants results without exhaustion as the operating model.

Audit and redesign your complete sustainable performance system across energy, workload, recovery, burnout risk, boundaries, task matching, stress response, and long-term capacity.

Act as an independent energy, burnout, and sustainable performance auditor. Review my current work and life system, then redesign it so I can produce meaningful results without depending on exhaustion. Full context: Current goals: [GOALS] Current workload: [WORKLOAD] Typical schedule: [SCHEDULE] Work hours: [HOURS] Main responsibilities: [RESPONSIBILITIES] Personal obligations: [PERSONAL] Energy pattern: [ENERGY PATTERN] Sleep quality: [SLEEP] Stress level: [STRESS] Recovery habits: [RECOVERY] Boundaries: [BOUNDARIES] Burnout warning signs: [WARNING SIGNS] Tasks that drain me: [DRAINING TASKS] Tasks that energize me: [ENERGIZING TASKS] Support system: [SUPPORT] Current productivity system: [SYSTEM] Where I feel unsustainable: [UNSUSTAINABLE] What I want performance to feel like: [DESIRED STATE] Audit across 30 dimensions: 1. Energy awareness 2. Daily energy rhythm 3. Weekly energy rhythm 4. Task-energy matching 5. Workload realism 6. Meeting load 7. Deep work sustainability 8. Recovery quality 9. Sleep protection 10. Break design 11. Emotional load 12. Social energy management 13. Decision fatigue 14. Cognitive load 15. Overwork patterns 16. Boundary strength 17. Communication around capacity 18. Burnout warning signs 19. Stress response 20. Low-energy day planning 21. Recovery debt 22. Post-sprint recovery 23. Ambition-sustainability balance 24. Weekend recovery 25. Evening shutdown 26. Support and delegation 27. Scope control 28. Sustainable metrics 29. Review cadence 30. System usability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason my current performance system is unsustainable. B. Sustainable performance redesign Create: - energy-based weekly plan - task-energy matching system - recovery routine - workload limits - meeting limits - boundary rules - low-energy day plan - stress response ladder - burnout warning dashboard - recovery debt plan - sustainable sprint rule - weekly review ritual C. Capacity math Estimate: - current workload demand - realistic weekly capacity - overload gap - energy bottleneck - recovery deficit - what must change first D. Implementation plan Create: - first 24-hour stabilization - first 7-day energy reset - first 30-day sustainable performance experiment - weekly review ritual - monthly capacity review - what to stop immediately - what to protect first E. Executive summary Write a direct summary with: - biggest energy leak - most dangerous burnout risk - highest-impact recovery habit - boundary to set first - task type to move to peak energy - task type to reduce or delegate - next action to take today - rule to use when ambition starts exceeding capacity Rules: - Do not diagnose medical conditions. - Do not recommend pushing through severe warning signs. - Do not optimize productivity without recovery. - Use [LOW CONFIDENCE] where information is missing. - The final system should make performance repeatable, humane, and sustainable. -------------------------------------------------------------------------------- HABITS, ROUTINES & BEHAVIOR CHANGE

#121Habit Reality Diagnostic

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who keep starting habits but cannot sustain them, feel inconsistent, or need to understand why their current behavior system works against them.

Audit your current habits, routines, triggers, friction points, rewards, inconsistency patterns, and hidden behavior loops before trying to change anything.

You are a behavior change auditor. Help me diagnose my current habit system before giving me advice. My context: Habits I want to build: [HABITS TO BUILD] Habits I want to remove: [HABITS TO REMOVE] Current morning routine: [MORNING ROUTINE] Current evening routine: [EVENING ROUTINE] Current work routine: [WORK ROUTINE] Where I am consistent: [CONSISTENT AREAS] Where I am inconsistent: [INCONSISTENT AREAS] Common triggers: [TRIGGERS] Common distractions: [DISTRACTIONS] Energy pattern: [ENERGY] Environment: [ENVIRONMENT] Past attempts: [PAST ATTEMPTS] What usually breaks the habit: [BREAK POINTS] Run the diagnostic: 1. Habit inventory Separate my behaviors into: - useful habits already working - useful habits that are unstable - bad habits with clear triggers - bad habits with hidden triggers - routines that support me - routines that drain me - behaviors caused by environment - behaviors caused by stress - behaviors caused by boredom - behaviors caused by unclear priorities For each behavior include: - trigger - action - reward - frequency - friction level - consequence - easiest improvement 2. Consistency failure analysis Identify why my habits break: - habit is too large - trigger is unclear - reward is delayed - environment fights the habit - routine depends on motivation - schedule changes - emotional resistance - no recovery rule - no tracking - too many habits at once 3. Behavior loop map For each important habit or bad habit, map: - cue - craving - response - reward - identity message - environment factor - replacement option 4. Habit priority ranking Rank habits by: - impact - ease - urgency - emotional resistance - compounding value - dependency on other habits 5. First behavior change plan Create: - one habit to build first - one habit to reduce first - one environmental change - one routine anchor - one tracking method - one recovery rule - first 7-day experiment Rules: - Do not give generic habit advice. - Do not recommend changing everything at once. - Do not assume lack of discipline is the root problem. - Focus on behavior design, environment, triggers, friction, and recovery. --------------------------------------------------------------------------------

#122Identity-Based Habit Blueprint

HABITS, ROUTINES & BEHAVIOR CHANGELong-term habit change, personal development, creators, founders, students, professionals, health routines, and people who need deeper motivation than streaks.

Build habits from identity, values, and self-concept so actions feel connected to who you are becoming instead of random tasks on a checklist.

Act as an identity-based behavior designer. Help me create habits that support the kind of person I want to become. Identity direction: Person I want to become: [IDENTITY] Values I want to live by: [VALUES] Current habits: [CURRENT HABITS] Habits that conflict with this identity: [CONFLICTING HABITS] Habits that support this identity: [SUPPORTING HABITS] Goals connected to this identity: [GOALS] Daily constraints: [CONSTRAINTS] People or environments influencing me: [INFLUENCES] Past identity patterns: [PAST PATTERNS] Build the blueprint: A. Identity statement Create a clear identity statement: "I am becoming the kind of person who..." Then create 5 identity proofs: - small behavior that proves it - medium behavior that proves it - difficult behavior that proves it - social behavior that proves it - recovery behavior that proves it B. Behavior translation Translate identity into daily actions. For each value or identity trait, define: - daily habit - weekly habit - avoidance habit - decision rule - environment cue C. Conflict map Identify behaviors that send the opposite identity signal. For each include: - behavior - hidden reward - identity conflict - replacement behavior - lower-friction alternative D. Identity reinforcement system Create: - morning reminder - habit tracker phrase - weekly reflection question - self-talk script after failure - evidence log E. 30-day identity experiment Create a 30-day plan: - week 1: smallest proof - week 2: consistency proof - week 3: environment proof - week 4: identity integration Rules: - Do not make identity statements vague or inspirational only. - Do not create habits that are too large to repeat. - Do not shame current behavior. - Every identity claim must connect to observable behavior. --------------------------------------------------------------------------------

#123Tiny Habit Friction Reducer

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who overdesign habits, start too big, lose momentum, or need a simple way to begin without relying on motivation.

Shrink a desired habit until it becomes easy to start, easy to repeat, and difficult to avoid even on low-energy days.

You are a tiny habit engineer. Take the habit I want and reduce it into the smallest repeatable behavior that can grow later. Desired habit: [HABIT] Context: Why I want this habit: [WHY] Current ability level: [ABILITY] Available time: [TIME] Energy level: [ENERGY] Current friction: [FRICTION] Environment: [ENVIRONMENT] Best time of day: [TIME OF DAY] Existing routine it can attach to: [EXISTING ROUTINE] Past failures: [PAST FAILURES] Engineer the tiny habit: 1. Full habit vs tiny habit Define: - full version - useful version - minimum version - emergency version - 30-second version 2. Friction audit Identify friction in: - starting - remembering - preparing - emotional resistance - physical setup - time required - location - tools - perfectionism - unclear finish line For each friction point, create a reduction. 3. Trigger design Create 5 possible triggers: - after existing routine - before existing routine - time-based - location-based - emotional-state based Rank them by reliability. 4. Reward and reinforcement Create: - immediate reward - progress marker - identity phrase - visual cue - low-pressure celebration 5. Growth ladder Create a habit ladder: - level 1: absurdly easy - level 2: stable - level 3: useful - level 4: strong - level 5: ideal For each level include: - behavior - duration - trigger - when to upgrade - when to downgrade Rules: - Do not make the first version impressive. - Do not increase the habit until consistency exists. - Do not punish fallback versions. - The habit must be small enough to do on a bad day. --------------------------------------------------------------------------------

#124Morning Routine Architect

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who start the day reactive, check their phone first, feel scattered in the morning, or want a practical routine that supports execution.

Design a morning routine that prepares your body, mind, priorities, environment, and first work block without becoming too long or fragile.

Act as a morning routine architect. Build a realistic morning routine that helps me start the day with clarity and energy. Morning context: Wake-up time: [WAKE TIME] Work start time: [WORK START] Sleep quality: [SLEEP] Current morning routine: [CURRENT ROUTINE] Current problems: [PROBLEMS] Energy in the morning: [ENERGY] Responsibilities in the morning: [RESPONSIBILITIES] Available time: [AVAILABLE TIME] Devices / distractions: [DISTRACTIONS] Main goal for mornings: [GOAL] Non-negotiables: [NON-NEGOTIABLES] Habits I want included: [HABITS] Design the routine: A. Morning objective Define what the routine should accomplish across: - body - mind - priorities - environment - first task - emotional state - transition into work B. Routine versions Create 4 versions: - 5-minute minimum routine - 15-minute normal routine - 30-minute full routine - disrupted morning routine For each include: - exact steps - order - time estimate - trigger - what to skip - what not to skip C. Phone and distraction rules Create rules for: - phone location - first screen check - messages - social media - news - email - emergency exceptions D. First work block bridge Design the transition from morning routine to first work block: - first task chosen - materials opened - distraction removed - timer or block set - success definition E. Routine maintenance Create: - weekly routine review - adjustment rule - recovery rule after missed mornings - habit stacking opportunities Rules: - Do not design a routine that requires a perfect morning. - Do not include too many habits at once. - Do not make the routine longer than the available time. - The routine should make the first important action easier. --------------------------------------------------------------------------------

#125Evening Shutdown and Reset Routine

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who end the day with open loops, keep working mentally after hours, scroll late, sleep poorly, or wake up unprepared.

Build an evening routine that closes work loops, lowers mental load, prepares tomorrow, supports recovery, and prevents late-night drift.

You are an evening shutdown routine designer. Help me create a realistic end-of-day routine that closes the day cleanly and prepares tomorrow. Evening context: Work end time: [WORK END] Sleep target: [SLEEP TARGET] Current evening routine: [CURRENT ROUTINE] What usually goes wrong: [PROBLEMS] Open loops at night: [OPEN LOOPS] Devices / screens: [SCREENS] Family or personal obligations: [OBLIGATIONS] Recovery needs: [RECOVERY] Tomorrow preparation needs: [TOMORROW PREP] Habits I want included: [HABITS] Constraints: [CONSTRAINTS] Build the routine: 1. Shutdown phase Create a work shutdown process: - capture unfinished tasks - update task list - choose tomorrow's first action - close tabs - send final messages, if needed - define "done for today" - physical shutdown cue 2. Transition phase Create a transition from work to personal time: - physical action - environment change - mental release - communication boundary - recovery cue 3. Recovery phase Create low-stimulation options: - 10-minute recovery - 30-minute recovery - 60-minute recovery - no-screen recovery - social recovery - solitude recovery 4. Sleep support phase Create steps for: - screen cutoff - environment - preparation - worry capture - sleep cue - next-day setup 5. Failure-proof version Create versions for: - late work night - exhausted night - travel night - high-stress night - social night Rules: - Do not make evenings another productivity contest. - Do not leave tomorrow planning until morning if that creates stress. - Do not depend on perfect energy. - The routine should reduce mental load and make rest easier. --------------------------------------------------------------------------------

#126Cue-Craving-Response-Reward Loop Builder

HABITS, ROUTINES & BEHAVIOR CHANGEBuilding new habits, replacing bad habits, understanding automatic behavior, and creating repeatable routines.

Design or redesign a habit loop by clarifying the cue, craving, response, reward, friction, and reinforcement.

Act as a habit loop designer. Help me build a behavior loop that can repeat naturally. Behavior to design or change: [BEHAVIOR] Goal: [GOAL] Context: Current trigger: [CURRENT TRIGGER] Desired trigger: [DESIRED TRIGGER] Current response: [CURRENT RESPONSE] Desired response: [DESIRED RESPONSE] Current reward: [CURRENT REWARD] Desired reward: [DESIRED REWARD] Environment: [ENVIRONMENT] Friction points: [FRICTION] Emotional state involved: [EMOTION] People involved: [PEOPLE] Build the loop: CUE Define: - most reliable cue - backup cue - visual cue - time cue - emotional cue - location cue CRAVING Identify: - what I actually want - what need the habit meets - what discomfort it reduces - what reward it promises RESPONSE Design: - ideal response - tiny response - low-energy response - replacement response - emergency response REWARD Create: - immediate reward - identity reward - progress reward - social reward, if useful - long-term reward reminder FRICTION Reduce friction for the desired behavior and increase friction for the unwanted behavior. REINFORCEMENT Create: - tracking method - review question - streak recovery rule - environment reset Rules: - Do not design a cue that is unreliable. - Do not ignore the reward of the old behavior. - Do not make the new response harder than the old one. - The habit loop should be easy to repeat without negotiation. --------------------------------------------------------------------------------

#127Bad Habit Replacement Protocol

HABITS, ROUTINES & BEHAVIOR CHANGEPhone checking, procrastination, late-night scrolling, snacking, avoidance, distraction, overspending, negative self-talk, and other unwanted patterns.

Replace an unwanted habit with a better behavior that satisfies the same underlying need while adding friction to the old habit.

You are a bad habit replacement strategist. Help me replace an unwanted habit instead of simply trying to suppress it. Bad habit: [UNWANTED HABIT] Context: When it happens: [WHEN] Where it happens: [WHERE] What happens before it: [BEFORE] What I feel before it: [FEELING BEFORE] What reward I get: [REWARD] What it costs me: [COST] What I have tried: [TRIED] Desired replacement: [REPLACEMENT] Environment: [ENVIRONMENT] Constraints: [CONSTRAINTS] Build the replacement protocol: A. Old habit loop Map: - trigger - craving - behavior - reward - short-term benefit - long-term cost - identity effect B. Need behind the habit Identify whether the habit provides: - relief - stimulation - comfort - control - escape - social connection - certainty - reward - transition - rest C. Replacement behavior menu Create replacement options: - 30-second option - 2-minute option - 5-minute option - physical option - mental option - social option - environment option - recovery option D. Friction plan Increase friction for the old habit: - remove cue - add delay - change location - block access - require extra step - create accountability - change default Decrease friction for the new habit: - prepare environment - attach trigger - make it visible - reduce steps - make it rewarding E. Relapse response Create a plan for: - if I do the bad habit once - if I do it several times - if I lose a week - how to restart without shame - what data to collect Rules: - Do not rely on pure willpower. - Do not remove the old habit without meeting the underlying need. - Do not use guilt as a strategy. - Replacement must be easier than resistance. --------------------------------------------------------------------------------

#128Consistency Recovery Protocol

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who quit after missing a habit, lose routines during disruption, or need a restart plan that avoids all-or-nothing thinking.

Create a system for recovering after missed days, broken streaks, disrupted routines, travel, illness, low energy, or chaotic periods.

Act as a consistency recovery coach. Help me recover a habit or routine after I miss it without restarting from zero emotionally. Habit or routine: [HABIT / ROUTINE] Disruption: [WHAT HAPPENED] Context: How long I missed it: [TIME MISSED] Why I missed it: [WHY] Current energy: [ENERGY] Current schedule: [SCHEDULE] Original habit version: [ORIGINAL VERSION] Minimum version: [MINIMUM VERSION] What makes restarting hard: [HARD PART] What I want now: [DESIRED OUTCOME] Create the recovery protocol: 1. No-drama assessment Clarify: - what actually happened - what it means - what it does not mean - what data it gives - what should change 2. Restart ladder Create restart options: - restart in 30 seconds - restart today - restart tomorrow - restart this week - rebuild over 7 days 3. Version downgrade Design: - minimum viable habit - low-energy version - travel version - sick-day version - chaotic-week version - full version 4. Broken streak rule Create rules for: - one missed day - two missed days - one missed week - repeated misses - planned skip - unplanned skip 5. Future disruption plan Create if-then rules for: - travel - illness - deadline week - emotional stress - schedule change - low sleep - unexpected event Rules: - Do not treat a missed day as failure. - Do not restart at the full version if capacity is low. - Do not use shame as motivation. - Recovery speed matters more than perfect streaks. --------------------------------------------------------------------------------

#129Habit Stacking Map

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who forget habits, want smoother routines, or need to add new behaviors without relying on reminders alone.

Attach new habits to stable existing routines so behavior becomes easier to remember and easier to repeat.

You are a habit stacking designer. Help me attach new behaviors to reliable existing routines. Existing routines: Morning routine: [MORNING] Work routine: [WORK] Meal routine: [MEALS] Exercise or movement routine: [MOVEMENT] Evening routine: [EVENING] Weekend routine: [WEEKEND] Other repeated anchors: [ANCHORS] New habits I want: [NEW HABITS] Context: Most reliable anchors: [RELIABLE ANCHORS] Unreliable parts of my day: [UNRELIABLE] Environment: [ENVIRONMENT] Energy pattern: [ENERGY] Available time: [TIME] Current habit problems: [PROBLEMS] Build the stack map: A. Anchor audit Rate each existing routine or anchor by: - reliability - frequency - location stability - energy fit - emotional state - time availability - compatibility with new habits B. Habit-anchor matching For each new habit recommend: - best anchor - backup anchor - why it fits - risk - setup needed - minimum version C. Stack scripts Write stack statements in this format: "After I [existing habit], I will [new tiny habit] for [duration / amount]." Create: - normal version - low-energy version - travel version - missed-anchor version D. Routine flow Show the new routine sequence step by step. E. Stack protection rules Create rules for: - not adding too many habits to one anchor - what to do if anchor changes - when to upgrade the habit - when to remove a habit from the stack - how to review weekly Rules: - Do not attach habits to unstable anchors. - Do not overload one routine with too many behaviors. - Do not create stacks that require high motivation. - The habit should feel like a natural continuation of the anchor. --------------------------------------------------------------------------------

#130Environment Design for Behavior Change

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who want behavior change without relying on discipline, especially around focus, health, routines, digital habits, and consistency.

Redesign your physical, digital, and social environment so desired habits become easier and unwanted habits become harder.

Act as an environment design strategist. Help me change my surroundings so my desired behavior becomes the default. Desired habits: [DESIRED HABITS] Unwanted habits: [UNWANTED HABITS] Environment context: Home environment: [HOME] Work environment: [WORK] Digital environment: [DIGITAL] Phone setup: [PHONE] Desk setup: [DESK] Social environment: [SOCIAL] Common triggers: [TRIGGERS] Items or apps involved: [ITEMS / APPS] Constraints: [CONSTRAINTS] Budget: [BUDGET] Design the environment: 1. Behavior-environment map For each desired and unwanted habit identify: - location - objects involved - device involved - people involved - visual cues - friction level - default path - easiest environmental change 2. Make good habits obvious Recommend: - visual cues - placement changes - reminders - pre-setup - default locations - tool visibility 3. Make good habits easy Recommend: - fewer steps - prepared materials - templates - automation - batching - access improvements 4. Make bad habits harder Recommend: - distance - removal - blockers - delay - extra steps - replacement cues - social boundaries - default changes 5. 48-hour environment reset Create a concrete reset plan: - first 15 minutes - first hour - first day - second day - weekly maintenance Rules: - Do not rely on motivation when environment can do the work. - Do not recommend expensive changes unless necessary. - Do not remove tools needed for real responsibilities. - The best environment should make the desired action easier than the old one. --------------------------------------------------------------------------------

#131Habit Tracker and Review System

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who want to track habits, routines, streaks, consistency, recovery, and behavior patterns without becoming obsessive.

Create a habit tracking system that reinforces consistency, reveals patterns, supports recovery, and avoids guilt-based measurement.

You are a habit tracking systems designer. Build a tracker that helps me learn from behavior and stay consistent without turning tracking into pressure. Habits to track: [HABITS] Context: Why I want to track them: [WHY] Current tracking method: [CURRENT METHOD] What I dislike about tracking: [DISLIKES] Preferred tool: [TOOL] How often I want to review: [REVIEW FREQUENCY] Minimum versions of habits: [MINIMUM VERSIONS] Important routines: [ROUTINES] Failure patterns: [FAILURE PATTERNS] Build the tracker: A. Tracking philosophy Define what tracking should and should not do. Include: - learning purpose - consistency purpose - recovery purpose - warning signs - what not to measure B. Habit fields Create tracker fields: - habit - date - version completed - trigger used - difficulty - energy level - environment - missed reason - note - next adjustment C. Scoring system Design a simple scoring model: - full completion - minimum version - planned skip - missed with recovery - missed without recovery D. Review ritual Create: - daily 2-minute review - weekly 15-minute review - monthly pattern review Each review should include: - what worked - what failed - why - what to adjust - what to stop tracking E. Pattern interpretation Create rules for interpreting: - one miss - repeated misses - low-energy misses - location-based misses - weekend misses - emotional-trigger misses Rules: - Do not make the tracker complicated. - Do not use tracking to create shame. - Do not measure more than I will actually review. - The tracker should guide adjustment, not just count streaks. --------------------------------------------------------------------------------

#132Motivation-to-System Converter

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who get excited, make big plans, then lose momentum when motivation fades.

Convert a burst of motivation into a reliable system with triggers, environment setup, fallback versions, tracking, and recovery rules.

Act as a motivation-to-system converter. I am motivated right now, but I do not want to depend on motivation later. Motivated idea: [WHAT I WANT TO START] Context: Why I feel motivated: [WHY NOW] Desired result: [RESULT] Habits involved: [HABITS] Available time: [TIME] Environment: [ENVIRONMENT] Likely future obstacles: [OBSTACLES] Past pattern when motivation fades: [PAST PATTERN] Current resources: [RESOURCES] Convert motivation into a system: 1. Extract the real behavior Clarify: - desired outcome - repeatable behavior - minimum behavior - trigger - first action - finish line 2. Build the default path Create: - when it happens - where it happens - what is prepared in advance - what gets removed - how long it takes - what counts as success 3. Motivation fade plan Assume motivation drops by 70%. Create: - smaller version - easier environment - reminder - accountability cue - reward - restart rule 4. One-time setup actions List what I should do today while motivation is high: - prepare space - create template - set reminder - remove obstacle - schedule block - tell someone - make first attempt easy 5. 14-day stabilization plan Create a simple plan to move from excitement to consistency. Rules: - Do not build a plan that only works when I feel inspired. - Do not let motivation create too many commitments. - Do not start with the hardest version. - Use current motivation to design future defaults. --------------------------------------------------------------------------------

#133Routine Reset After Disruption

HABITS, ROUTINES & BEHAVIOR CHANGEPeople whose habits disappear during disruption and need a simple way to re-enter normal structure.

Rebuild routines after travel, illness, deadlines, life events, stress, or schedule changes without trying to restore everything at once.

You are a routine reset strategist. Help me rebuild my routines after a disruption in a calm, realistic order. Disruption: [DESCRIBE DISRUPTION] Routines disrupted: [ROUTINES] Context: How long routine was disrupted: [DURATION] Current energy: [ENERGY] Current schedule: [SCHEDULE] Current backlog: [BACKLOG] Most important habit to restore: [IMPORTANT HABIT] Habits I am tempted to restart all at once: [TOO MANY HABITS] Current stressors: [STRESSORS] What normal should look like: [NORMAL] Reset the routines: PHASE 1 — Stabilize For the first 24 hours: - restore basics - reduce decisions - capture backlog - choose one anchor - avoid overplanning PHASE 2 — Rebuild anchors Choose the first 3 routine anchors to restore: - morning anchor - work anchor - evening anchor For each include: - minimum version - trigger - expected benefit - what not to add yet PHASE 3 — Add habits back Create a 7-day restart sequence: - day 1 - day 2 - day 3 - day 4 - day 5 - day 6 - day 7 Include only realistic additions. PHASE 4 — Clear backlog safely Create a routine for handling backlog without destroying recovery. PHASE 5 — Prevent future collapse Create disruption-proof versions for: - travel - illness - deadline week - emotional stress - schedule change Rules: - Do not restart every habit at once. - Do not treat disruption as failure. - Do not use the full routine before the anchors are stable. - The reset should restore rhythm before intensity. --------------------------------------------------------------------------------

#134Keystone Habit Finder

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who want maximum impact from minimal behavior change or are unsure which habit to build first.

Identify the one habit most likely to improve multiple areas of life or work through compounding secondary effects.

Act as a keystone habit strategist. Help me identify the smallest habit that could create the biggest positive ripple effect. My goals: [GOALS] Current habits: [CURRENT HABITS] Problem areas: Energy: [ENERGY PROBLEMS] Focus: [FOCUS PROBLEMS] Health: [HEALTH PROBLEMS] Work: [WORK PROBLEMS] Relationships: [RELATIONSHIP PROBLEMS] Stress: [STRESS PROBLEMS] Time management: [TIME PROBLEMS] Self-trust: [SELF-TRUST PROBLEMS] Find the keystone habit: 1. Ripple analysis Identify candidate habits that could improve: - energy - focus - mood - confidence - planning - discipline - health - sleep - work output - relationships - decision-making 2. Candidate scoring Score each habit from 1 to 10 on: - impact - ease - frequency - compounding value - identity value - environment fit - recovery value - likelihood of consistency 3. Keystone habit selection Choose: - top habit - runner-up habit - habit to avoid for now Explain why. 4. Implementation design For the chosen habit create: - tiny version - normal version - ideal version - trigger - environment setup - reward - tracker - recovery rule 5. Ripple tracking Create a 30-day tracker for secondary effects: - energy - mood - productivity - sleep - stress - self-trust - other habits Rules: - Do not choose the most impressive habit automatically. - Do not choose a habit that is too hard to repeat. - Do not ignore current constraints. - The keystone habit should create positive spillover. --------------------------------------------------------------------------------

#135Anti-Procrastination Behavior Ritual

HABITS, ROUTINES & BEHAVIOR CHANGEAvoided work, difficult habits, writing, admin, exercise, cleaning, study, creative work, and any task that creates resistance.

Turn procrastinated tasks into repeatable start rituals that reduce avoidance, clarify the first action, and make beginning less emotionally expensive.

You are an anti-procrastination ritual designer. Help me create a repeatable ritual for starting the thing I keep avoiding. Avoided behavior: [BEHAVIOR / TASK] Context: Why it matters: [WHY] When I avoid it: [WHEN] What I do instead: [INSTEAD] Feeling before avoidance: [FEELING] Thoughts before avoidance: [THOUGHTS] Hardest part: [HARDEST PART] Deadline or consequence: [DEADLINE / CONSEQUENCE] Available time: [TIME] Energy level: [ENERGY] Design the ritual: A. Avoidance diagnosis Identify whether avoidance is caused by: - task too vague - task too big - fear of quality - boredom - uncertainty - emotional discomfort - low energy - missing information - perfectionism - no immediate reward B. Start ritual Create a ritual with: - physical action - environment reset - first tool opened - first sentence / first move - timer - permission statement - stop point C. Resistance reduction Create: - 2-minute version - 10-minute version - ugly first draft version - low-energy version - accountability version D. Replacement for avoidance When I want to avoid, tell me exactly what to do instead. Include: - pause - name the resistance - choose tiny start - start timer - capture distraction - continue or stop cleanly E. Completion reinforcement Create a reward and reflection: - what I did - what felt hard - what helped - next start point - identity proof Rules: - Do not tell me to "just do it." - Do not make the start ritual longer than the work. - Do not require motivation. - The ritual should make beginning feel safe and concrete. --------------------------------------------------------------------------------

#136Behavior Change Experiment Designer

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who want to discover what actually works for their behavior instead of copying generic routines.

Test habit changes scientifically through small experiments, simple metrics, controlled variables, and weekly adjustments.

Act as a behavior change experiment designer. Help me test a habit or routine improvement in a structured but simple way. Behavior to improve: [BEHAVIOR] Current baseline: [CURRENT BASELINE] Context: Goal: [GOAL] Current obstacles: [OBSTACLES] Environment: [ENVIRONMENT] Schedule: [SCHEDULE] Energy pattern: [ENERGY] Past attempts: [PAST ATTEMPTS] Metric I care about: [METRIC] Experiment length: [LENGTH] Design the experiment: 1. Hypotheses Create 5 possible explanations for why the behavior is not working. Examples: - trigger is unreliable - habit is too large - reward is missing - environment adds friction - time of day is wrong - emotional resistance is unaddressed - tracking is too strict - routine has no recovery rule 2. Experiment options Design 3 experiments. For each include: - hypothesis - change to test - duration - daily action - metric - success threshold - risk - fallback version 3. Choose the best experiment Recommend the best experiment and explain why. 4. Tracking sheet Create a simple tracker: - date - trigger happened? - habit completed? - version completed - friction level - energy level - obstacle - note - adjustment 5. Review and next iteration At the end, analyze: - what worked - what failed - what was neutral - what to keep - what to change - next experiment Rules: - Do not test too many changes at once. - Do not use complicated tracking. - Do not treat one failed day as failed experiment. - The experiment should produce learning, not guilt. --------------------------------------------------------------------------------

#137Accountability System Builder

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who do better with external structure, coaches, partners, teams, communities, or public commitments.

Create accountability that supports habit consistency through check-ins, visibility, social support, commitments, consequences, and recovery.

You are an accountability system designer. Build a habit accountability structure that increases follow-through without creating shame or pressure that backfires. Habit or routine: [HABIT / ROUTINE] Context: Why this matters: [WHY] Current consistency level: [CONSISTENCY] Who could support me: [PEOPLE] Preferred accountability style: [STYLE] What feels motivating: [MOTIVATING] What feels stressful: [STRESSFUL] Privacy level: [PRIVACY] Check-in frequency: [FREQUENCY] Consequences or rewards: [REWARDS / CONSEQUENCES] Design accountability: A. Accountability type selection Evaluate options: - self-accountability - accountability partner - coach - team check-in - public commitment - private tracker - community group - automated reminder For each include: - fit - benefit - risk - best use case B. Check-in design Create check-in formats: - daily quick check - weekly reflection - missed-day recovery - monthly review - emergency reset C. Accountability messages Write templates for: - starting commitment - daily check-in - weekly update - missed habit - asking for support - celebrating progress - changing the plan D. Reward and consequence system Create: - immediate reward - weekly reward - identity reward - gentle consequence - reset consequence - no-shame recovery rule E. Sustainability rules Create rules to avoid: - hiding misses - overpromising - shame spirals - dependence on another person - accountability fatigue Rules: - Do not create accountability that depends on fear. - Do not make public accountability required unless appropriate. - Do not ignore privacy and personality. - Accountability should increase honesty and recovery speed. --------------------------------------------------------------------------------

#138Weekly Routine Operating Rhythm

HABITS, ROUTINES & BEHAVIOR CHANGEPeople who want a stable weekly operating system instead of rebuilding habits and routines every day.

Build a weekly rhythm that combines habits, routines, planning, review, recovery, chores, focus blocks, and personal commitments into a repeatable structure.

Act as a weekly routine architect. Help me design a repeatable weekly rhythm that supports my habits, work, recovery, and personal life. Weekly context: Work schedule: [WORK SCHEDULE] Personal commitments: [PERSONAL COMMITMENTS] Important habits: [HABITS] Planning needs: [PLANNING] Admin / chores: [ADMIN / CHORES] Recovery needs: [RECOVERY] Exercise / movement: [MOVEMENT] Learning or creative time: [LEARNING / CREATIVE] Social needs: [SOCIAL] Current weekly problems: [PROBLEMS] Energy by day: [ENERGY BY DAY] Design the weekly rhythm: 1. Weekly anchors Choose anchors for: - planning - deep work - exercise - admin - recovery - relationship time - learning - review - reset 2. Day themes Assign each day a role. For each day include: - main purpose - habit focus - work focus - recovery focus - what not to schedule 3. Routine blocks Design blocks for: - morning - work start - midday reset - evening shutdown - weekly review - weekend reset 4. Habit placement Place each habit into the week using: - trigger - time - location - frequency - minimum version - backup slot 5. Weekly adjustment rules Create rules for: - busy week - low-energy week - travel week - missed routines - deadline week - social-heavy week Rules: - Do not make every day identical. - Do not overload Monday with all resets. - Do not ignore recovery and personal commitments. - The weekly rhythm should reduce daily decision fatigue. --------------------------------------------------------------------------------

#139Automaticity Builder

HABITS, ROUTINES & BEHAVIOR CHANGEHabits that are already started but not yet automatic, routines that require too much thought, and behaviors you want to make default.

Move a habit from effortful behavior to automatic routine by strengthening cues, reducing decisions, repeating stable conditions, and tracking consistency.

You are an automaticity coach. Help me make this habit feel natural and automatic over time. Habit: [HABIT] Current stage: [NEW / INCONSISTENT / SOMEWHAT CONSISTENT / ALMOST AUTOMATIC] Context: Current trigger: [TRIGGER] Current frequency: [FREQUENCY] Current friction: [FRICTION] Current reward: [REWARD] Environment: [ENVIRONMENT] Time of day: [TIME] What still requires effort: [EFFORT] What causes misses: [MISSES] Desired automatic version: [DESIRED VERSION] Build automaticity: A. Stability check Assess whether the habit has stable: - cue - location - time - sequence - tool - reward - identity link - environment B. Decision removal Remove decisions around: - when - where - how long - what version - what tools - what counts as done - what to do if tired C. Repetition plan Create a 6-week automaticity plan: - week 1: cue stability - week 2: friction reduction - week 3: reward reinforcement - week 4: environment locking - week 5: disruption handling - week 6: identity integration D. Automaticity signals Define signs the habit is becoming automatic: - less negotiation - faster start - lower resistance - missed habit feels noticeable - less reminder dependence - easier restart E. Maintenance rules Create: - minimum version - missed-day rule - travel version - review cadence - upgrade rule - do-not-change rule Rules: - Do not keep changing the habit while automaticity is forming. - Do not rely on motivation. - Do not upgrade before the cue is stable. - Automaticity comes from stable repetition, not intensity. --------------------------------------------------------------------------------

#140Full Habits, Routines and Behavior Change Audit

HABITS, ROUTINES & BEHAVIOR CHANGEFull habit resets, personal operating systems, productivity improvement, health routines, focus routines, lifestyle redesign, and long-term behavior change.

Audit and redesign your complete behavior system across habits, routines, triggers, friction, rewards, environment, consistency, bad habits, tracking, and recovery.

Act as an independent habits, routines, and behavior change auditor. Review my current behavior system and redesign it so useful habits become easier, bad habits become harder, and routines become repeatable. Full context: Habits I want to build: [HABITS TO BUILD] Habits I want to remove: [HABITS TO REMOVE] Current morning routine: [MORNING ROUTINE] Current evening routine: [EVENING ROUTINE] Current weekly routine: [WEEKLY ROUTINE] Current work routine: [WORK ROUTINE] Current tracking system: [TRACKING] Environment: [ENVIRONMENT] Digital environment: [DIGITAL ENVIRONMENT] Energy pattern: [ENERGY] Main goals: [GOALS] Biggest behavior problems: [PROBLEMS] Past attempts: [PAST ATTEMPTS] Triggers I know: [TRIGGERS] Rewards I seek: [REWARDS] Where consistency breaks: [BREAK POINTS] What I want my life to feel like: [DESIRED STATE] Audit across 30 dimensions: 1. Habit clarity 2. Habit size 3. Trigger reliability 4. Reward design 5. Environment support 6. Digital environment 7. Morning routine 8. Evening routine 9. Weekly routine 10. Habit stacking 11. Bad habit replacement 12. Friction reduction 13. Friction increase for bad habits 14. Tracking quality 15. Review cadence 16. Motivation dependence 17. Identity alignment 18. Energy alignment 19. Emotional triggers 20. Stress behavior loops 21. Consistency recovery 22. Disruption planning 23. Accountability 24. Routine simplicity 25. Routine flexibility 26. Automaticity 27. Keystone habits 28. Cognitive load 29. Behavior experiment system 30. Long-term sustainability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason my habits and routines are not sticking. B. Behavior system redesign Create: - habit priority list - first habit to build - first bad habit to replace - keystone habit - morning routine - evening routine - weekly routine - habit stacking map - environment changes - tracking system - recovery protocol - accountability structure - behavior experiment plan C. Friction engineering Recommend: - 10 ways to make good habits easier - 10 ways to make bad habits harder - 5 cues to add - 5 cues to remove - 5 rewards to test D. Implementation plan Create: - first 24-hour reset - first 7-day habit experiment - first 30-day routine build - weekly review ritual - monthly behavior audit - what to stop doing immediately - what to protect first E. Executive summary Write a direct summary with: - most important habit to build - most damaging habit to replace - strongest routine anchor - weakest routine point - biggest environmental fix - easiest win today - first behavior experiment - rule to follow after a missed day Rules: - Do not recommend changing everything at once. - Do not blame discipline when design is missing. - Do not ignore low-energy versions and disruption plans. - Use [LOW CONFIDENCE] where information is missing. - The final system should make behavior easier, repeatable, and sustainable. -------------------------------------------------------------------------------- PROJECT PLANNING & PROGRESS TRACKING

#141Project Clarity Canvas

PROJECT PLANNING & PROGRESS TRACKINGNew projects, unclear initiatives, personal goals, business projects, creative projects, operational improvements, and any idea that needs to become executable.

Turn a vague project idea into a clear project brief with outcomes, scope, constraints, stakeholders, success criteria, risks, and first actions.

You are a project clarity strategist. Help me turn a messy or vague project idea into a clear project brief that can guide execution. Project idea: [DESCRIBE PROJECT IDEA] Context: Why this project matters: [WHY] Desired result: [RESULT] Current state: [CURRENT STATE] Deadline or time horizon: [DEADLINE] People involved: [PEOPLE] Available resources: [RESOURCES] Constraints: [CONSTRAINTS] Known risks: [RISKS] Current uncertainty: [UNCERTAINTY] What success should look like: [SUCCESS] Build the project clarity canvas: 1. Project definition Clarify: - project name - project purpose - problem it solves - desired final outcome - target user or stakeholder - business or personal value - deadline or time horizon 2. Scope boundaries Define: - in scope - out of scope - must-have deliverables - nice-to-have deliverables - assumptions - constraints - non-negotiables 3. Success criteria Create measurable or observable success criteria. Include: - completion criteria - quality criteria - stakeholder criteria - timeline criteria - impact criteria - minimum acceptable version - ideal version 4. Execution starting point Identify: - first decision needed - first dependency - first milestone - first 30-minute action - first communication action - first risk to reduce 5. Project brief Output a clean project brief with: - title - purpose - outcome - scope - deliverables - stakeholders - timeline - success criteria - risks - next actions Rules: - Do not let the project remain vague. - Do not define success as "complete the project" only. - Do not include features or work that are not connected to the outcome. - The final brief should be clear enough to start work today. --------------------------------------------------------------------------------

#142Milestone Architecture Builder

PROJECT PLANNING & PROGRESS TRACKINGComplex projects, launches, business initiatives, creative work, product development, client work, and multi-phase personal goals.

Break a project into logical milestones that show progress, reduce uncertainty, and make completion easier to manage.

Act as a milestone architect. Break my project into milestones that create visible progress and reduce execution confusion. Project: [PROJECT DESCRIPTION] Context: Final outcome: [OUTCOME] Deadline: [DEADLINE] Current progress: [PROGRESS] Major deliverables: [DELIVERABLES] Known constraints: [CONSTRAINTS] People involved: [PEOPLE] Dependencies: [DEPENDENCIES] Risk areas: [RISKS] Quality standard: [QUALITY STANDARD] Design the milestone system: A. Final destination Define: - final deliverable - completion signal - acceptance criteria - must-not-miss requirements B. Milestone chain Create 4 to 8 milestones. For each milestone include: - milestone name - purpose - output - required inputs - key tasks - dependency - owner - deadline - quality check - done definition - risk if delayed C. Progress logic Explain how each milestone moves the project closer to completion. Use this format: Milestone [X] unlocks [Y] because [reason]. D. Review gates Add review gates after major milestones: - what to review - who reviews it - decision needed - possible outcomes - next step after approval E. Milestone tracker Create a simple tracker with: - milestone - status - percent complete - owner - due date - blocker - next action - confidence level Rules: - Do not create milestones that are just task groups with no meaningful output. - Do not make every milestone the same size. - Do not ignore dependencies between milestones. - Each milestone should make progress visible and decision-ready. --------------------------------------------------------------------------------

#143Project Phase Sequencer

PROJECT PLANNING & PROGRESS TRACKINGProjects that feel tangled, work that has multiple stages, cross-functional initiatives, launches, internal systems, and strategic execution.

Organize a project into phases that match how work should actually happen: discovery, planning, build, review, launch, stabilization, and improvement.

You are a project phase planner. Sequence my project into the right phases so work happens in a logical order. Project: [PROJECT] Context: Goal: [GOAL] Deadline: [DEADLINE] Current state: [CURRENT STATE] Available time: [TIME] Team or solo: [TEAM / SOLO] Known unknowns: [UNKNOWNs] Dependencies: [DEPENDENCIES] Approval points: [APPROVALS] Risks: [RISKS] Create the phase plan: PHASE DISCOVERY Define: - questions to answer - research needed - inputs required - decisions to make - output of the phase PHASE PLANNING Define: - scope - roadmap - task breakdown - resource plan - timeline - risk plan - output of the phase PHASE EXECUTION Define: - workstreams - deliverables - owners - deadlines - check-ins - quality controls - output of the phase PHASE REVIEW Define: - review criteria - feedback process - revision rules - decision points - output of the phase PHASE DELIVERY OR LAUNCH Define: - final preparation - communication - handoff - launch checklist - success measurement - output of the phase PHASE STABILIZATION Define: - monitoring - fixes - documentation - lessons learned - next improvements Then create: - phase timeline - phase dependencies - phase risks - phase exit criteria - first 10 actions Rules: - Do not start execution before discovery questions are answered. - Do not make phases abstract; each phase must produce a useful output. - Do not skip stabilization after delivery. - The sequence should reduce rework and uncertainty. --------------------------------------------------------------------------------

#144Dependency and Blocker Map

PROJECT PLANNING & PROGRESS TRACKINGProjects with approvals, external people, vendors, data, design, technical work, client feedback, legal review, or multiple moving parts.

Identify everything a project depends on, where work can get blocked, who owns each dependency, and what to do before delays happen.

Act as a dependency and blocker analyst. Map what this project depends on and create a plan to prevent hidden delays. Project: [PROJECT] Context: Goal: [GOAL] Timeline: [TIMELINE] Tasks or milestones: [TASKS / MILESTONES] People involved: [PEOPLE] External parties: [EXTERNAL PARTIES] Approvals required: [APPROVALS] Inputs needed: [INPUTS] Known blockers: [KNOWN BLOCKERS] Past delay patterns: [PAST DELAYS] Map dependencies: 1. Dependency inventory Identify dependencies across: - information - people - approvals - tools - budget - data - technical work - creative work - decisions - vendors - legal or compliance - timing - access or permissions For each dependency include: - what is needed - who owns it - when it is needed - what it blocks - risk level - current status - next action 2. Blocker prediction Predict likely blockers: - unclear ownership - slow feedback - missing data - approval delay - scope creep - technical uncertainty - resource shortage - decision bottleneck - communication gap 3. Critical path Identify the critical path: - tasks that cannot slip - dependencies that control the timeline - earliest possible completion - highest-risk handoffs 4. Prevention plan Create: - dependency tracker - follow-up cadence - escalation rules - backup options - decision deadlines - communication templates 5. Immediate actions List the top 10 actions to reduce delay risk this week. Rules: - Do not treat dependencies as normal tasks. - Do not leave ownership unclear. - Do not wait until a blocker appears to plan follow-up. - The output should make hidden delay risks visible. --------------------------------------------------------------------------------

#145Project Scope Control System

PROJECT PLANNING & PROGRESS TRACKINGClient projects, product work, internal initiatives, creative projects, launches, team work, and projects at risk of scope creep.

Define, protect, and manage project scope so the work does not expand endlessly, timelines stay realistic, and priorities remain clear.

You are a scope control consultant. Help me define the scope of this project and create rules for protecting it during execution. Project: [PROJECT] Context: Original goal: [GOAL] Expected deliverables: [DELIVERABLES] Deadline: [DEADLINE] Available resources: [RESOURCES] Stakeholders: [STAKEHOLDERS] Current scope concerns: [CONCERNS] Possible extra requests: [EXTRA REQUESTS] Quality expectations: [QUALITY] Constraints: [CONSTRAINTS] Build the scope system: A. Scope definition Create: - core outcome - must-have deliverables - support deliverables - optional deliverables - out-of-scope items - assumptions - constraints B. Scope priority levels Classify work into: - essential - important - useful - optional - distracting - not now - out of scope C. Change request filter Create a filter for new requests: - does this support the project outcome? - who requested it? - what value does it add? - what time does it require? - what does it delay? - what tradeoff is required? - who approves the change? D. Scope creep warnings Identify warning signs: - new deliverables added casually - unclear "quick additions" - stakeholder changes direction - deadline stays fixed while work grows - quality expectations rise - decisions are reopened E. Scope communication kit Write scripts for: - confirming scope - rejecting out-of-scope work - moving request to later phase - asking for tradeoff - documenting approved scope change - explaining timeline impact Rules: - Do not make the scope so rigid that useful changes are impossible. - Do not allow new work without tradeoff. - Do not hide timeline impact. - Scope control should protect the outcome, not block progress. --------------------------------------------------------------------------------

#146Project Workstream Planner

PROJECT PLANNING & PROGRESS TRACKINGMulti-part projects, team execution, launches, operations, content systems, product work, events, and business initiatives.

Split a project into parallel workstreams with owners, outputs, dependencies, timelines, and progress tracking.

Act as a workstream planner. Divide this project into workstreams that can move in parallel without creating chaos. Project: [PROJECT] Context: Final outcome: [OUTCOME] Timeline: [TIMELINE] People involved: [PEOPLE] Skill areas needed: [SKILLS] Deliverables: [DELIVERABLES] Dependencies: [DEPENDENCIES] Risks: [RISKS] Current project plan: [CURRENT PLAN] Create the workstream plan: 1. Workstream identification Identify the natural workstreams, such as: - strategy - research - design - production - operations - content - technical - communication - sales or launch - quality assurance - reporting - documentation Only include workstreams that fit my project. 2. Workstream definition For each workstream provide: - purpose - owner - outputs - tasks - dependencies - timeline - quality standard - risks - check-in cadence - done definition 3. Cross-workstream dependencies Map: - what each workstream needs from others - handoff points - review points - shared decisions - timing conflicts 4. Coordination rhythm Create: - weekly project check-in - async update format - decision log - blocker escalation - progress review - handoff checklist 5. Progress tracker Create a workstream tracker with: - workstream - owner - status - percent complete - current task - blocker - next milestone - due date - confidence Rules: - Do not create workstreams just to sound organized. - Do not let parallel work hide dependencies. - Do not leave ownership vague. - Workstreams should make the project easier to coordinate and track. --------------------------------------------------------------------------------

#147Progress Dashboard Designer

PROJECT PLANNING & PROGRESS TRACKINGProject managers, founders, consultants, teams, solo operators, client projects, internal projects, and anyone who needs progress visibility.

Build a project dashboard that tracks milestones, tasks, blockers, scope, risks, confidence, deadlines, decisions, and next actions.

You are a project dashboard designer. Build a simple dashboard that shows the real state of this project at a glance. Project: [PROJECT] Context: Goal: [GOAL] Timeline: [TIMELINE] Milestones: [MILESTONES] Tasks: [TASKS] Stakeholders: [STAKEHOLDERS] Current status: [STATUS] Risks: [RISKS] Blockers: [BLOCKERS] Tools available: [TOOLS] Who will read the dashboard: [AUDIENCE] Design the dashboard: A. Dashboard purpose Define what the dashboard must answer: - are we on track? - what is done? - what is next? - what is blocked? - what decisions are needed? - what risks are rising? - what changed since last update? - what needs attention now? B. Core sections Create dashboard sections for: - project summary - milestone status - task progress - blocker list - dependency list - risk log - decision log - scope changes - next actions - confidence rating C. Status logic Define status labels: - not started - on track - at risk - blocked - delayed - complete - paused For each label include: - definition - when to use it - required action D. Update cadence Create rules for: - daily update - weekly update - milestone update - stakeholder update - emergency update E. Dashboard template Output a copyable dashboard template. Rules: - Do not track metrics that do not change decisions. - Do not hide risk behind positive wording. - Do not make the dashboard harder to maintain than the project. - The dashboard should reveal the truth quickly. --------------------------------------------------------------------------------

#148Project Timeline Reality Check

PROJECT PLANNING & PROGRESS TRACKINGProjects with deadlines, launch plans, client commitments, internal initiatives, roadmap planning, and deadline negotiation.

Test whether a project timeline is realistic by checking task effort, dependencies, review cycles, buffers, risk, capacity, and hidden work.

Act as a timeline reality checker. Review my project timeline and tell me whether it is realistic. Project: [PROJECT] Proposed timeline: [TIMELINE] Context: Deadline: [DEADLINE] Milestones: [MILESTONES] Task list: [TASKS] Available capacity: [CAPACITY] People involved: [PEOPLE] Dependencies: [DEPENDENCIES] Review or approval cycles: [REVIEWS] Known risks: [RISKS] Quality standard: [QUALITY] Past estimation issues: [PAST ISSUES] Check the timeline: 1. Hidden work scan Find missing time for: - planning - research - setup - coordination - approvals - feedback - revisions - testing - handoff - documentation - communication - buffer - cleanup 2. Effort estimate For each milestone estimate: - optimistic duration - realistic duration - pessimistic duration - confidence level - reason for uncertainty 3. Capacity check Compare: - required work hours - available work hours - meeting load - other obligations - energy demand - overload gap 4. Critical risk points Identify: - tightest deadlines - most fragile dependencies - highest rework risk - likely approval delays - tasks that cannot overlap - tasks that can overlap 5. Revised timeline Create: - realistic timeline - compressed timeline - safe timeline - tradeoffs needed for each - communication script for deadline adjustment Rules: - Do not validate an unrealistic timeline to be polite. - Do not ignore review cycles. - Do not assume perfect capacity. - The result should make timeline risk visible before the project fails. --------------------------------------------------------------------------------

#149Project Risk Register Builder

PROJECT PLANNING & PROGRESS TRACKINGHigh-stakes projects, team work, launches, client delivery, operational projects, product work, and projects with uncertainty.

Identify, score, and manage project risks across timeline, scope, quality, resources, stakeholders, dependencies, execution, and communication.

You are a project risk manager. Build a practical risk register for this project and recommend mitigation actions. Project: [PROJECT] Context: Goal: [GOAL] Timeline: [TIMELINE] Scope: [SCOPE] People involved: [PEOPLE] Dependencies: [DEPENDENCIES] Budget or resources: [RESOURCES] Quality expectations: [QUALITY] Stakeholders: [STAKEHOLDERS] Known concerns: [CONCERNS] Past similar failures: [PAST FAILURES] Build the risk register: A. Risk discovery Identify risks across: - timeline - scope - quality - capacity - budget - stakeholder alignment - communication - technical feasibility - data or information - approvals - vendor or external partner - adoption or usage - handoff - maintenance B. Risk scoring For each risk provide: - risk description - probability from 1 to 5 - impact from 1 to 5 - risk score - early warning sign - owner - mitigation action - contingency plan - review date C. Top risks Identify: - top 5 risks by score - top 3 risks by urgency - top 3 risks that are easiest to reduce now - risk that could silently grow D. Mitigation plan Create: - immediate actions - preventive actions - monitoring actions - communication actions - escalation rules E. Risk review ritual Create a weekly risk review checklist. Rules: - Do not create vague risks like "project may fail." - Do not list risks without owners or actions. - Do not ignore low-probability high-impact risks. - The risk register should help prevent problems, not just document fear. --------------------------------------------------------------------------------

#150Scope-to-Task Conversion Engine

PROJECT PLANNING & PROGRESS TRACKINGMoving from planning to action, turning briefs into task boards, preparing project kickoff, and preventing vague project plans.

Convert project scope and deliverables into specific tasks, owners, deadlines, dependencies, done criteria, and execution order.

Act as a scope-to-task conversion engine. Turn this project scope into a clean execution task list. Project scope: [PASTE SCOPE / BRIEF / DELIVERABLES] Context: Final outcome: [OUTCOME] Deadline: [DEADLINE] People involved: [PEOPLE] Tools: [TOOLS] Known dependencies: [DEPENDENCIES] Quality standard: [QUALITY] Preferred task system: [TASK SYSTEM] Convert scope into tasks: 1. Deliverable extraction Identify all deliverables. For each deliverable include: - purpose - required components - acceptance criteria - owner - due date - dependency 2. Task generation For each deliverable create tasks across: - preparation - research - creation - review - revision - approval - delivery - documentation - follow-up 3. Task formatting Write each task as: Verb + object + output + context For each task include: - task name - project area - owner - effort estimate - deadline - dependency - priority - done definition 4. Execution order Sequence tasks by: - dependency - urgency - effort - risk - milestone - owner availability 5. Task board output Create task board sections: - backlog - ready - in progress - waiting - review - done Rules: - Do not leave deliverables as tasks. - Do not create tasks without clear done criteria. - Do not ignore review and approval tasks. - The output should be ready to paste into a task manager. --------------------------------------------------------------------------------

#151Weekly Project Progress Review

PROJECT PLANNING & PROGRESS TRACKINGOngoing projects, team updates, client reports, solo project reviews, leadership summaries, and keeping projects from drifting.

Run a weekly review that shows what moved, what stalled, what changed, what is blocked, and what must happen next.

You are a weekly project progress review facilitator. Help me review this project honestly and decide the next actions. Project: [PROJECT] This week's data: Completed work: [COMPLETED] Planned work: [PLANNED] Unfinished work: [UNFINISHED] New issues: [ISSUES] Blockers: [BLOCKERS] Decisions made: [DECISIONS] Decisions needed: [DECISIONS NEEDED] Scope changes: [SCOPE CHANGES] Stakeholder feedback: [FEEDBACK] Next deadline: [DEADLINE] Run the review: A. Progress summary Summarize: - what moved forward - what did not move - what changed - what became clearer - what became riskier B. Plan vs actual Compare: - planned tasks - completed tasks - delayed tasks - added tasks - removed tasks - reasons for variance C. Blocker analysis For each blocker identify: - owner - root cause - impact - deadline risk - next action - escalation need D. Next week plan Create: - top 3 outcomes - must-complete tasks - follow-ups - decisions to force - risks to monitor - scope items to protect E. Update message Write a short progress update for stakeholders with: - status - progress - risks - asks - next steps Rules: - Do not turn the review into a task dump. - Do not hide delayed work. - Do not roll over tasks without understanding why. - The review should create decisions and movement. --------------------------------------------------------------------------------

#152Project Status Report Generator

PROJECT PLANNING & PROGRESS TRACKINGClient updates, leadership reports, internal project communication, weekly summaries, async updates, and decision-making meetings.

Create clear project status reports for stakeholders with progress, risks, blockers, decisions, next steps, and confidence level.

Act as a project status report writer. Turn my project data into a clear, honest, useful status update. Project: [PROJECT] Status data: Goal: [GOAL] Current status: [STATUS] Completed since last update: [COMPLETED] Current work: [CURRENT WORK] Upcoming milestones: [MILESTONES] Blockers: [BLOCKERS] Risks: [RISKS] Decisions needed: [DECISIONS] Scope changes: [SCOPE CHANGES] Timeline changes: [TIMELINE CHANGES] Budget or resource issues: [RESOURCES] Asks from stakeholders: [ASKS] Audience: [AUDIENCE] Preferred tone: [TONE] Create the report: 1. Executive summary Write 3 to 5 lines covering: - overall status - key progress - major concern - next milestone - ask or decision needed 2. Status table Include: - area - status - update - risk - next action - owner 3. Progress since last update List: - completed - partially completed - delayed - changed - learned 4. Risks and blockers For each include: - issue - impact - owner - mitigation - decision needed - date needed 5. Next steps Create: - next 7 days - next milestone - stakeholder ask - confidence level 6. Versions Write three versions: - short Slack-style update - formal email update - leadership summary Rules: - Do not exaggerate progress. - Do not bury risks at the bottom. - Do not include unnecessary details for the audience. - The update should help stakeholders make decisions. --------------------------------------------------------------------------------

#153Project Momentum Rescue

PROJECT PLANNING & PROGRESS TRACKINGStalled projects, abandoned goals, delayed initiatives, blocked creative work, team drift, and projects that keep rolling over.

Diagnose why a project has stalled and create a restart plan with smaller actions, decisions, accountability, scope control, and momentum milestones.

You are a project momentum rescue specialist. Help me restart a project that has stalled. Stalled project: [PROJECT] Context: Original goal: [GOAL] Current status: [STATUS] How long it has been stalled: [TIME STALLED] Why it stalled: [KNOWN REASONS] Tasks left: [TASKS LEFT] Blockers: [BLOCKERS] People involved: [PEOPLE] Deadline pressure: [DEADLINE] Emotional resistance: [RESISTANCE] Scope concerns: [SCOPE] What still matters: [WHY IT STILL MATTERS] Rescue the project: 1. Stall diagnosis Classify the stall causes: - unclear next action - project too large - scope creep - missing decision - missing owner - weak deadline - dependency blocked - low energy - emotional resistance - loss of relevance - no progress tracking - perfectionism 2. Project truth check Answer: - is the project still worth doing? - should it be completed, reduced, paused, delegated, or deleted? - what is the minimum useful version? - what has changed since the project started? 3. Restart path Create: - 15-minute restart action - 60-minute restart action - first milestone - first decision - first communication - first visible output 4. Momentum plan Create a 10-day restart plan: - daily action - output - time box - progress signal - blocker to watch 5. Prevention rules Create rules to keep the project from stalling again. Rules: - Do not assume the project should continue unchanged. - Do not restart with a huge task. - Do not ignore emotional resistance or lost relevance. - The project should become easier to move within 24 hours. --------------------------------------------------------------------------------

#154Decision Log and Change Control System

PROJECT PLANNING & PROGRESS TRACKINGTeam projects, client work, product development, operations, strategy, complex planning, and projects with many stakeholder decisions.

Track decisions, changes, assumptions, approvals, reversals, and rationale so projects do not lose context or repeat debates.

Act as a decision log and change control architect. Build a system for tracking project decisions and scope changes clearly. Project: [PROJECT] Context: Stakeholders: [STAKEHOLDERS] Types of decisions expected: [DECISIONS] Types of changes expected: [CHANGES] Approval process: [APPROVALS] Current confusion: [CONFUSION] Tools: [TOOLS] Risk of undocumented changes: [RISKS] Create the system: A. Decision log structure Design fields for: - decision - date - owner - stakeholders consulted - options considered - rationale - expected impact - assumptions - related milestone - review date - status B. Change request structure Design fields for: - requested change - requester - reason - value - effort - timeline impact - budget impact - scope impact - risk - approval status - tradeoff required C. Decision rules Create rules for: - what needs to be logged - who can approve decisions - when to reopen a decision - when not to reopen a decision - how to communicate a decision - how to archive old decisions D. Change control flow Create the flow: - request - clarify - estimate impact - approve / reject / defer - update plan - notify stakeholders - log decision E. Templates Create: - decision log template - change request template - decision summary message - rejected change message - approved change message Rules: - Do not let major changes happen verbally only. - Do not reopen decisions without new evidence. - Do not approve changes without tradeoff visibility. - The system should preserve project memory. --------------------------------------------------------------------------------

#155Project Communication Cadence Planner

PROJECT PLANNING & PROGRESS TRACKINGTeam projects, client projects, cross-functional work, remote collaboration, leadership reporting, and projects where communication affects progress.

Design the communication rhythm for a project, including updates, meetings, async check-ins, stakeholder reports, escalation paths, and feedback loops.

You are a project communication planner. Create a communication cadence that keeps everyone aligned without creating meeting overload. Project: [PROJECT] Context: Stakeholders: [STAKEHOLDERS] Team members: [TEAM] Client or leadership audience: [AUDIENCE] Timeline: [TIMELINE] Current communication channels: [CHANNELS] Current communication problems: [PROBLEMS] Decision speed needed: [DECISION SPEED] Risk level: [RISK LEVEL] Preferred meeting load: [MEETING LOAD] Plan communication: 1. Stakeholder map For each stakeholder group identify: - what they need to know - how often they need updates - what decisions they own - what format they prefer - what risks they care about - what not to bother them with 2. Cadence design Create: - daily async check-in, if needed - weekly project update - milestone review - risk review - decision meeting - stakeholder report - escalation channel - closing report 3. Meeting rules Define: - which meetings are needed - agenda - owner - attendees - duration - input required - output expected - cancellation rule 4. Async update templates Create templates for: - daily update - weekly update - blocker update - milestone completion - risk escalation - decision request 5. Communication health checks Create rules to detect: - overcommunication - undercommunication - unclear ownership - slow decisions - stakeholder surprise - hidden blockers Rules: - Do not create meetings without decisions or outputs. - Do not send every detail to every stakeholder. - Do not allow blockers to wait for the next scheduled update. - Communication should keep work moving. --------------------------------------------------------------------------------

#156Project Capacity and Resource Planner

PROJECT PLANNING & PROGRESS TRACKINGProjects with limited resources, solo operators, small teams, overloaded teams, deadline planning, and workload negotiation.

Match project work to available time, energy, people, tools, budget, and attention so the plan reflects real capacity.

Act as a project capacity planner. Check whether this project can realistically be completed with the available resources. Project: [PROJECT] Context: Required work: [REQUIRED WORK] Deadline: [DEADLINE] People available: [PEOPLE] Hours available: [HOURS] Skills available: [SKILLS] Budget: [BUDGET] Tools: [TOOLS] Other commitments: [OTHER COMMITMENTS] Energy or focus constraints: [ENERGY] Quality expectations: [QUALITY] Current resource concerns: [CONCERNS] Analyze capacity: A. Work demand estimate Estimate demand across: - planning - research - production - coordination - review - revisions - approvals - communication - documentation - launch or delivery - stabilization B. Resource inventory List available: - people - hours - skills - tools - budget - decision-makers - support - external resources C. Capacity gap Compare: - required capacity - available capacity - skill gaps - time gaps - attention gaps - decision gaps - budget gaps D. Resource strategy Recommend: - reduce scope - extend timeline - add support - delegate - automate - outsource - simplify deliverables - change quality level - sequence differently E. Final capacity plan Create: - realistic project plan - reduced-scope plan - accelerated plan - resource requests - tradeoff explanation Rules: - Do not assume people have 100% availability. - Do not ignore coordination and review time. - Do not hide capacity gaps. - The plan should make tradeoffs explicit. --------------------------------------------------------------------------------

#157Progress Tracking Metrics Selector

PROJECT PLANNING & PROGRESS TRACKINGProject dashboards, team reporting, milestone tracking, personal goals, product projects, operations, and leadership updates.

Choose the right progress metrics for a project so tracking reflects real movement instead of vanity activity.

You are a progress measurement strategist. Help me choose the right metrics to track project progress accurately. Project: [PROJECT] Context: Goal: [GOAL] Deliverables: [DELIVERABLES] Timeline: [TIMELINE] Milestones: [MILESTONES] Stakeholders: [STAKEHOLDERS] Current metrics: [CURRENT METRICS] What progress currently means: [PROGRESS DEFINITION] Risks: [RISKS] Audience for reporting: [AUDIENCE] Select metrics: 1. Progress dimensions Identify what should be measured across: - milestone completion - task completion - output quality - timeline health - blocker count - decision speed - scope stability - stakeholder approval - budget or resource use - risk level - confidence - impact after delivery 2. Metric candidates For each metric provide: - name - definition - why it matters - how to measure it - update frequency - owner - healthy range - warning sign - action if warning appears 3. Vanity metric filter Identify metrics to avoid because they: - look good but do not show progress - reward busywork - hide risk - are hard to measure - do not inform decisions 4. Dashboard metric set Recommend: - 3 core metrics - 3 supporting metrics - 3 risk metrics - 1 confidence metric 5. Review process Create a metric review ritual: - what to check weekly - what to report monthly - when to change metrics - how to interpret conflicting signals Rules: - Do not track everything. - Do not measure effort as progress unless output is unclear. - Do not ignore quality and risk. - Metrics should help people make decisions and act. --------------------------------------------------------------------------------

#158Project Completion and Handoff Checklist

PROJECT PLANNING & PROGRESS TRACKINGClient delivery, internal projects, launches, operations, content projects, product work, and projects that often end messily.

Define what must happen at the end of a project so deliverables are finished, approved, documented, communicated, handed off, and archived properly.

Act as a project completion and handoff specialist. Build a closing system that ensures this project ends cleanly. Project: [PROJECT] Context: Final deliverables: [DELIVERABLES] Stakeholders: [STAKEHOLDERS] Approval process: [APPROVAL] Documentation needed: [DOCUMENTATION] Handoff owner: [OWNER] Users or recipients: [USERS] Quality standard: [QUALITY] Post-delivery support: [SUPPORT] Known loose ends: [LOOSE ENDS] Build the completion system: A. Done definition Define: - final output - required approvals - quality checks - documentation - communication - ownership transfer - archive requirements - post-project support B. Final checklist Create checklist sections: - deliverables - quality review - stakeholder approval - documentation - file organization - access and permissions - communication - training or handoff - open issues - support period - archive C. Handoff packet Create a handoff packet with: - project summary - final deliverables - how to use them - owner - maintenance needs - known limitations - open risks - next recommended actions D. Closing communication Write messages for: - internal completion update - client or stakeholder delivery - handoff confirmation - open issue disclosure - project closeout note E. Post-project review Create a short retrospective: - what worked - what failed - what changed - what to improve - what to reuse - what to document Rules: - Do not call a project complete before handoff is clear. - Do not leave ownership ambiguous. - Do not skip documentation if future use depends on it. - Completion should reduce future confusion. --------------------------------------------------------------------------------

#159Project Delay Recovery Plan

PROJECT PLANNING & PROGRESS TRACKINGLate projects, delayed milestones, client or leadership updates, team recovery, timeline renegotiation, and crisis stabilization.

Create a practical recovery plan when a project is late, behind schedule, blocked, over scope, or at risk of missing the deadline.

You are a project delay recovery advisor. Help me recover a delayed project and communicate the situation clearly. Delayed project: [PROJECT] Context: Original deadline: [ORIGINAL DEADLINE] Current status: [STATUS] What is late: [LATE ITEMS] Why it is late: [REASONS] Tasks remaining: [REMAINING TASKS] Blockers: [BLOCKERS] Stakeholders affected: [STAKEHOLDERS] Quality risks: [QUALITY RISKS] Scope changes: [SCOPE CHANGES] Available capacity: [CAPACITY] New target deadline, if any: [NEW DEADLINE] Create recovery plan: 1. Delay diagnosis Classify the delay cause: - underestimated work - missing dependency - unclear ownership - scope creep - approval delay - resource shortage - rework - decision delay - quality issue - communication breakdown 2. Impact assessment Identify: - timeline impact - stakeholder impact - quality impact - budget or resource impact - risk of further delay - trust impact 3. Recovery options Create 3 options: - protect scope and extend deadline - protect deadline and reduce scope - add resources and maintain scope - hybrid option, if needed For each include: - tradeoffs - risks - required decisions - likely outcome 4. Recovery schedule Create: - next 24 hours - next 3 days - next 7 days - revised milestones - blocker removal plan 5. Communication plan Write: - transparent stakeholder update - internal team reset message - deadline renegotiation message - decision request message Rules: - Do not hide the delay. - Do not promise a new deadline without capacity check. - Do not sacrifice quality silently. - Recovery should make tradeoffs visible and restore confidence. --------------------------------------------------------------------------------

#160Full Project Planning and Progress Tracking Audit

PROJECT PLANNING & PROGRESS TRACKINGFull project resets, complex initiatives, team projects, client work, launches, operational improvements, solo projects, and projects that need reliable movement from idea to completion.

Audit and redesign a complete project system across goals, scope, milestones, tasks, dependencies, risks, timeline, communication, tracking, reporting, and completion.

Act as an independent project planning and progress tracking auditor. Review my project system and redesign it so the project can move from idea to completion with clear scope, visible progress, and fewer delays. Full context: Project name: [PROJECT NAME] Project goal: [GOAL] Current status: [STATUS] Deadline: [DEADLINE] Current scope: [SCOPE] Deliverables: [DELIVERABLES] Milestones: [MILESTONES] Task list: [TASKS] Timeline: [TIMELINE] People involved: [PEOPLE] Stakeholders: [STAKEHOLDERS] Dependencies: [DEPENDENCIES] Blockers: [BLOCKERS] Risks: [RISKS] Budget or resources: [RESOURCES] Current tracking method: [TRACKING METHOD] Current communication cadence: [COMMUNICATION] Where progress stalls: [STALL POINTS] What success should look like: [SUCCESS] Audit across 30 dimensions: 1. Project goal clarity 2. Outcome definition 3. Scope clarity 4. Out-of-scope clarity 5. Deliverable definition 6. Milestone quality 7. Phase sequencing 8. Task breakdown 9. Task ownership 10. Done definitions 11. Dependency visibility 12. Critical path clarity 13. Timeline realism 14. Capacity realism 15. Resource fit 16. Risk visibility 17. Blocker management 18. Decision logging 19. Change control 20. Stakeholder alignment 21. Communication cadence 22. Progress metrics 23. Dashboard quality 24. Weekly review process 25. Reporting clarity 26. Scope creep control 27. Delay recovery readiness 28. Handoff planning 29. Retrospective process 30. System usability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason this project may stall, drift, or miss its deadline. B. Project system redesign Create: - revised project brief - scope definition - milestone roadmap - phase plan - task breakdown - dependency map - risk register - decision log - change control process - progress dashboard - communication cadence - weekly review ritual - delay recovery rules - completion and handoff checklist C. Timeline and capacity reality Estimate: - likely timeline risk - capacity gap - dependency risk - scope risk - review cycle risk - most important tradeoff D. Implementation plan Create: - first 24-hour cleanup - first 7-day project reset - first 30-day tracking plan - weekly review structure - stakeholder update plan - what to stop immediately - what to protect first E. Executive summary Write a direct summary with: - most unclear part of the project - highest-risk dependency - weakest milestone - most important next decision - first task to complete - first stakeholder update to send - first tracking metric to add - rule to use when the project starts drifting Rules: - Do not recommend a complex system if a simple one will work. - Do not hide uncertainty. - Do not leave vague tasks or owners. - Use [LOW CONFIDENCE] where information is missing. - The final system should make project progress visible, honest, and easier to sustain. -------------------------------------------------------------------------------- WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENT

#161Workflow Reality Map

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTAny repeated process that feels confusing, slow, undocumented, inconsistent, or dependent on memory.

Turn a messy recurring workflow into a clear visual-style map with steps, owners, inputs, outputs, tools, delays, and improvement opportunities.

You are a workflow mapping specialist. Help me map the real workflow as it actually happens, not how it is supposed to happen. Workflow to map: [WORKFLOW NAME / DESCRIPTION] Context: Purpose of the workflow: [PURPOSE] Who starts it: [STARTER] Who is involved: [PEOPLE / ROLES] How often it happens: [FREQUENCY] Current tools: [TOOLS] Current documentation: [DOCUMENTATION] Known problems: [PROBLEMS] Where delays happen: [DELAYS] Where mistakes happen: [MISTAKES] Desired outcome: [DESIRED OUTCOME] Create the workflow map: 1. Current-state flow Map the workflow step by step. For each step include: - step number - action - owner - input needed - tool used - output produced - estimated time - waiting time - failure risk - handoff point 2. Reality gaps Identify where the workflow differs from the ideal process: - undocumented steps - hidden decisions - informal approvals - repeated questions - unclear ownership - duplicate work - manual workarounds - unnecessary status checks - missing quality checks 3. Friction labels Label each step as: - value-creating - necessary but non-value-creating - avoidable waste - approval delay - rework risk - handoff risk - automation candidate - documentation candidate 4. Workflow pain summary Summarize: - slowest step - most confusing step - most fragile handoff - most repeated mistake - most unnecessary step - easiest improvement - highest-impact improvement 5. Improved workflow draft Create a cleaner version of the workflow with: - fewer steps - clearer owners - better handoffs - better quality checks - fewer delays - stronger documentation Rules: - Do not assume the documented workflow is the real workflow. - Do not skip informal steps if they affect outcomes. - Do not recommend automation before understanding the process. - The final map should make the workflow easier to explain, improve, and delegate. --------------------------------------------------------------------------------

#162Bottleneck Finder and Fix Planner

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTSlow processes, queues, delayed approvals, overloaded team members, stuck projects, service workflows, content operations, and internal operations.

Identify the exact bottlenecks slowing a workflow and create practical fixes for throughput, waiting time, decision delays, capacity constraints, and repeated blockers.

Act as a bottleneck analyst. Find what is slowing this workflow down and design a realistic fix plan. Workflow: [WORKFLOW] Current symptoms: [SYMPTOMS] Context: Average volume: [VOLUME] Current cycle time: [CYCLE TIME] Desired cycle time: [DESIRED CYCLE TIME] People involved: [PEOPLE] Tools used: [TOOLS] Steps in the process: [STEPS] Known waiting points: [WAITING POINTS] Approval requirements: [APPROVALS] Capacity limits: [LIMITS] Business impact of delay: [IMPACT] Analyze bottlenecks: A. Bottleneck candidates List every possible bottleneck across: - people capacity - approval delay - unclear requirements - missing input - too many handoffs - tool limitations - decision bottlenecks - rework loops - quality issues - batching delays - prioritization conflicts B. Bottleneck evidence For each candidate provide: - symptom - likely root cause - evidence to look for - data needed - impact on cycle time - confidence level C. Primary bottleneck Identify the most likely primary bottleneck. Explain: - why it controls the workflow - what happens before it - what happens after it - what gets stuck there - what would improve if fixed D. Fix options Create 3 fix options: - low-effort quick fix - process redesign fix - capacity or resource fix For each include: - change required - expected impact - risk - owner - implementation effort - how to measure success E. 14-day bottleneck removal plan Create a day-by-day plan to test and reduce the bottleneck. Rules: - Do not confuse symptoms with bottlenecks. - Do not recommend adding people before checking process design. - Do not ignore waiting time. - The fix should improve flow, not just make one person work harder. --------------------------------------------------------------------------------

#163Rework Elimination System

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTTeams with frequent revisions, quality problems, client edits, unclear briefs, inconsistent output, duplicate effort, or repeated corrections.

Find why work gets redone, corrected, reopened, rejected, or clarified repeatedly, then design prevention checks that reduce rework.

You are a rework reduction expert. Help me identify why work is being redone and design a system to prevent avoidable rework. Process or work type: [PROCESS / WORK TYPE] Rework examples: [PASTE EXAMPLES] Context: Who creates the work: [CREATOR] Who reviews the work: [REVIEWER] Who approves the work: [APPROVER] Common correction types: [CORRECTIONS] Current brief or input quality: [INPUT QUALITY] Current quality checks: [CHECKS] Current tools: [TOOLS] Deadline pressure: [DEADLINES] Impact of rework: [IMPACT] Build the rework elimination system: 1. Rework pattern diagnosis Classify rework causes: - unclear initial requirements - missing examples - weak brief - wrong assumptions - poor handoff - no quality standard - late stakeholder feedback - inconsistent review criteria - tool or data errors - rushed execution - approval ambiguity - scope change disguised as correction 2. Rework source map For each rework example identify: - where the error entered - who could have detected it earlier - what information was missing - what check would have prevented it - what standard was unclear 3. Prevention gates Design quality gates before: - work starts - work is handed off - work is reviewed - work is approved - work is delivered Each gate should include: - checklist - owner - pass criteria - fail action - time required 4. Brief improvement Create a better input brief template with: - objective - required output - examples - constraints - acceptance criteria - stakeholder preferences - known risks - final approval owner 5. Rework metric Create a simple tracking system for: - rework frequency - rework cause - time lost - reviewer - prevention action - trend over time Rules: - Do not blame people before checking the process. - Do not add excessive review steps. - Do not allow vague quality standards. - The goal is to prevent rework earlier, not criticize it later. --------------------------------------------------------------------------------

#164Handoff Improvement Kit

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTCross-functional workflows, client delivery, operations, sales-to-service, content production, project transitions, onboarding, support, and approval workflows.

Improve handoffs between people, teams, tools, or stages so work does not get delayed, misunderstood, duplicated, or dropped.

Act as a handoff design consultant. Redesign this handoff so work moves cleanly from one person or stage to the next. Handoff to improve: [HANDOFF] Context: Person or team handing off: [SENDER] Person or team receiving: [RECEIVER] What is handed off: [WORK / ASSET / INFORMATION] Current format: [FORMAT] Current tools: [TOOLS] Current timing: [TIMING] Common misunderstandings: [MISUNDERSTANDINGS] Common missing items: [MISSING ITEMS] Impact of poor handoff: [IMPACT] Design the handoff: A. Handoff anatomy Clarify: - what must be transferred - why it matters - when it must happen - who owns sending - who owns receiving - what receiver must do next - what confirms successful handoff B. Missing information scan Identify what receivers often need but do not get: - context - objective - deadline - files - decisions made - open questions - risks - dependencies - approval status - next action - quality expectations C. Handoff checklist Create a checklist with: - required information - required files - required links - required decisions - known risks - owner confirmation - receiver confirmation D. Handoff template Write a copyable handoff message: - summary - status - what is included - what is needed - decisions made - open questions - deadline - next action - contact point E. Handoff health system Create: - handoff success metric - missed-item tracker - feedback loop - escalation rule - weekly improvement review Rules: - Do not rely on verbal handoffs for important work. - Do not assume the receiver knows the context. - Do not create a handoff that is longer than the work requires. - A good handoff should make the next action obvious. --------------------------------------------------------------------------------

#165Checklist Builder for Repeatable Work

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTOperational tasks, admin work, content production, client delivery, QA, onboarding, reporting, publishing, procurement, and any repeated workflow.

Convert recurring work into a practical checklist that prevents missed steps, improves quality, speeds training, and reduces reliance on memory.

You are a checklist systems designer. Build a checklist that makes this recurring work easier, safer, and more consistent. Recurring work: [WORKFLOW / TASK] Context: Goal of the work: [GOAL] Who performs it: [OWNER] Frequency: [FREQUENCY] Current steps: [CURRENT STEPS] Common mistakes: [MISTAKES] Quality standard: [QUALITY] Tools used: [TOOLS] Inputs required: [INPUTS] Outputs required: [OUTPUTS] Review or approval needed: [REVIEW] Consequences of mistakes: [CONSEQUENCES] Create the checklist: 1. Checklist type Choose the right checklist style: - do-confirm checklist - read-do checklist - quality control checklist - handoff checklist - launch checklist - troubleshooting checklist - closing checklist Explain why. 2. Checklist structure Build sections for: - before starting - inputs ready - execution steps - quality checks - approval or review - handoff or delivery - documentation - cleanup - exception handling 3. Step writing Rewrite each step so it is: - specific - observable - action-based - in order - not overloaded - easy to verify 4. Failure prevention Add checks for the most common errors. For each error include: - warning sign - prevention step - correction step - owner 5. Final version Output: - short checklist - detailed checklist - manager review checklist - training notes - improvement log Rules: - Do not create vague checklist items like "make sure everything is good." - Do not include unnecessary steps. - Do not turn the checklist into a long manual. - The checklist should reduce errors without slowing the work too much. --------------------------------------------------------------------------------

#166SOP Simplification and Upgrade Prompt

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTOutdated SOPs, confusing instructions, long internal docs, onboarding materials, operational manuals, and recurring process documentation.

Improve an existing SOP by making it clearer, shorter, easier to follow, easier to train, and more useful in real execution.

Act as an SOP improvement editor. Rewrite and upgrade this SOP so someone can follow it correctly with less confusion. Existing SOP: [PASTE SOP] Context: Who uses this SOP: [USER] Skill level of user: [SKILL LEVEL] How often it is used: [FREQUENCY] Tools involved: [TOOLS] Common mistakes: [MISTAKES] Where people get confused: [CONFUSION] Required compliance or quality rules: [RULES] Desired tone: [TONE] Improve the SOP: A. SOP diagnosis Identify: - unclear steps - missing steps - duplicate steps - outdated instructions - ambiguous ownership - missing inputs - missing outputs - weak quality checks - unnecessary detail - missing exception handling B. Structural redesign Rebuild the SOP with: - purpose - when to use it - who owns it - required inputs - required tools - step-by-step instructions - quality checks - common mistakes - exceptions - escalation path - expected output - revision history C. Step rewrite Rewrite each step using: - action verb - specific object - tool or location - expected result - verification point D. Quick-use version Create: - one-page version - detailed version - new employee version - manager audit version E. Maintenance plan Recommend: - owner of SOP - review frequency - change log rules - feedback collection - retirement criteria Rules: - Do not make the SOP more complicated than the work. - Do not remove required compliance or quality steps. - Do not leave unclear ownership. - The final SOP should be usable during real work, not just readable. --------------------------------------------------------------------------------

#167Process Waste Removal Audit

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTTeams that feel busy but slow, processes with many steps, admin-heavy workflows, overloaded operations, and recurring work that feels heavier than necessary.

Identify wasted time, duplicate work, unnecessary approvals, waiting, overprocessing, manual copy-paste, unclear communication, and low-value steps.

You are a lean process improvement analyst. Audit this workflow for waste and remove unnecessary friction while protecting quality. Workflow: [WORKFLOW] Context: Purpose: [PURPOSE] Steps: [STEPS] People involved: [PEOPLE] Tools: [TOOLS] Time required: [TIME] Volume: [VOLUME] Common delays: [DELAYS] Common errors: [ERRORS] Quality requirements: [QUALITY] Constraints: [CONSTRAINTS] Audit for waste: 1. Waste categories Find waste across: - waiting - unnecessary movement between tools - duplicate data entry - overprocessing - unnecessary approvals - unclear requirements - rework - excessive meetings - status chasing - unused reports - manual copy-paste - task switching - unnecessary handoffs - searching for information 2. Waste table For each waste item include: - where it appears - who experiences it - root cause - time cost - quality risk - removal difficulty - recommended action 3. Keep / simplify / remove Classify every workflow step as: - keep as is - simplify - combine - automate - delegate - document - remove - move earlier - move later 4. Redesigned workflow Create a reduced-friction workflow with: - fewer steps - fewer handoffs - clearer inputs - faster decisions - better quality checks - less manual work 5. Implementation priority Rank improvements by: - impact - effort - risk - speed - owner Rules: - Do not remove quality controls that prevent serious mistakes. - Do not optimize one person by making the whole process worse. - Do not assume every approval is waste. - The goal is faster, cleaner flow with fewer low-value actions. --------------------------------------------------------------------------------

#168Process Automation Candidate Scanner

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTAI operations, no-code workflows, admin processes, reporting, content workflows, CRM tasks, data entry, notifications, and recurring coordination.

Find which workflow steps should be automated, templated, batched, delegated, or left manual based on risk, frequency, complexity, and value.

Act as an automation opportunity analyst. Review this workflow and identify what should and should not be automated. Workflow: [WORKFLOW] Context: Steps: [STEPS] Frequency: [FREQUENCY] Volume: [VOLUME] Tools used: [TOOLS] Manual repetitive work: [REPETITIVE WORK] Data involved: [DATA] Quality risks: [RISKS] Current errors: [ERRORS] People involved: [PEOPLE] Budget or tool limits: [LIMITS] Automation tools available: [AUTOMATION TOOLS] Scan for automation: A. Automation candidates Identify steps that are good candidates because they are: - repetitive - rule-based - high-volume - low-judgment - data-transfer heavy - notification-based - template-driven - status-update driven - reporting-based B. Do-not-automate list Identify steps that should remain human because they involve: - judgment - sensitive context - final approval - creative decisions - relationship management - compliance interpretation - edge cases - high consequence errors C. Automation scoring For each candidate score: - frequency - time saved - rule clarity - error reduction potential - setup effort - maintenance effort - risk - ROI D. Better-than-automation alternatives Recommend where to use: - template - checklist - batch processing - delegation - standard naming - form intake - saved replies - dashboard - SOP E. Automation roadmap Create: - quick automation wins - medium automation projects - advanced automation ideas - required data cleanup - QA checks - rollback plan Rules: - Do not automate a broken process without simplifying it first. - Do not automate unclear decisions. - Do not ignore maintenance cost. - The best recommendation may be template, batch, or SOP instead of automation. --------------------------------------------------------------------------------

#169Workflow Intake Form Designer

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTCreative requests, internal tickets, client work, marketing requests, design tasks, operations requests, support escalation, procurement, and project intake.

Create an intake form that collects the right information upfront so work starts faster, questions decrease, and rework is reduced.

You are an intake system designer. Build an intake form for this workflow so requests arrive complete, clear, and ready to process. Workflow or request type: [REQUEST TYPE] Context: Who submits requests: [REQUESTERS] Who processes requests: [PROCESSORS] Current request format: [CURRENT FORMAT] Common missing information: [MISSING INFO] Common clarifying questions: [QUESTIONS] Approval needed: [APPROVAL] Priority rules: [PRIORITY RULES] SLA or deadline expectations: [SLA] Tools used: [TOOLS] Bad request examples: [BAD EXAMPLES] Design the intake system: 1. Intake objective Define what the intake form must achieve: - clarify request - collect required inputs - set priority - confirm owner - confirm deadline - reduce back-and-forth - prevent out-of-scope work 2. Form sections Create sections for: - requester details - request type - objective - background context - required deliverable - audience or end user - deadline - priority - files and links - constraints - approval status - success criteria - risks or sensitivities 3. Field design For each field include: - question text - field type - required or optional - example answer - why it is needed - what happens if missing 4. Routing logic Create routing rules based on: - request type - urgency - complexity - department - approval status - required skill - capacity 5. Request quality control Create: - incomplete request response - acceptance confirmation - rejection or redirect response - priority clarification message - SLA expectation message Rules: - Do not make the form so long that people avoid it. - Do not ask questions that do not change execution. - Do not allow urgent requests to bypass all clarity. - The intake form should make work ready to start. --------------------------------------------------------------------------------

#170Review and Approval Process Redesign

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTCreative reviews, legal approvals, client approvals, leadership sign-off, content reviews, product decisions, finance approvals, and quality control.

Make reviews and approvals faster, clearer, less political, and less repetitive by defining criteria, owners, deadlines, feedback formats, and escalation rules.

Act as a review and approval process designer. Help me redesign this review process so decisions happen faster and feedback is more useful. Review process: [PROCESS] Context: What gets reviewed: [WORK] Reviewers: [REVIEWERS] Approvers: [APPROVERS] Current review steps: [STEPS] Current delays: [DELAYS] Common feedback issues: [FEEDBACK ISSUES] Number of review rounds: [ROUNDS] Deadline pressure: [DEADLINES] Quality or compliance needs: [QUALITY / COMPLIANCE] Tools used: [TOOLS] Redesign the process: A. Review purpose Clarify what the review is for: - quality - accuracy - compliance - brand consistency - strategic alignment - final approval - risk reduction - stakeholder buy-in B. Review role separation Separate roles: - contributor - reviewer - approver - decision-maker - informed stakeholder For each role define: - responsibility - decision rights - response time - feedback type allowed - escalation path C. Feedback format Create a feedback template with: - issue - severity - reason - requested change - example - must-have or suggestion - decision needed D. Approval rules Define: - what requires approval - what does not - approval deadline - silence rule - maximum review rounds - conflict resolution - final decision owner E. Improved workflow Create: - review checklist - approval checklist - timeline - meeting or async rules - escalation message - final approval record Rules: - Do not allow everyone to approve everything. - Do not treat opinions and requirements as equal. - Do not let feedback arrive without a deadline. - The process should reduce review loops and clarify decisions. --------------------------------------------------------------------------------

#171Queue and Prioritization System

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTSupport teams, operations teams, marketing requests, design queues, internal tickets, client requests, admin work, and overloaded teams.

Organize incoming work into a clear queue with priority rules, SLA expectations, capacity limits, escalation paths, and status visibility.

You are a queue management designer. Help me build a system for prioritizing and processing incoming work. Incoming work type: [WORK TYPE] Context: Request volume: [VOLUME] Current queue method: [CURRENT METHOD] People processing work: [PEOPLE] Capacity: [CAPACITY] Common request types: [REQUEST TYPES] Urgent request patterns: [URGENT REQUESTS] Current delays: [DELAYS] Stakeholders: [STAKEHOLDERS] Service expectations: [EXPECTATIONS] Tools: [TOOLS] Build the queue system: 1. Request categories Create categories for incoming work. For each category include: - description - examples - required intake fields - expected effort - owner - SLA target - escalation rule 2. Priority model Create priority levels: - critical - high - medium - low - backlog - not accepted For each priority include: - definition - criteria - response time - completion target - who can assign it 3. Queue rules Define rules for: - first-in-first-out - priority override - emergency handling - capacity limit - blocked request - incomplete request - aging request - duplicate request 4. Status system Create statuses: - received - needs clarification - ready - in progress - waiting - review - done - rejected - deferred For each include: - meaning - owner - next action 5. Visibility and reporting Create: - queue dashboard - weekly queue review - capacity report - overdue report - stakeholder update template Rules: - Do not let every request become urgent. - Do not accept incomplete work into active production. - Do not create priority rules that nobody can enforce. - The queue should protect capacity and improve trust. --------------------------------------------------------------------------------

#172Process QA Gate Designer

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTRecurring production, content, operations, reporting, customer service, fulfillment, finance checks, compliance-sensitive work, and handoffs.

Add quality assurance gates at the right points in a workflow so errors are caught early without slowing everything down.

Act as a process quality gate designer. Add practical QA checks to this workflow so mistakes are caught earlier and quality becomes more consistent. Workflow: [WORKFLOW] Context: Output produced: [OUTPUT] Current errors: [ERRORS] Quality standard: [QUALITY STANDARD] Risk if mistakes happen: [RISK] Current review process: [REVIEW] People involved: [PEOPLE] Tools used: [TOOLS] Deadline pressure: [DEADLINE] Compliance or brand requirements: [REQUIREMENTS] Design QA gates: GATE 1 — Input quality Check: - required information - files and links - decision status - deadline - constraints - acceptance criteria GATE 2 — Mid-process quality Check: - work matches request - assumptions are documented - major risks surfaced - format is correct - dependencies are not missing GATE 3 — Pre-handoff quality Check: - output is complete - naming is clear - instructions are included - next owner knows what to do - open questions are listed GATE 4 — Final delivery quality Check: - final approval - user or stakeholder requirements - error scan - documentation - archive or record update For each gate include: - owner - checklist - pass criteria - fail action - time required - evidence to save Then create: - QA checklist - error log - weekly quality review - improvement loop Rules: - Do not add QA steps everywhere. - Do not make QA purely subjective. - Do not catch errors only at the end. - QA should prevent rework without creating unnecessary delay. --------------------------------------------------------------------------------

#173Recurring Work Batch Optimizer

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTAdmin work, content creation, reporting, email, approvals, data entry, invoicing, scheduling, file cleanup, and routine operations.

Group repeated tasks into better batches to reduce context switching, setup time, decision fatigue, and scattered execution.

You are a batching and workload flow optimizer. Help me redesign recurring work so it is processed in efficient batches instead of scattered throughout the day or week. Recurring tasks: [PASTE TASKS] Context: Frequency of tasks: [FREQUENCY] Current schedule: [CURRENT SCHEDULE] Tools used: [TOOLS] People waiting on outputs: [PEOPLE] Deadlines or SLAs: [DEADLINES] Tasks that require focus: [FOCUS TASKS] Tasks that are low-energy: [LOW ENERGY TASKS] Tasks that interrupt other work: [INTERRUPTIONS] Current pain points: [PAIN POINTS] Optimize batching: 1. Task classification Classify tasks by: - tool - cognitive mode - urgency - energy requirement - owner - dependency - frequency - output type 2. Batch candidates Identify tasks that should be batched because they share: - same tool - same context - same reviewer - same input source - same output format - same energy level 3. Do-not-batch list Identify tasks that should not be batched because they are: - urgent - relationship-sensitive - high-risk - deadline-bound - blocking others - better handled immediately 4. Batch schedule Create: - daily batches - weekly batches - monthly batches - emergency exceptions - buffer windows For each batch include: - task types - duration - input needed - output produced - cutoff time - owner - quality check 5. Efficiency rules Create rules for: - batching communication - batching admin - batching review - batching planning - batching cleanup - avoiding overlarge batches Rules: - Do not batch work that will create harmful delays. - Do not make batches so large they become exhausting. - Do not ignore stakeholder expectations. - The batching system should reduce switching and protect flow. --------------------------------------------------------------------------------

#174Exception Handling Playbook

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTSupport, operations, fulfillment, client service, finance, HR, internal requests, compliance workflows, and any process where exceptions create chaos.

Create clear rules for what to do when a workflow does not follow the normal path: missing inputs, urgent requests, errors, escalations, edge cases, and special approvals.

Act as an exception handling playbook designer. Build a clear system for handling cases that do not fit the normal workflow. Workflow: [WORKFLOW] Normal process: [NORMAL PROCESS] Common exceptions: [EXCEPTIONS] Context: Who handles exceptions: [OWNER] Who approves exceptions: [APPROVER] Risks: [RISKS] Current confusion: [CONFUSION] Tools used: [TOOLS] Communication channels: [CHANNELS] Time sensitivity: [TIME SENSITIVITY] Compliance or policy rules: [RULES] Build the playbook: A. Exception categories Categorize exceptions into: - missing information - urgent request - scope exception - quality issue - customer or stakeholder escalation - approval exception - technical issue - capacity issue - policy exception - duplicate or conflicting request B. Decision tree Create a decision tree: - what happened? - is it urgent? - is it allowed? - who owns it? - what information is missing? - who approves? - what is the next action? - how is it documented? C. Response protocols For each exception type include: - first action - owner - communication template - escalation path - documentation required - resolution time - prevention note D. Exception log Create fields for: - date - exception type - cause - owner - action taken - time to resolve - impact - prevention opportunity E. Prevention loop Create a monthly review to decide: - which exceptions need better intake - which need SOP updates - which need automation - which need policy clarification - which are acceptable rare cases Rules: - Do not force every exception through the normal workflow. - Do not allow exceptions to become undocumented shortcuts. - Do not make every exception a leadership decision. - The playbook should reduce panic and preserve control. --------------------------------------------------------------------------------

#175Tool Stack and Process Fit Audit

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTTeams using too many apps, spreadsheets, chat, task tools, CRMs, shared drives, forms, dashboards, and manual workarounds.

Evaluate whether the tools used in a workflow support the process or create extra work, confusion, duplication, and fragmented information.

You are a tool stack and process fit auditor. Review the tools used in this workflow and identify where they help, hurt, duplicate, or fragment the process. Workflow: [WORKFLOW] Tools used: [TOOLS] Context: What each tool is used for: [TOOL USAGE] People using the tools: [PEOPLE] Current pain points: [PAIN POINTS] Duplicate data entry: [DUPLICATION] Reporting needs: [REPORTING] Handoff points: [HANDOFFS] Documentation needs: [DOCUMENTATION] Automation needs: [AUTOMATION] Constraints: [CONSTRAINTS] Audit tool fit: 1. Tool role map For each tool identify: - purpose - user - input - output - source of truth or not - workflow step supported - problems created - replacement risk 2. Fragmentation diagnosis Find where information is split across: - chat - email - spreadsheets - task boards - documents - dashboards - CRM - file storage - personal notes 3. Source-of-truth design Define: - where requests live - where tasks live - where files live - where decisions live - where status lives - where reports live - where documentation lives 4. Tool simplification options Recommend: - tool to keep - tool to remove - tool to consolidate - tool to integrate - tool to use differently - manual workaround to eliminate 5. Improved tool workflow Create the improved process with: - tool used at each step - required field or artifact - owner - update rule - handoff rule - reporting rule Rules: - Do not recommend a new tool unless process changes require it. - Do not remove a tool that is a required source of truth. - Do not confuse tool problems with process problems. - The goal is fewer places to check and cleaner workflow ownership. --------------------------------------------------------------------------------

#176Cycle Time Reduction Planner

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTService workflows, operations, content production, support, approvals, fulfillment, reporting, internal requests, and project delivery.

Reduce the time it takes for work to move from request to completion by analyzing active work time, waiting time, approvals, handoffs, batching, and rework.

Act as a cycle time reduction strategist. Help me reduce how long this workflow takes from start to finish. Workflow: [WORKFLOW] Current cycle time: [CYCLE TIME] Target cycle time: [TARGET] Context: Start trigger: [START] End point: [END] Steps: [STEPS] Active work time: [ACTIVE TIME] Waiting time: [WAITING TIME] Approvals: [APPROVALS] Handoffs: [HANDOFFS] Rework: [REWORK] Volume: [VOLUME] Capacity: [CAPACITY] Quality constraints: [QUALITY] Current delays: [DELAYS] Reduce cycle time: A. Cycle time breakdown Separate: - active work time - waiting time - review time - rework time - queue time - handoff time - decision time - communication time B. Delay root causes Identify the biggest drivers of delay: - unclear intake - queue backlog - unavailable owner - batch timing - approval wait - slow review - missing input - rework - tool switching - priority confusion C. Reduction levers Recommend changes to: - start work earlier - reduce waiting - reduce handoffs - improve intake - shorten reviews - parallelize safe steps - reduce rework - pre-approve low-risk items - create SLA rules - automate status updates D. Tradeoff analysis For each reduction option include: - expected time saved - quality risk - cost - owner - implementation difficulty - confidence E. New workflow target Create: - redesigned timeline - new SLA - tracking metric - pilot test - review date Rules: - Do not reduce cycle time by silently lowering quality. - Do not ignore waiting time. - Do not promise speed improvements without process changes. - The plan should identify the fastest safe path. --------------------------------------------------------------------------------

#177Process Training System Builder

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTOnboarding, operations teams, service delivery, admin processes, support teams, creative teams, and any workflow that depends on people learning repeatable steps.

Build a training system that helps new or existing team members learn a workflow faster, follow standards, avoid mistakes, and improve confidence.

You are a process training designer. Turn this workflow into a training system that helps someone perform it correctly. Workflow: [WORKFLOW] Context: Who needs training: [TRAINEE] Skill level: [SKILL LEVEL] Trainer or owner: [TRAINER] Current documentation: [DOCUMENTATION] Common beginner mistakes: [MISTAKES] Tools required: [TOOLS] Quality standard: [QUALITY] Practice opportunities: [PRACTICE] Time available for training: [TIME] Build the training system: 1. Learning outcomes Define what the trainee must be able to do: - understand purpose - identify inputs - follow steps - use tools - handle exceptions - meet quality standard - complete handoff - know when to escalate 2. Training sequence Create stages: - observe - explain - guided practice - independent practice - review - certification - ongoing improvement For each stage include: - activities - materials - trainer role - trainee output - pass criteria 3. Training materials Create: - quick-start guide - detailed SOP - checklist - example good output - example bad output - troubleshooting guide - FAQ 4. Practice plan Design practice tasks with: - scenario - expected output - common trap - feedback criteria - difficulty level 5. Competency check Create a simple assessment: - practical test - quality checklist - time expectation - error tolerance - sign-off criteria Rules: - Do not make training only a document. - Do not expect a new person to learn edge cases first. - Do not leave quality standards implicit. - Training should make performance repeatable, not personality-dependent. --------------------------------------------------------------------------------

#178Continuous Improvement Loop

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTTeams that want ongoing operational improvement instead of one-time cleanup, especially in recurring workflows.

Create a recurring process improvement system that captures problems, prioritizes fixes, tests changes, measures impact, and updates documentation.

Act as a continuous improvement systems designer. Build a lightweight loop for improving this workflow over time. Workflow: [WORKFLOW] Context: Current problems: [PROBLEMS] People involved: [PEOPLE] Process owner: [OWNER] Data available: [DATA] Improvement ideas: [IDEAS] Current review cadence: [CADENCE] Business impact: [IMPACT] Constraints: [CONSTRAINTS] Team culture: [CULTURE] Design the improvement loop: CYCLE 1 — Capture Create a way to collect: - process friction - errors - delays - repeated questions - workarounds - customer complaints - team suggestions - automation ideas - documentation gaps CYCLE 2 — Prioritize Create a scoring model using: - impact - frequency - effort - risk - time saved - quality improvement - customer or stakeholder value CYCLE 3 — Test Create an experiment format: - problem - hypothesis - change - owner - test duration - success metric - risk - rollback plan CYCLE 4 — Standardize When a change works, define how to: - update SOP - update checklist - train team - update tools - communicate change - retire old method CYCLE 5 — Review Create a monthly improvement review: - wins - failed experiments - metrics - next improvements - unresolved blockers - owner assignments Rules: - Do not make improvement work too heavy to maintain. - Do not collect ideas without acting on them. - Do not change the process without updating documentation. - Continuous improvement should become a habit, not a special project. --------------------------------------------------------------------------------

#179Process Metrics and Reporting Designer

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTOperations dashboards, team reporting, leadership updates, SLA tracking, quality control, service workflows, and process improvement programs.

Choose the right metrics for a workflow so process health, speed, quality, workload, delays, and improvement impact become visible.

You are a process measurement strategist. Help me design metrics and reporting for this workflow. Workflow: [WORKFLOW] Context: Purpose of workflow: [PURPOSE] Current goals: [GOALS] Current problems: [PROBLEMS] Volume: [VOLUME] Cycle time: [CYCLE TIME] Error rate: [ERROR RATE] People involved: [PEOPLE] Stakeholders: [STAKEHOLDERS] Current reporting: [REPORTING] Tools or data sources: [DATA SOURCES] Design the measurement system: 1. Process health questions Define what reporting should answer: - how much work came in? - how much was completed? - how fast did work move? - where did work wait? - how often did errors happen? - where did rework happen? - who or what was overloaded? - what improved? - what needs intervention? 2. Metric set Create metrics for: - volume - throughput - cycle time - lead time - waiting time - SLA compliance - rework rate - error rate - backlog size - blocker count - handoff quality - stakeholder satisfaction - automation success - improvement impact For each metric include: - definition - formula - data source - owner - update frequency - healthy range - warning range - action when warning appears 3. Dashboard design Create dashboard sections: - executive summary - workload - speed - quality - blockers - backlog - trend - improvement actions 4. Reporting cadence Define: - daily operational view - weekly team report - monthly leadership report - quarterly improvement review 5. Metric discipline Identify metrics to avoid because they encourage: - busywork - speed over quality - hiding blockers - unnecessary complexity - vanity reporting Rules: - Do not track metrics that do not change decisions. - Do not measure only speed. - Do not hide quality problems behind high throughput. - Reporting should help improve the process, not just describe it. --------------------------------------------------------------------------------

#180Full Workflow Optimization and Process Improvement Audit

WORKFLOW OPTIMIZATION & PROCESS IMPROVEMENTFull operations resets, recurring workflows, team processes, service delivery, internal systems, admin processes, production workflows, and any process that needs to become faster and cleaner.

Audit and redesign a complete workflow across steps, owners, bottlenecks, handoffs, tools, rework, quality checks, automation, documentation, metrics, and continuous improvement.

Act as an independent workflow optimization and process improvement auditor. Review my current workflow and redesign it so recurring work becomes faster, cleaner, easier to train, and more reliable. Full context: Workflow name: [WORKFLOW NAME] Purpose: [PURPOSE] Current steps: [STEPS] People or roles involved: [PEOPLE / ROLES] Workflow owner: [OWNER] Frequency: [FREQUENCY] Volume: [VOLUME] Inputs: [INPUTS] Outputs: [OUTPUTS] Tools used: [TOOLS] Current documentation: [DOCUMENTATION] Current cycle time: [CYCLE TIME] Desired cycle time: [DESIRED CYCLE TIME] Common delays: [DELAYS] Common errors: [ERRORS] Common rework: [REWORK] Handoffs: [HANDOFFS] Approvals: [APPROVALS] Known bottlenecks: [BOTTLENECKS] Quality requirements: [QUALITY REQUIREMENTS] Constraints: [CONSTRAINTS] What a better workflow should feel like: [DESIRED STATE] Audit across 30 dimensions: 1. Workflow purpose clarity 2. Step sequence 3. Input quality 4. Output clarity 5. Ownership clarity 6. Handoff quality 7. Approval efficiency 8. Bottleneck visibility 9. Waiting time 10. Cycle time 11. Rework frequency 12. Error prevention 13. Quality gates 14. Checklist quality 15. SOP quality 16. Tool fit 17. Source of truth 18. Duplicate work 19. Manual work 20. Automation opportunity 21. Queue management 22. Priority rules 23. Exception handling 24. Training readiness 25. Communication flow 26. Capacity fit 27. Metrics and reporting 28. Continuous improvement loop 29. Documentation maintenance 30. Overall workflow usability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason this workflow is slower, messier, or more fragile than it needs to be. B. Workflow redesign Create: - simplified workflow map - improved step sequence - owner map - input requirements - output standards - handoff checklist - QA gates - approval rules - exception handling playbook - SOP outline - checklist - tool usage rules - automation candidates - process metrics - continuous improvement loop C. Bottleneck and waste removal Identify: - primary bottleneck - top 5 waste sources - top 5 rework causes - top 5 handoff risks - top 5 tool or documentation issues - quickest process win - highest-impact process fix D. Implementation plan Create: - first 24-hour cleanup - first 7-day workflow improvement sprint - first 30-day process redesign plan - weekly process review - monthly improvement review - what to stop immediately - what to standardize first E. Executive summary Write a direct summary with: - most broken step - most important owner clarification - biggest bottleneck - easiest waste to remove - highest-value checklist to create - best automation candidate - first metric to track - first improvement to test this week Rules: - Do not recommend automation before simplifying the workflow. - Do not add complexity in the name of process improvement. - Do not remove quality controls without replacing risk protection. - Use [LOW CONFIDENCE] where information is missing. - The final system should make the workflow faster, cleaner, easier to teach, and easier to improve. -------------------------------------------------------------------------------- INFORMATION MANAGEMENT & DIGITAL ORGANIZATION

#181Digital Information Chaos Audit

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONPeople with too many apps, messy folders, lost notes, repeated searching, duplicated files, unclear systems, or digital clutter that blocks execution.

Diagnose where your notes, files, documents, bookmarks, ideas, tasks, and messages are scattered so you can rebuild a cleaner information system.

You are a digital information systems auditor. Help me audit my current information environment and identify why it feels messy, hard to search, or difficult to maintain. My context: Main tools I use: [TOOLS] Types of information I manage: [NOTES / FILES / DOCUMENTS / TASKS / BOOKMARKS / RESEARCH / IDEAS] Current note system: [NOTE SYSTEM] Current file system: [FILE SYSTEM] Current task system: [TASK SYSTEM] Current inboxes: [EMAIL / CHAT / APP INBOXES] Current bookmarks or saved resources: [BOOKMARKS] Where I usually lose information: [WHERE LOST] What I search for repeatedly: [REPEATED SEARCHES] What feels most chaotic: [CHAOS POINTS] What I want the system to feel like: [DESIRED STATE] Run the audit: 1. Information inventory Classify my information into: - active work - reference material - ideas - research - decisions - tasks - meeting notes - files and assets - templates - bookmarks - personal records - archived material For each category identify: - where it currently lives - where it should live - how often I use it - who needs access - search difficulty - cleanup priority 2. Chaos source diagnosis Identify the biggest problems across: - too many tools - no source of truth - poor naming - missing tags - unclear folders - mixed tasks and notes - old files - duplicate documents - no archive rules - no review routine - poor capture habits - weak searchability 3. Information flow map Map how information enters, moves, gets used, and gets stored. Use this structure: - capture point - temporary holding place - processing step - permanent location - action required - review cycle - archive rule 4. Fix priority ranking Rank fixes by: - impact - ease - urgency - time saved - risk reduction - maintenance effort 5. First cleanup plan Create: - first 30-minute cleanup - first 2-hour cleanup - first 7-day reset - first source-of-truth decision - first naming rule - first review habit Rules: - Do not recommend a complicated system. - Do not suggest changing tools unless the current tool setup is the problem. - Do not organize everything at once. - The output should make the mess understandable and the next cleanup action obvious. --------------------------------------------------------------------------------

#182File System Architecture Builder

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONCloud drives, local folders, business documents, client files, creative assets, personal admin, team folders, and messy file systems.

Create a clean folder, naming, tagging, and archive structure for files so documents are easy to find, share, update, and retire.

Act as a file system architect. Design a practical file organization structure for my work or personal files. File system context: Where files live now: [GOOGLE DRIVE / DROPBOX / LOCAL / NOTION / OTHER] Main file categories: [CATEGORIES] Who uses the files: [USERS] File types: [DOCS / SHEETS / PDFS / IMAGES / VIDEOS / PRESENTATIONS / CONTRACTS] Current folder structure: [CURRENT STRUCTURE] Current naming problems: [NAMING PROBLEMS] Duplicate file issues: [DUPLICATES] Access or sharing needs: [ACCESS NEEDS] Archive needs: [ARCHIVE NEEDS] Search problems: [SEARCH PROBLEMS] Design the file system: A. Folder architecture Create a folder structure with: - top-level folders - second-level folders - optional third-level folders - active work area - reference area - archive area - templates area - shared area - private area, if needed B. Naming convention Create naming rules for: - documents - spreadsheets - presentations - images - exports - contracts - project files - client files - versions - final files - archived files Use examples. C. Version control rules Define: - draft naming - review naming - final naming - approved naming - archived naming - when to duplicate - when not to duplicate - how to avoid "final_final_v3" D. Access and ownership Define: - who owns each folder - who can edit - who can view - who approves changes - where sensitive files go - how sharing links should be managed E. Migration plan Create a practical cleanup plan: - what to move first - what to rename first - what to archive - what to delete - what to leave for later - how to maintain the system weekly Rules: - Do not make the folder system deeper than necessary. - Do not create folders that will only contain one file. - Do not mix active and archived files in the same place. - The final structure should be easy to use without explanation. --------------------------------------------------------------------------------

#183Notes-to-Knowledge Base Converter

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONPeople with messy notes, meeting notes, research notes, course notes, client notes, personal learning notes, or half-finished thoughts.

Turn scattered notes into a structured knowledge base with categories, summaries, links, tags, action items, and reusable insights.

You are a knowledge base organizer. Convert my scattered notes into a useful, searchable, reusable knowledge system. Notes to organize: [PASTE NOTES] Context: Purpose of these notes: [PURPOSE] Where they came from: [SOURCE] How I want to reuse them: [REUSE] Audience: [JUST ME / TEAM / CLIENT / PUBLIC] Current tool: [TOOL] Preferred organization style: [FOLDERS / TAGS / DATABASE / WIKI] Important projects connected to these notes: [PROJECTS] Topics I care about: [TOPICS] Convert the notes: 1. Note sorting Separate the notes into: - concepts - facts - decisions - questions - action items - ideas - references - quotes - examples - frameworks - tasks - follow-ups 2. Knowledge base structure Create a structure with: - main categories - subcategories - page titles - suggested tags - related pages - source references - update frequency 3. Note rewriting For each useful note, create: - clean title - 3-line summary - key points - action items - related topic - reusable insight - where it should live 4. Connection map Identify links between notes: - repeated themes - related ideas - contradictions - dependencies - future research questions - project connections 5. Final output Create: - organized knowledge base outline - cleaned notes - action list - unanswered questions - archive list - next processing steps Rules: - Do not preserve messy notes just because they exist. - Do not turn every note into a separate page. - Do not mix tasks with permanent knowledge without labeling them. - The final system should make the information easier to reuse. --------------------------------------------------------------------------------

#184Inbox Triage and Processing System

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONOverloaded inboxes, unread emails, saved messages, Slack/Telegram chaos, task leakage, and people who use inboxes as memory.

Create a system for processing email, chat, app notifications, saved messages, and digital inboxes so information becomes action, reference, delegation, or archive.

Act as an inbox processing strategist. Build a triage system that helps me process incoming information quickly and reliably. Inboxes: [LIST INBOXES] Context: Current unread count: [UNREAD COUNT] Types of incoming messages: [MESSAGE TYPES] Important senders: [SENDERS] Common actions required: [ACTIONS] Current response expectations: [EXPECTATIONS] Where tasks should go: [TASK SYSTEM] Where reference info should go: [REFERENCE SYSTEM] What usually gets lost: [LOST ITEMS] Time available for processing: [TIME] Stress level caused by inboxes: [STRESS] Build the triage system: STEP 1 — Capture rules Define what belongs in each inbox and what should not. STEP 2 — Processing categories Sort every item into: - reply now - reply later - task - calendar - delegate - reference - waiting for - archive - delete - unsubscribe - escalate - ignore STEP 3 — Decision rules Create rules for: - urgent messages - non-urgent important messages - newsletters - receipts - requests - approvals - personal messages - unclear messages - spam or low-value messages STEP 4 — Processing cadence Create a schedule for: - quick daily scan - deep processing - weekly cleanup - monthly unsubscribe review - saved message review STEP 5 — Templates Write templates for: - delayed response - clarification request - delegation - declining request - moving to task system - confirming receipt - asking for deadline Rules: - Do not use the inbox as the final storage place for tasks. - Do not aim for inbox zero if it creates unnecessary pressure. - Do not process messages all day. - The system should turn incoming information into clear next actions or clean storage. --------------------------------------------------------------------------------

#185Bookmark and Resource Library Organizer

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONPeople with hundreds of saved links, messy browser bookmarks, read-it-later apps, research resources, tool lists, swipe files, and inspiration folders.

Organize bookmarks, saved articles, videos, tools, references, and useful links into a searchable library that supports learning and execution.

You are a resource library curator. Help me organize my saved links and bookmarks into a clean library I can actually use. Saved resources: [PASTE BOOKMARKS / LINKS / RESOURCE LIST] Context: Main topics: [TOPICS] Why I save resources: [WHY] Current storage location: [LOCATION] How often I use saved resources: [FREQUENCY] What I want to find quickly: [SEARCH NEEDS] Types of resources: [ARTICLES / VIDEOS / TOOLS / EXAMPLES / REFERENCES / COURSES] Current problems: [PROBLEMS] Preferred tool: [TOOL] Organize the library: A. Resource classification Classify each resource as: - reference - tutorial - inspiration - tool - example - template - research - idea source - swipe file - future reading - outdated - delete B. Library taxonomy Create categories and subcategories. For each category include: - purpose - what belongs there - what does not belong there - suggested tags - examples C. Resource card format Create a standard card for each resource: - title - link - category - tags - short summary - why saved - best use case - action required - review date D. Cleanup decisions Identify: - keep - read soon - process into notes - move to project - archive - delete - replace with better resource E. Maintenance system Create: - save rule - tagging rule - weekly review - monthly cleanup - stale resource rule - search naming rule Rules: - Do not create too many categories. - Do not keep links just because they once seemed useful. - Do not mix active research with long-term reference. - The library should help me find and use resources, not collect them endlessly. --------------------------------------------------------------------------------

#186Research Capture and Synthesis Workflow

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONMarket research, academic research, content research, product research, competitive analysis, learning projects, and deep topic exploration.

Create a workflow for capturing research, extracting useful insights, organizing sources, synthesizing themes, and turning research into decisions or content.

Act as a research organization specialist. Build a workflow that turns raw research into usable knowledge and decisions. Research topic: [TOPIC] Raw research: [PASTE SOURCES / NOTES / LINKS] Context: Research goal: [GOAL] Decision or output this supports: [OUTPUT] Audience: [AUDIENCE] Depth needed: [DEPTH] Source types: [SOURCE TYPES] Time available: [TIME] Current organization method: [METHOD] What I need to understand: [QUESTIONS] Design the research workflow: 1. Research question map Break the topic into: - core question - subquestions - assumptions to test - evidence needed - decision criteria - unknowns 2. Source intake For each source capture: - title - link or citation - source type - reliability level - key claim - supporting evidence - useful quote or data point - limitations - relevance score 3. Insight extraction Extract: - repeated themes - surprising findings - contradictions - strong evidence - weak evidence - open questions - practical implications 4. Synthesis structure Organize findings into: - executive summary - key insights - evidence table - implications - risks - recommendations - next research needed 5. Action conversion Turn research into: - decisions - content ideas - project tasks - knowledge base entries - stakeholder update - archive notes Rules: - Do not confuse saved sources with synthesized knowledge. - Do not treat all sources as equally reliable. - Do not leave research disconnected from a decision or output. - The final system should make research easier to reuse. --------------------------------------------------------------------------------

#187Document Naming and Version Control System

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONTeams, client work, contracts, reports, presentations, creative assets, proposals, policies, internal documents, and shared drives.

Create clear naming and version rules so documents, drafts, files, exports, reviews, approvals, and final versions do not become confusing.

You are a document control specialist. Build a naming and version control system for my documents and files. Document context: Document types: [DOCUMENT TYPES] Where documents live: [LOCATION] Who creates documents: [CREATORS] Who reviews documents: [REVIEWERS] Who approves documents: [APPROVERS] Current naming examples: [EXAMPLES] Current version problems: [PROBLEMS] Final approval process: [APPROVAL] Archive needs: [ARCHIVE] Compliance or audit needs: [COMPLIANCE] Create the system: A. Naming formula Design naming formulas for: - working drafts - review drafts - approved documents - final documents - archived documents - client-facing exports - internal-only documents - templates Use this format: [DATE]_[PROJECT]_[DOCUMENT TYPE]_[STATUS]_[VERSION]_[OWNER] Adapt if needed. B. Status labels Define labels: - DRAFT - REVIEW - REVISION - APPROVED - FINAL - ARCHIVED - TEMPLATE - DEPRECATED For each label include: - meaning - when to use it - who can change it - what happens next C. Version rules Define: - when to increment version - difference between v0.1 and v1.0 - when to create a copy - when to edit the same file - how to handle comments - how to mark final approval - how to retire old versions D. Folder placement rules Define where each version should live. E. Examples Create 20 example filenames for my context. Rules: - Do not create naming rules that are too long to use. - Do not allow "final_final" naming. - Do not keep outdated drafts beside approved files without labels. - The system should make the current version obvious. --------------------------------------------------------------------------------

#188Idea Capture-to-Action Pipeline

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONCreators, founders, writers, marketers, product people, students, entrepreneurs, and anyone with many ideas but poor follow-through.

Turn random ideas, notes, voice memos, screenshots, and quick thoughts into a pipeline that filters, organizes, develops, schedules, or archives them.

Act as an idea pipeline designer. Build a system that captures ideas quickly and turns the best ones into action without overwhelming me. Idea sources: [IDEA SOURCES] Current idea list: [PASTE IDEAS] Context: Types of ideas I capture: [TYPES] Where ideas currently live: [LOCATIONS] How often I review them: [REVIEW FREQUENCY] What ideas should become: [CONTENT / PROJECTS / TASKS / PRODUCTS / RESEARCH] Current problem: [PROBLEM] Selection criteria: [CRITERIA] Time available for processing: [TIME] Build the pipeline: CAPTURE Create rules for: - quick capture - voice notes - screenshots - links - physical notes - chat messages - mobile capture - no-organization capture CLARIFY For each idea, ask: - what is the idea? - why does it matter? - what category is it? - what outcome could it support? - what is the next step? - is it actionable now? FILTER Sort ideas into: - act now - develop later - research - combine with another idea - save as reference - archive - delete DEVELOP Create a development template: - title - one-line concept - audience - use case - supporting notes - first action - related ideas SCHEDULE OR STORE Create rules for: - moving idea to task system - adding idea to content calendar - adding idea to project backlog - storing as reference - reviewing later Rules: - Do not force organization during capture. - Do not turn every idea into a task. - Do not keep weak ideas forever. - The pipeline should protect creativity while improving execution. --------------------------------------------------------------------------------

#189Knowledge Base Taxonomy Designer

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONNotion, Obsidian, Confluence, Google Drive, internal wikis, personal knowledge management, team documentation, and research libraries.

Design categories, tags, relationships, and page types for a knowledge base so information is easy to file, search, connect, and update.

You are a taxonomy and knowledge architecture designer. Create a clean information structure for my knowledge base. Knowledge base context: Purpose: [PURPOSE] Users: [USERS] Main topics: [TOPICS] Types of content: [CONTENT TYPES] Current structure: [CURRENT STRUCTURE] Search problems: [SEARCH PROBLEMS] Update problems: [UPDATE PROBLEMS] Tool: [TOOL] Growth expectation: [SMALL / MEDIUM / LARGE] Examples of pages or notes: [EXAMPLES] Design the taxonomy: 1. Content type model Define page types: - reference page - process page - project page - decision page - meeting page - research page - idea page - template page - archive page For each include: - purpose - required fields - naming rule - tags - review frequency 2. Category structure Create top-level categories and subcategories. For each category include: - what belongs there - what does not belong there - example pages - owner - maintenance rule 3. Tag system Design tags for: - topic - status - project - priority - audience - source - format - review date Explain when to use tags instead of folders. 4. Relationship map Define relationships between: - projects and notes - research and decisions - meetings and tasks - templates and processes - ideas and outputs - archive and active material 5. Governance rules Create rules for: - adding new pages - merging duplicate pages - updating old pages - retiring pages - naming pages - avoiding category sprawl Rules: - Do not create a taxonomy that requires too much maintenance. - Do not use both folders and tags for the same purpose. - Do not make categories so broad they become dumping grounds. - The structure should scale without becoming chaotic. --------------------------------------------------------------------------------

#190Digital Declutter Sprint Planner

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONDigital cleanup days, quarterly resets, messy desktops, overflowing downloads, old cloud drives, app clutter, and disorganized knowledge systems.

Plan a focused cleanup sprint for files, notes, inboxes, bookmarks, downloads, desktops, apps, and old documents without getting overwhelmed.

Act as a digital declutter sprint coach. Help me plan a short, focused cleanup sprint that creates visible order quickly. Areas to declutter: [AREAS] Context: Time available: [TIME] Most painful digital clutter: [PAIN] Files or notes at risk of being lost: [IMPORTANT ITEMS] Tools involved: [TOOLS] What I should not delete: [DO NOT DELETE] What I want cleaned first: [PRIORITY] Energy level: [ENERGY] How organized I want to be: [STANDARD] Plan the sprint: A. Sprint target Choose the best cleanup target based on: - impact - urgency - visibility - ease - risk - time available B. Declutter rules Create rules for: - keep - move - rename - tag - archive - delete - merge - review later C. Sprint sequence Build a sprint plan for: - 15 minutes - 30 minutes - 60 minutes - 2 hours - half day Each version should include: - start point - actions - stopping point - success definition D. Decision shortcuts Create quick decisions for: - duplicate files - old downloads - screenshots - outdated documents - unfinished notes - old bookmarks - unknown files - random ideas E. Maintenance after sprint Create: - weekly cleanup routine - monthly archive routine - download folder rule - desktop rule - inbox rule - naming rule Rules: - Do not organize low-value clutter before protecting important information. - Do not create a massive project from a cleanup sprint. - Do not delete anything high-risk without a review step. - The sprint should create visible relief and a maintainable system. --------------------------------------------------------------------------------

#191Searchability and Retrieval Optimizer

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONPeople who know they saved something but cannot find it, teams with poor documentation search, messy notes, and large knowledge bases.

Improve how information is named, tagged, summarized, linked, and stored so it can be found quickly later.

You are a searchability optimization expert. Help me make my information easier to find later. Information set: [PASTE SAMPLE NOTES / FILE LIST / PAGE TITLES] Context: Where information lives: [TOOL / LOCATION] What I often search for: [SEARCH TERMS] What I cannot find easily: [HARD TO FIND] Who needs to find it: [USERS] Current naming style: [NAMING STYLE] Current tags: [TAGS] Current folder structure: [FOLDERS] Preferred search method: [SEARCH METHOD] Optimize retrieval: 1. Search behavior analysis Identify how someone would search for this information by: - topic - project - date - person - client - status - file type - decision - keyword - problem - outcome 2. Naming improvements Rewrite titles and filenames to include: - specific topic - project or area - date when useful - status - document type - searchable keywords - owner, if useful 3. Metadata design Recommend fields: - summary - category - tags - project - status - owner - source - date - review date - related links 4. Link and index system Create: - home index - topic indexes - project indexes - decision log links - related notes links - archive index 5. Retrieval test Create 10 search scenarios and show where each item should be found. Rules: - Do not rely on memory. - Do not create tags nobody will use. - Do not make titles clever at the expense of search. - The system should help future me find information in under 60 seconds. --------------------------------------------------------------------------------

#192Project Knowledge Hub Builder

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONProjects with scattered information across chat, docs, drives, meetings, task managers, and emails.

Create a single project hub that holds goals, documents, decisions, tasks, meeting notes, links, owners, timelines, risks, and status updates.

Act as a project knowledge hub designer. Build one central hub for all important information about this project. Project: [PROJECT] Current project information: [PASTE INFO / LINKS / NOTES] Context: Project goal: [GOAL] People involved: [PEOPLE] Tools currently used: [TOOLS] Documents involved: [DOCUMENTS] Meetings involved: [MEETINGS] Tasks involved: [TASKS] Decisions involved: [DECISIONS] Current information problems: [PROBLEMS] Who needs access: [ACCESS] Build the project hub: A. Hub structure Create sections for: - project overview - goals - scope - timeline - milestones - tasks - owners - key documents - meeting notes - decisions - risks - dependencies - status updates - resources - archive B. Source-of-truth rules Define: - where status lives - where tasks live - where files live - where decisions live - where meeting notes live - where final deliverables live C. Page templates Create templates for: - project overview - meeting notes - decision log - risk log - weekly update - document index - handoff notes D. Update cadence Create rules for: - daily updates - weekly updates - after meetings - after decisions - after milestone completion - after scope changes E. Migration plan List how to move scattered information into the hub without losing anything. Rules: - Do not duplicate information across multiple tools without a clear reason. - Do not make the hub a static document nobody updates. - Do not mix old archive material with current project status. - The hub should answer "what is happening, where is it, who owns it, and what changed?" --------------------------------------------------------------------------------

#193Meeting Notes to Action System

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONPeople who leave meetings with messy notes, unclear decisions, forgotten tasks, or no reliable follow-up system.

Convert raw meeting notes into decisions, tasks, owners, deadlines, follow-ups, reference notes, and updated project documentation.

You are a meeting information processor. Turn these raw meeting notes into clean actions, decisions, and documentation updates. Raw meeting notes: [PASTE NOTES] Context: Meeting name: [MEETING NAME] Date: [DATE] Attendees: [ATTENDEES] Project or topic: [PROJECT / TOPIC] Purpose of meeting: [PURPOSE] Task system: [TASK SYSTEM] Knowledge base location: [KNOWLEDGE BASE] Follow-up audience: [AUDIENCE] Process the meeting: 1. Meeting summary Create: - 5-line summary - key discussion points - unresolved questions - important context - risks raised 2. Decision extraction Extract decisions with: - decision - owner - rationale - affected area - date - follow-up needed - where to log it 3. Action item extraction Extract tasks with: - action - owner - deadline - priority - dependency - next step - task system destination 4. Information storage Classify information as: - project update - reference note - decision log - risk log - task - follow-up message - archive 5. Follow-up package Write: - meeting recap - action list - decision list - open questions - next meeting agenda - short message to attendees Rules: - Do not invent decisions that were not made. - Mark unclear owners or dates as [NEEDS CLARIFICATION]. - Do not leave action items buried in notes. - The output should be ready to paste into a task manager and knowledge base. --------------------------------------------------------------------------------

#194Personal Knowledge Inbox Processor

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONNotion inboxes, Apple Notes, Obsidian daily notes, Todoist inbox, saved messages, mobile notes, and quick capture systems.

Process all captured notes, links, screenshots, voice memos, and quick thoughts from a personal inbox into tasks, notes, projects, references, or archive.

Act as my personal knowledge inbox processor. Help me turn my raw capture inbox into organized, usable information. Raw inbox: [PASTE INBOX ITEMS] Context: My main projects: [PROJECTS] My main areas of life/work: [AREAS] My task system: [TASK SYSTEM] My notes system: [NOTES SYSTEM] My file system: [FILE SYSTEM] My categories: [CATEGORIES] What I want to prioritize: [PRIORITIES] What I want to ignore: [IGNORE] Time available to process: [TIME] Process every item: For each inbox item, decide: - what is this? - does it require action? - is it a task, note, project, reference, idea, reminder, or archive item? - where should it go? - what is the next action? - does it need a deadline? - does it need a tag? - should it be deleted? Create output sections: A. Tasks to add Include: - task - project - priority - deadline - context - first step B. Notes to save Include: - title - category - summary - tags - related project C. Ideas to develop Include: - idea - potential use - next review date D. Reference items Include: - title - storage location - tags - why saved E. Delete or archive Explain what can be removed and why. Rules: - Do not turn everything into a task. - Do not keep low-value items by default. - Do not leave items in the inbox after processing. - The output should empty the inbox into a clean system. --------------------------------------------------------------------------------

#195Digital Tool Source-of-Truth Audit

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONPeople or teams using many tools such as Notion, Google Drive, Slack, email, Trello, Asana, ClickUp, Obsidian, Airtable, and spreadsheets.

Decide which tool should own each type of information so tasks, notes, files, calendars, decisions, and reference materials do not get duplicated or lost.

You are a digital tool architecture consultant. Help me define a clear source of truth for each kind of information I manage. Tools I use: [TOOLS] Context: What each tool currently stores: [CURRENT USE] Information types: [TASKS / NOTES / FILES / DECISIONS / CALENDAR / LINKS / CONTACTS / REPORTS] Where duplication happens: [DUPLICATION] Where information gets lost: [LOST INFO] Who needs access: [USERS] Current workflow problems: [PROBLEMS] Tools I must keep: [MUST KEEP] Tools I am willing to remove: [CAN REMOVE] Integration options: [INTEGRATIONS] Audit tools: 1. Tool role analysis For each tool define: - current role - best role - information it should own - information it should not own - strengths - weaknesses - duplication risk - maintenance burden 2. Source-of-truth matrix Create a matrix for: - tasks - calendar - files - project status - meeting notes - decisions - reference knowledge - bookmarks - ideas - contacts - reports - templates - archive For each type specify: - primary tool - secondary tool, if needed - capture location - processing rule - archive location 3. Duplication cleanup Identify: - duplicates to remove - tools to stop using for certain info - data to migrate - links to preserve - naming to standardize 4. Workflow rules Create rules for: - where new tasks go - where new notes go - where files go - where decisions go - where project updates go - where final records go 5. Tool simplification plan Create: - keep - reduce - consolidate - integrate - retire - review later Rules: - Do not recommend changing tools just for novelty. - Do not allow the same information to have two competing sources of truth. - Do not ignore collaboration needs. - The final system should reduce confusion about where things belong. --------------------------------------------------------------------------------

#196Read-It-Later and Learning Pipeline

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONPeople who save too much content, consume without applying, forget what they read, or want learning to turn into notes and action.

Build a system for saving, reading, processing, summarizing, and applying articles, books, videos, courses, and learning resources.

Act as a learning pipeline designer. Help me turn saved content into real learning, usable notes, and practical action. Learning resources: [PASTE RESOURCES] Context: Topics I am learning: [TOPICS] Why I am learning them: [WHY] Current read-it-later system: [SYSTEM] Saved content backlog size: [BACKLOG] Available learning time: [TIME] Preferred formats: [ARTICLES / BOOKS / VIDEOS / COURSES / PODCASTS] How I take notes: [NOTES METHOD] How I want to apply learning: [APPLICATION] Build the pipeline: STAGE 1 — Save Create rules for what is worth saving and what should be ignored. STAGE 2 — Prioritize Sort resources into: - read now - read this week - reference only - extract key idea - watch later - archive - delete STAGE 3 — Consume Create reading or watching rules: - purpose before consuming - time limit - note method - when to stop - how to avoid passive consumption STAGE 4 — Process Create a processing template: - source - summary - key ideas - examples - quotes or data - personal interpretation - action to take - related notes - revisit date STAGE 5 — Apply Turn learning into: - task - habit - project idea - content idea - decision - experiment - reference note Rules: - Do not let saved content become a guilt pile. - Do not process every resource deeply. - Do not confuse consumption with learning. - The pipeline should turn the best resources into usable knowledge. --------------------------------------------------------------------------------

#197Archive, Retention and Cleanup Rules

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONShared drives, knowledge bases, personal files, notes, old projects, legal documents, screenshots, downloads, receipts, and outdated resources.

Create rules for what to keep, delete, archive, review, update, or move so digital systems do not grow endlessly.

You are an archive and retention policy designer. Help me create simple rules for keeping, deleting, reviewing, and archiving digital information. Information types: [INFORMATION TYPES] Context: Where information lives: [LOCATIONS] What must be kept: [MUST KEEP] What can be deleted: [CAN DELETE] Legal or compliance needs: [COMPLIANCE] Personal importance: [PERSONAL VALUE] Team or client access needs: [ACCESS] Current archive problems: [PROBLEMS] Storage limits: [LIMITS] Risk tolerance: [RISK TOLERANCE] Create retention rules: A. Information categories Classify items into: - active - reference - historical - legal or compliance - personal record - template - outdated - duplicate - temporary - trash B. Retention schedule For each category define: - keep duration - review frequency - archive location - delete criteria - owner - exceptions C. Archive structure Design archive folders or tags: - by year - by project - by client - by category - by status - by legal need D. Cleanup rules Create rules for: - downloads - screenshots - duplicate files - old drafts - abandoned notes - expired links - completed projects - old exports - outdated templates E. Safety checklist Before deleting, check: - legal value - financial value - client value - project history - personal value - unique information - backup availability Rules: - Do not delete high-risk information without review. - Do not archive everything just to avoid decisions. - Do not let archive folders become active workspaces. - The rules should make cleanup faster and safer. --------------------------------------------------------------------------------

#198Cross-Platform Information Flow Map

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONComplex digital setups, team workflows, solo operators with many apps, project systems, content workflows, and operations environments.

Map how information moves between tools, apps, people, inboxes, files, notes, task systems, and dashboards so flow becomes clear and duplication decreases.

Act as an information flow architect. Map how information moves across my tools and design a cleaner flow. Tools and platforms: [TOOLS / PLATFORMS] Context: Types of information moving between tools: [INFO TYPES] People involved: [PEOPLE] Current capture points: [CAPTURE POINTS] Current storage points: [STORAGE POINTS] Current task system: [TASK SYSTEM] Current knowledge system: [KNOWLEDGE SYSTEM] Current file system: [FILE SYSTEM] Current reporting system: [REPORTING] Current problems: [PROBLEMS] Map the flow: 1. Entry points Identify where information enters: - email - chat - meetings - forms - documents - browser - mobile notes - voice memos - task apps - shared drives - external sources 2. Movement map For each information type show: - entry point - first processing step - destination tool - action owner - update rule - archive rule - deletion rule 3. Duplication diagnosis Find where information is copied unnecessarily between: - chat and docs - docs and tasks - email and task manager - notes and knowledge base - drive and project hub - dashboards and spreadsheets 4. Clean flow design Create a cleaner flow with: - one capture inbox - one task destination - one file destination - one knowledge destination - one decision log - one archive path - clear exceptions 5. Automation or integration ideas Recommend: - safe automations - integration opportunities - templates - manual rules - areas to keep human Rules: - Do not design a flow that requires constant manual copying. - Do not create multiple destinations for the same information type. - Do not automate unclear information movement. - The final flow should make it obvious where information goes next. --------------------------------------------------------------------------------

#199Weekly Digital Organization Review

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONMaintaining digital order, preventing clutter from returning, processing captured information, and keeping systems useful over time.

Create a weekly review routine that clears inboxes, organizes notes, updates project hubs, archives completed items, reviews bookmarks, and prepares information for action.

You are a weekly digital review designer. Build a realistic weekly routine that keeps my digital information organized and actionable. Current systems: Task system: [TASK SYSTEM] Notes system: [NOTES SYSTEM] File system: [FILE SYSTEM] Calendar: [CALENDAR] Email or inboxes: [INBOXES] Bookmarks or read-it-later: [BOOKMARKS] Project hubs: [PROJECT HUBS] Knowledge base: [KNOWLEDGE BASE] Available review time: [TIME] Biggest weekly mess: [MESS] Desired outcome: [OUTCOME] Design the review: A. Review objectives The weekly review should: - empty capture inboxes - clarify tasks - organize notes - file documents - update project status - process saved resources - archive completed work - surface next actions - reduce digital clutter B. Review checklist Create a checklist for: - email - chat saves - task inbox - notes inbox - downloads folder - desktop - cloud drive - bookmarks - calendar - project hubs - knowledge base - archive C. Time-boxed versions Create versions for: - 10 minutes - 30 minutes - 60 minutes - 90 minutes - recovery week minimum D. Decision rules For each item decide: - action - schedule - delegate - save as reference - move to project - archive - delete - review later E. Weekly output At the end, produce: - cleaned inboxes - updated project list - next actions - files moved - notes processed - links processed - archive completed - unresolved items Rules: - Do not make the review so long I avoid it. - Do not reorganize the whole system every week. - Do not leave captured items unprocessed. - The weekly review should maintain the system, not rebuild it. --------------------------------------------------------------------------------

#200Full Information Management and Digital Organization Audit

INFORMATION MANAGEMENT & DIGITAL ORGANIZATIONFull digital resets, personal knowledge management, team documentation, messy drives, scattered notes, overloaded inboxes, and complex tool ecosystems.

Audit and redesign your complete digital information system across notes, files, inboxes, bookmarks, research, documents, knowledge bases, tools, naming, search, archive, and review habits.

Act as an independent information management and digital organization auditor. Review my complete digital system and redesign it so information is easy to capture, find, reuse, update, and turn into action. Full context: Main tools: [TOOLS] Main information types: [INFORMATION TYPES] Current notes system: [NOTES SYSTEM] Current file system: [FILE SYSTEM] Current task system: [TASK SYSTEM] Current calendar system: [CALENDAR] Current inboxes: [INBOXES] Current bookmarks or saved resources: [BOOKMARKS] Current knowledge base: [KNOWLEDGE BASE] Current project hubs: [PROJECT HUBS] Current naming conventions: [NAMING] Current tags or folders: [TAGS / FOLDERS] Current archive method: [ARCHIVE] Search problems: [SEARCH PROBLEMS] Duplicate information: [DUPLICATES] Information I often lose: [LOST INFO] Information I need to reuse often: [REUSE INFO] People who need access: [ACCESS] Privacy or compliance needs: [PRIVACY / COMPLIANCE] What I want the system to feel like: [DESIRED STATE] Audit across 30 dimensions: 1. Capture system 2. Inbox processing 3. Task separation 4. Notes organization 5. File structure 6. Folder depth 7. Naming conventions 8. Version control 9. Bookmark organization 10. Research workflow 11. Knowledge base taxonomy 12. Project hub structure 13. Meeting note processing 14. Decision logging 15. Source-of-truth clarity 16. Tool overlap 17. Searchability 18. Tag quality 19. Link structure 20. Archive rules 21. Retention rules 22. Duplicate control 23. Digital declutter habits 24. Weekly review routine 25. Access and sharing 26. Security or sensitivity handling 27. Templates 28. Automation or integration opportunities 29. Maintenance effort 30. Overall system usability For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason my information system is hard to use. B. System redesign Create: - information type map - source-of-truth matrix - folder structure - note structure - knowledge base taxonomy - naming convention - tagging rules - project hub template - inbox processing system - bookmark library structure - research workflow - archive and retention rules - weekly review routine C. Cleanup priorities Identify: - first 30-minute fix - first 2-hour fix - first 7-day cleanup plan - highest-risk clutter - easiest searchability improvement - most important source-of-truth decision - tool to simplify first D. Maintenance system Create: - daily capture rule - weekly processing rule - monthly cleanup rule - quarterly archive review - stale information rule - duplicate information rule - new tool adoption rule E. Executive summary Write a direct summary with: - messiest area - highest-impact fix - first folder to rebuild - first naming rule to adopt - first inbox to process - first archive rule to create - first weekly review habit - one rule to prevent the system from becoming chaotic again Rules: - Do not recommend an overbuilt personal knowledge system. - Do not confuse collecting information with managing information. - Do not create categories that require constant maintenance. - Use [LOW CONFIDENCE] where information is missing. - The final system should make information easier to find, reuse, update, and convert into action. -------------------------------------------------------------------------------- COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITY

#201Meeting Value Audit

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYTeams with too many meetings, unclear agendas, repeated discussions, low-energy calls, weak outcomes, or calendar overload.

Audit recurring meetings to identify which should stay, change, become async, merge, shorten, or disappear.

You are a meeting productivity auditor. Review my current meetings and help me reduce wasted time while protecting important collaboration. Meeting list: [PASTE MEETINGS] Context: Team size: [TEAM SIZE] Roles involved: [ROLES] Meeting frequency: [FREQUENCY] Meeting duration: [DURATION] Current calendar load: [CALENDAR LOAD] Main collaboration problems: [PROBLEMS] Meetings people complain about: [COMPLAINTS] Meetings that feel useful: [USEFUL MEETINGS] Meetings that feel unclear: [UNCLEAR MEETINGS] Decision speed needs: [DECISION SPEED] Audit every meeting: 1. Meeting inventory For each meeting identify: - meeting name - purpose - attendees - frequency - duration - owner - expected output - actual output - decisions made - actions created - information shared - recurring problems 2. Meeting value score Score each meeting from 1 to 10 across: - clear purpose - right attendees - useful output - decision quality - action follow-through - information value - energy cost - time efficiency - async potential 3. Keep / change / remove decision Classify each meeting as: - keep as is - shorten - reduce frequency - merge with another meeting - split into smaller meeting - turn into async update - replace with dashboard - remove completely - redesign from scratch 4. Redesign plan For every meeting that should change, provide: - new purpose - new agenda - new attendee list - new duration - new frequency - required pre-work - required output - follow-up rule 5. Calendar recovery plan Create: - hours saved per week - first meeting to remove - first meeting to redesign - async replacement template - team communication message Rules: - Do not remove meetings that are necessary for trust, decisions, or coordination. - Do not keep meetings just because they are traditional. - Do not recommend async updates for sensitive conversations that require discussion. - The final plan should reduce wasted time and increase meeting usefulness. --------------------------------------------------------------------------------

#202Async Communication Decision Tree

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYTeams with messy communication channels, too many meetings, scattered updates, slow decisions, or confusion about where to communicate.

Decide when to use email, chat, voice note, document, dashboard, meeting, comment, or task manager based on urgency, complexity, sensitivity, and decision needs.

Act as an async communication architect. Build a decision tree that tells us which communication channel to use for different kinds of work. Communication context: Team or group: [TEAM] Channels currently used: [CHANNELS] Tools available: [TOOLS] Current problems: [PROBLEMS] Work types: [WORK TYPES] Urgency expectations: [URGENCY] Decision-making needs: [DECISIONS] Sensitive topics: [SENSITIVE TOPICS] Documentation needs: [DOCUMENTATION] Time zones, if relevant: [TIME ZONES] Create the decision tree: START WITH THE QUESTION: "What kind of communication is this?" Then route by type: 1. Quick clarification Define: - best channel - response expectation - message format - when to escalate - when not to use a meeting 2. Status update Define: - best channel - required fields - frequency - audience - archive location 3. Decision request Define: - best channel - required context - deadline - decision owner - logging rule 4. Complex discussion Define: - when async is enough - when a meeting is needed - what pre-work is required - what output must be captured 5. Feedback request Define: - best format - review deadline - feedback rules - approval owner 6. Urgent blocker Define: - escalation channel - required details - response time - backup owner 7. Sensitive topic Define: - channel to avoid - preferred format - privacy rule - documentation rule Output: - full decision tree - channel rules - message templates - response-time expectations - examples of good and bad channel choices Rules: - Do not make chat the default for everything. - Do not make meetings the default for unclear messages. - Do not put important decisions only in private messages. - The system should reduce interruptions and make communication searchable. --------------------------------------------------------------------------------

#203Outcome-Driven Agenda Builder

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYPlanning sessions, project meetings, leadership updates, client calls, team syncs, brainstorming sessions, and decision meetings.

Create meeting agendas that define the outcome, required pre-work, decision points, discussion limits, owners, and follow-up expectations.

You are a meeting agenda designer. Create an agenda that makes this meeting useful, focused, and outcome-driven. Meeting: [MEETING NAME] Context: Why this meeting is needed: [WHY] Desired outcome: [OUTCOME] Attendees: [ATTENDEES] Meeting length: [LENGTH] Current problems with this meeting: [PROBLEMS] Topics to cover: [TOPICS] Decisions needed: [DECISIONS] Updates needed: [UPDATES] Pre-work available: [PRE-WORK] Constraints: [CONSTRAINTS] Build the agenda: A. Meeting purpose Write one clear sentence: "This meeting exists to..." B. Required output Define what must exist by the end: - decision - action plan - alignment - risk resolution - feedback - priorities - next steps - owner assignments C. Agenda structure Create a timed agenda with: - opening context - pre-read confirmation - decision items - discussion items - blocker review - action assignment - closing summary For each agenda item include: - owner - timebox - question to answer - input needed - output expected - decision rule D. Pre-work Create pre-work instructions for attendees: - what to read - what to prepare - what decision to consider - what information to bring - what not to discuss live E. Follow-up format Create a post-meeting summary template: - decisions - actions - owners - deadlines - open questions - risks - next meeting, if needed Rules: - Do not include agenda items that have no expected output. - Do not use the meeting for updates that can be sent async. - Do not invite people who do not contribute to the outcome. - The agenda should make it clear what "successful meeting" means. --------------------------------------------------------------------------------

#204Meeting Notes to Action Converter

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYAfter meetings, messy notes, unclear ownership, project calls, client calls, leadership discussions, and team syncs.

Convert messy meeting notes into decisions, action items, owners, deadlines, risks, follow-ups, and documentation updates.

Act as a meeting notes processor. Turn these raw notes into a clean execution package. Raw meeting notes: [PASTE NOTES] Context: Meeting name: [MEETING NAME] Date: [DATE] Attendees: [ATTENDEES] Project or topic: [PROJECT / TOPIC] Meeting purpose: [PURPOSE] Task system: [TASK SYSTEM] Decision log location: [DECISION LOG] Audience for recap: [AUDIENCE] Process the notes in this order: 1. Summary Write: - 3-line summary - main topic - most important outcome - unresolved tension - next milestone 2. Decisions Extract every decision. For each include: - decision - decision owner - rationale - date - affected project area - where it should be logged - confidence level If a decision is unclear, mark it as [DECISION UNCLEAR]. 3. Action items Extract every action item. For each include: - task - owner - deadline - priority - dependency - first step - done definition If owner or deadline is missing, mark [NEEDS OWNER] or [NEEDS DEADLINE]. 4. Risks and blockers Extract: - risk - blocker - impact - owner - next action - escalation needed 5. Follow-up message Write: - short recap for all attendees - direct owner-by-owner action list - open questions - next check-in recommendation Rules: - Do not invent decisions that were not made. - Do not bury action items inside paragraphs. - Do not treat discussion points as decisions unless clearly agreed. - The output should be ready to paste into a task manager and send as a recap. --------------------------------------------------------------------------------

#205Collaboration Operating Agreement

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYTeams, founders, remote teams, cross-functional groups, agencies, client delivery teams, and overloaded collaborators.

Create a team agreement for how people communicate, meet, give feedback, make decisions, follow up, and handle blockers.

You are a collaboration systems designer. Build a practical operating agreement for how this group should work together. Team or group: [TEAM / GROUP] Context: Team size: [SIZE] Roles: [ROLES] Work type: [WORK TYPE] Current collaboration problems: [PROBLEMS] Tools: [TOOLS] Meeting cadence: [MEETINGS] Decision-making style: [DECISION STYLE] Time zones: [TIME ZONES] Response expectations: [EXPECTATIONS] Common conflicts: [CONFLICTS] What good collaboration should feel like: [DESIRED STATE] Create the operating agreement: SECTION 1 — Communication principles Define rules for: - clarity - response times - urgency labels - channel selection - documentation - respectful escalation - sensitive topics SECTION 2 — Meeting rules Define: - when meetings are allowed - required agenda - required outcome - attendee rules - timebox rules - note-taking rules - follow-up rules SECTION 3 — Decision rules Define: - decision owner - input provider - approval owner - documentation rule - deadline rule - disagreement rule - revisit rule SECTION 4 — Feedback rules Define: - how to request feedback - how to give feedback - deadline expectations - required specificity - how to separate opinion from requirement SECTION 5 — Blocker rules Define: - what counts as a blocker - where to raise it - response time - escalation path - backup owner - documentation required SECTION 6 — Collaboration rituals Recommend: - weekly sync - async update - decision review - retrospective - project check-in - knowledge cleanup Rules: - Do not make rules that are too strict for real work. - Do not create policies nobody will follow. - Do not ignore remote or async needs. - The agreement should reduce confusion and make collaboration easier. --------------------------------------------------------------------------------

#206Feedback Loop Designer

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYCreative teams, managers, client work, design reviews, writing reviews, product reviews, performance feedback, and cross-functional collaboration.

Create a feedback system that makes requests, reviews, comments, approvals, and revisions clearer, faster, and less emotional.

Act as a feedback loop designer. Help me create a feedback process that improves work without creating confusion or endless revisions. Feedback context: Work being reviewed: [WORK] Who gives feedback: [REVIEWERS] Who receives feedback: [RECIPIENTS] Who approves final work: [APPROVER] Current feedback problems: [PROBLEMS] Typical review timeline: [TIMELINE] Number of review rounds: [ROUNDS] Quality criteria: [CRITERIA] Common vague feedback: [VAGUE FEEDBACK] Tools used: [TOOLS] Design the feedback loop: 1. Feedback request format Create a template that asks for: - context - objective - audience - stage of work - specific feedback needed - what not to review - deadline - decision needed 2. Feedback categories Separate feedback into: - required change - strategic concern - quality issue - factual correction - preference - suggestion - question - out-of-scope comment 3. Reviewer instructions Write rules for reviewers: - be specific - explain why - label severity - separate opinion from requirement - avoid rewriting everything - respect the stage of work - respond by deadline 4. Receiver process Create steps for the person receiving feedback: - collect - group - clarify - accept - reject - defer - revise - confirm 5. Approval flow Define: - when feedback closes - who makes final call - how conflicts are resolved - how decisions are logged - how changes are confirmed Rules: - Do not let every reviewer act as final approver. - Do not accept vague feedback without clarification. - Do not allow feedback after final approval unless scope changes. - The loop should improve quality while reducing revision chaos. --------------------------------------------------------------------------------

#207Follow-Up Reliability System

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYManagers, founders, client work, sales, project teams, operations, support, and people who lose track of pending replies or commitments.

Create a system for follow-ups after meetings, messages, decisions, requests, and commitments so nothing gets forgotten or delayed.

You are a follow-up systems architect. Build a reliable follow-up system for my communication and collaboration work. Follow-up context: Types of follow-ups: [TYPES] People involved: [PEOPLE] Current follow-up problems: [PROBLEMS] Where commitments are captured now: [CAPTURE LOCATION] Task system: [TASK SYSTEM] Calendar system: [CALENDAR] Communication channels: [CHANNELS] Urgency levels: [URGENCY LEVELS] Common missed follow-ups: [MISSED FOLLOW-UPS] Build the system: A. Follow-up categories Classify follow-ups into: - waiting for reply - action promised by me - action promised by someone else - decision pending - approval pending - information needed - payment or contract pending - meeting recap pending - deadline reminder - relationship check-in B. Capture method Create rules for capturing follow-ups from: - meetings - email - chat - calls - comments - documents - task boards - verbal requests C. Tracking system Design fields: - person - topic - promised action - owner - due date - next follow-up date - channel - priority - status - last contact - next message D. Follow-up cadence Create timing rules for: - same-day recap - 24-hour follow-up - 3-day follow-up - 1-week follow-up - overdue follow-up - final follow-up - escalation E. Message templates Write templates for: - gentle reminder - deadline reminder - clarification - overdue item - escalation - closing the loop - no longer needed Rules: - Do not rely on memory. - Do not make every follow-up urgent. - Do not let waiting items hide in chat or email. - The system should make commitments visible and easy to close. --------------------------------------------------------------------------------

#208Status Update Generator

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYTeam updates, project updates, leadership notes, client updates, Slack posts, email summaries, and async work environments.

Turn scattered progress information into clear async updates that show progress, blockers, decisions, risks, next actions, and confidence.

Act as an async status update writer. Convert my scattered progress data into a clear update that helps people understand what changed and what needs attention. Update context: Project or workstream: [PROJECT / WORKSTREAM] Audience: [AUDIENCE] Update frequency: [DAILY / WEEKLY / MILESTONE] Progress since last update: [PROGRESS] Current work: [CURRENT WORK] Blockers: [BLOCKERS] Risks: [RISKS] Decisions needed: [DECISIONS] Changes to scope or timeline: [CHANGES] Next actions: [NEXT ACTIONS] Tone: [TONE] Length preference: [LENGTH] Create the update in four versions: VERSION 1 — Ultra-short chat update Format: - Status: - Done: - Next: - Blocked: - Ask: VERSION 2 — Standard async update Format: - Summary - Progress - Current focus - Risks / blockers - Decisions needed - Next steps - Confidence level VERSION 3 — Leadership update Format: - Executive summary - What changed - What matters - Risk - Ask - Timeline confidence VERSION 4 — Client or stakeholder update Format: - Friendly summary - Completed work - What is in progress - What we need from you - Next milestone - Date of next update Then improve the update by: - removing vague language - making asks explicit - marking risks early - clarifying ownership - shortening where possible Rules: - Do not hide blockers. - Do not write long updates when a short one will work. - Do not use vague phrases like "working on it" without specifics. - The update should reduce follow-up questions. --------------------------------------------------------------------------------

#209Decision Log Architect

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYProjects, team collaboration, leadership decisions, client work, product work, operations, and any environment where decisions get forgotten or reopened.

Create a system for capturing decisions, rationale, owners, dates, alternatives considered, tradeoffs, and revisit rules.

You are a decision log architect. Build a decision tracking system that prevents repeated debates and lost context. Decision context: Project or team: [PROJECT / TEAM] Types of decisions made: [DECISION TYPES] Who makes decisions: [DECISION MAKERS] Who gives input: [INPUT PROVIDERS] Current decision problems: [PROBLEMS] Where decisions are currently stored: [CURRENT STORAGE] Tools available: [TOOLS] Decisions that often get reopened: [REOPENED DECISIONS] Build the decision log: 1. Decision capture criteria Define what must be logged: - strategic decisions - scope decisions - budget decisions - timeline decisions - ownership decisions - policy decisions - technical decisions - client decisions - exception decisions 2. Decision log fields Create fields for: - decision title - decision statement - date - owner - approver - contributors - context - options considered - rationale - tradeoffs - expected impact - related documents - revisit date - status 3. Decision workflow Create the process: - decision needed - context gathered - options listed - input collected - decision made - decision logged - communicated - reviewed if needed 4. Decision communication templates Write templates for: - decision request - decision made - decision changed - decision deferred - decision reopened - decision rejected 5. Revisit rules Define: - when to revisit - when not to revisit - what new evidence is required - who can reopen a decision - how to document changes Rules: - Do not log every tiny preference. - Do not allow major decisions to live only in chat. - Do not reopen decisions without new evidence. - The decision log should preserve context and speed up collaboration. --------------------------------------------------------------------------------

#210Meeting-to-Async Conversion Planner

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYReducing meeting load, protecting focus time, helping remote teams, improving documentation, and removing low-value syncs.

Convert unnecessary meetings into async updates, dashboards, decision docs, Loom-style recordings, comment threads, or office hours.

Act as a meeting-to-async conversion strategist. Help me replace unnecessary meetings with better async systems. Meeting to convert: [MEETING] Context: Current purpose: [PURPOSE] Attendees: [ATTENDEES] Frequency: [FREQUENCY] Duration: [DURATION] Topics usually discussed: [TOPICS] Decisions made in the meeting: [DECISIONS] Updates shared: [UPDATES] Problems with the meeting: [PROBLEMS] Risks of removing it: [RISKS] Tools available: [TOOLS] Evaluate conversion: A. Meeting necessity test Answer: - does this require live discussion? - does it require emotional nuance? - does it require fast back-and-forth? - does it require decision-making? - does it require relationship building? - does it require conflict resolution? - can it be handled with structured writing? B. Async replacement options Design replacements: - written status update - dashboard - decision document - recorded walkthrough - comment thread - shared checklist - office hours - weekly digest - exception-only meeting C. Recommended async format Choose the best replacement and define: - format - owner - deadline - response expectations - required fields - where it lives - how decisions are captured D. Safety mechanism Add a rule for when to bring the meeting back temporarily: - blocker threshold - decision delay - conflict - confusion - missed responses - high-risk change E. Conversion announcement Write a message explaining the change to the team. Rules: - Do not convert sensitive or conflict-heavy meetings into async by default. - Do not remove live collaboration where it creates trust or speed. - Do not replace meetings with unstructured chat. - The replacement should save time and improve documentation. --------------------------------------------------------------------------------

#211Cross-Functional Coordination Map

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYMarketing and sales handoffs, product launches, operations, client delivery, leadership work, project teams, and cross-functional initiatives.

Map coordination between teams, roles, dependencies, handoffs, communication channels, and decision owners so collaboration becomes cleaner.

You are a cross-functional coordination designer. Help me map how different people or teams should work together on this initiative. Initiative: [INITIATIVE] Context: Teams or roles involved: [TEAMS / ROLES] Goal: [GOAL] Timeline: [TIMELINE] Deliverables: [DELIVERABLES] Dependencies: [DEPENDENCIES] Current coordination problems: [PROBLEMS] Communication tools: [TOOLS] Decision owners: [DECISION OWNERS] Handoff points: [HANDOFFS] Risks: [RISKS] Create the coordination map: 1. Role map For each team or role define: - responsibility - deliverables owned - inputs needed - outputs provided - decisions owned - risks owned - communication channel 2. Dependency map Show: - who depends on whom - what is needed - when it is needed - what happens if delayed - backup option - escalation owner 3. Handoff map For every handoff define: - sender - receiver - asset or information transferred - required format - deadline - acceptance criteria - confirmation rule 4. Communication rhythm Create: - weekly coordination update - milestone check-in - blocker escalation path - decision request format - shared dashboard structure 5. Conflict prevention Identify likely friction points: - competing priorities - unclear ownership - slow approvals - resource conflicts - duplicate work - missed handoffs Create prevention rules for each. Rules: - Do not assume alignment because people are in the same meeting. - Do not leave dependencies informal. - Do not make everyone responsible for everything. - The map should make collaboration roles and handoffs obvious. --------------------------------------------------------------------------------

#212Collaborative Brainstorming Session Designer

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYCreative teams, product ideas, campaign planning, content ideation, problem-solving, workshops, and strategy sessions.

Design brainstorming sessions that generate useful ideas, avoid groupthink, capture decisions, and turn ideas into next steps.

Act as a collaborative brainstorming facilitator. Design a session that produces useful ideas and converts them into action. Brainstorming topic: [TOPIC] Context: Goal of session: [GOAL] Participants: [PARTICIPANTS] Time available: [TIME] Current problem or opportunity: [PROBLEM / OPPORTUNITY] Constraints: [CONSTRAINTS] Decision criteria: [CRITERIA] Ideas already considered: [EXISTING IDEAS] Desired output: [OUTPUT] Design the session: PHASE 1 — Prepare Create: - pre-read - framing question - constraints - examples - individual thinking prompt - required context PHASE 2 — Diverge Design exercises: - silent idea generation - bad idea reversal - audience perspective - constraint challenge - analogy prompt - "what would make this easier?" prompt - edge-case prompt PHASE 3 — Cluster Create a method to group ideas by: - theme - customer need - effort - impact - risk - novelty - feasibility PHASE 4 — Evaluate Create scoring criteria: - impact - effort - confidence - speed - strategic fit - risk - originality PHASE 5 — Decide and act Create: - top idea shortlist - decision owner - experiment plan - next action - owner - deadline - parking lot Output: - full agenda - facilitator script - participant prompts - decision matrix - follow-up template Rules: - Do not let loud voices dominate. - Do not end with only a list of ideas. - Do not evaluate ideas too early. - The session should produce decisions or experiments, not just energy. --------------------------------------------------------------------------------

#213Communication Clarity Rewriter

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYSlack messages, emails, manager updates, client communication, feedback comments, decision requests, and difficult conversations.

Rewrite unclear messages, updates, requests, feedback, or explanations so they become specific, actionable, respectful, and easy to respond to.

You are a communication clarity editor. Rewrite my message so it is easier to understand and act on. Original message: [PASTE MESSAGE] Context: Audience: [AUDIENCE] Relationship: [RELATIONSHIP] Goal of message: [GOAL] Desired action from recipient: [ACTION] Tone: [TONE] Urgency: [URGENCY] Important background: [BACKGROUND] What I want to avoid: [AVOID] Channel: [EMAIL / CHAT / DOC COMMENT / OTHER] Rewrite the message in five versions: 1. Clear and direct Use when speed matters. 2. Warm and collaborative Use when relationship matters. 3. Executive concise Use for leaders or busy stakeholders. 4. Feedback-focused Use when reviewing work. 5. Decision-request format Use when a decision or approval is needed. For each version include: - subject line or opening line - rewritten message - explicit ask - deadline, if relevant - next step Then diagnose the original message: - what was unclear - what was missing - what could be misread - what action was not obvious - what context was needed Rules: - Do not make the message longer unless clarity requires it. - Do not soften the ask until it disappears. - Do not make the tone robotic. - The recipient should know exactly what to do next. --------------------------------------------------------------------------------

#214Remote Collaboration Rhythm Builder

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYRemote teams, hybrid teams, distributed collaborators, international teams, async-first companies, freelancers, agencies, and cross-time-zone projects.

Build a remote-friendly communication rhythm with async updates, live meetings, decision docs, documentation habits, and time-zone-aware expectations.

Act as a remote collaboration systems designer. Create a rhythm that helps people stay aligned without constant meetings. Remote context: Team size: [TEAM SIZE] Locations or time zones: [TIME ZONES] Work type: [WORK TYPE] Current communication tools: [TOOLS] Current meeting load: [MEETING LOAD] Current async habits: [ASYNC HABITS] Biggest remote problems: [PROBLEMS] Decision speed needed: [DECISION SPEED] Documentation quality: [DOCUMENTATION] Preferred working hours: [WORKING HOURS] Build the rhythm: A. Communication layers Design layers for: - urgent blockers - daily progress - weekly alignment - decisions - documentation - social connection - deep collaboration - retrospectives For each layer specify: - channel - frequency - owner - expected response time - documentation rule B. Live meeting map Define which meetings should exist: - purpose - frequency - duration - attendees - pre-work - required output - cancellation rule C. Async update system Create templates for: - daily update - weekly update - blocker - decision request - project handoff - feedback request D. Time-zone rules Define: - overlap hours - response expectations - handoff rules - no-meeting windows - urgency definition - delayed response norms E. Remote trust rituals Create lightweight rituals for: - visibility - recognition - support - context sharing - learning - relationship maintenance Rules: - Do not require people to be always online. - Do not use meetings to compensate for poor documentation. - Do not make async communication vague. - The rhythm should protect focus while keeping collaboration alive. --------------------------------------------------------------------------------

#215Stakeholder Communication Cadence

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYProject managers, founders, agencies, consultants, leadership teams, client delivery, internal initiatives, and cross-functional projects.

Design a communication cadence for stakeholders so they receive the right updates, decisions, risks, and asks at the right time.

You are a stakeholder communication planner. Build a communication cadence that keeps stakeholders informed without overwhelming them. Project or initiative: [PROJECT / INITIATIVE] Stakeholders: [STAKEHOLDERS] Context: Stakeholder concerns: [CONCERNS] Decisions they own: [DECISIONS] Information they need: [INFO NEEDS] Current communication problems: [PROBLEMS] Project timeline: [TIMELINE] Risk level: [RISK] Preferred channels: [CHANNELS] Update frequency expectations: [FREQUENCY] Relationship sensitivity: [SENSITIVITY] Create the cadence: 1. Stakeholder segmentation Group stakeholders into: - decision-makers - contributors - reviewers - informed observers - blockers or risk owners - external partners - clients or customers 2. Communication needs matrix For each group define: - what they need to know - what they do not need to know - how often - channel - format - owner - response expectation - escalation trigger 3. Update formats Create templates for: - weekly status update - milestone update - risk alert - decision request - blocker escalation - scope change notice - final closeout 4. Cadence calendar Create a sample cadence for: - daily, if needed - weekly - milestone-based - monthly - exception-based - project close 5. Risk prevention Identify where stakeholders might be surprised and create proactive messages. Rules: - Do not send every stakeholder the same update. - Do not hide risks until they become emergencies. - Do not ask for decisions without context and options. - The cadence should increase trust and reduce surprise. --------------------------------------------------------------------------------

#216Action Item Accountability Board

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYTeams with forgotten action items, weak meeting follow-through, unclear ownership, recurring delays, or scattered commitments.

Create a board that tracks action items from meetings, messages, projects, and decisions with owners, deadlines, status, dependencies, and follow-ups.

Act as an accountability board designer. Build a system for tracking action items until they are completed or intentionally closed. Action item sources: [MEETINGS / CHAT / EMAIL / PROJECTS / DOCS] Context: Team or group: [TEAM] Current tracking method: [CURRENT METHOD] Common missed actions: [MISSED ACTIONS] Task system: [TASK SYSTEM] Meeting cadence: [MEETINGS] Owner expectations: [OWNER EXPECTATIONS] Deadline expectations: [DEADLINES] Follow-up style: [FOLLOW-UP STYLE] Design the board: A. Board structure Create columns: - captured - clarified - ready - in progress - waiting - blocked - review - done - closed / no longer needed For each column define: - meaning - entry criteria - exit criteria - owner responsibility B. Action item fields Create fields: - action - owner - source - date captured - due date - priority - dependency - status - blocker - next follow-up date - done definition C. Capture rules Define how actions are captured from: - meetings - chat - email - calls - document comments - stakeholder requests - decisions D. Review rhythm Create: - daily quick check - weekly action review - overdue review - blocked item review - completed item cleanup E. Accountability scripts Write messages for: - assigning an action - confirming ownership - asking for status - following up overdue - escalating blocker - closing completed item Rules: - Do not create action items without owners. - Do not create action items without a clear done definition. - Do not let "waiting" become a graveyard. - The board should make commitments visible and easy to complete. --------------------------------------------------------------------------------

#217Meeting Facilitation Script Builder

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYTeam leads, founders, managers, consultants, workshop facilitators, client calls, project meetings, and difficult discussions.

Create a facilitation script that helps the meeting leader open, guide, timebox, redirect, decide, summarize, and close the meeting effectively.

You are a meeting facilitation coach. Create a facilitation script for this meeting so it stays focused and produces a useful outcome. Meeting: [MEETING] Context: Purpose: [PURPOSE] Desired outcome: [OUTCOME] Attendees: [ATTENDEES] Duration: [DURATION] Agenda: [AGENDA] Likely distractions: [DISTRACTIONS] Likely conflicts: [CONFLICTS] Decisions needed: [DECISIONS] Tone needed: [TONE] Facilitator experience level: [EXPERIENCE] Create the script: OPENING Write what to say to: - welcome people - state purpose - confirm outcome - explain agenda - set participation rules - define decision method DISCUSSION CONTROL Create scripts for: - redirecting off-topic discussion - stopping repeated debate - inviting quieter people - limiting dominant voices - clarifying vague comments - moving from discussion to decision - parking unrelated issues DECISION MOMENTS Create scripts for: - summarizing options - naming tradeoffs - asking for final input - confirming decision owner - documenting decision - assigning actions TIMEBOXING Create phrases for: - 5 minutes left - topic over time - decision needed now - move to async follow-up - schedule separate discussion CLOSING Write what to say to: - summarize decisions - confirm action items - confirm owners and deadlines - name open questions - explain follow-up - close cleanly Rules: - Do not make the facilitator sound robotic. - Do not let the meeting end without decisions or next steps. - Do not ignore conflict if it blocks progress. - The script should help the facilitator keep momentum without being harsh. --------------------------------------------------------------------------------

#218Collaboration Handoff Brief

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYProject handoffs, shift handoffs, team transitions, client delivery, freelancer collaboration, manager delegation, and cross-functional work.

Create clear handoff briefs between collaborators so context, files, decisions, open questions, and next actions transfer without confusion.

Act as a collaboration handoff specialist. Create a handoff brief that lets the next person continue work without needing to chase context. Handoff situation: [HANDOFF SITUATION] Context: Person handing off: [SENDER] Person receiving: [RECEIVER] Project or work item: [PROJECT / WORK] Current status: [STATUS] Files or links: [FILES / LINKS] Decisions made: [DECISIONS] Open questions: [OPEN QUESTIONS] Risks: [RISKS] Deadlines: [DEADLINES] Next expected outcome: [OUTCOME] Communication channel: [CHANNEL] Build the handoff brief: 1. Handoff summary Include: - what this is - current status - why it matters - what has changed recently - what needs to happen next 2. Context package Include: - background - relevant documents - key decisions - stakeholders - constraints - dependencies - known sensitivities 3. Next-action map Create: - immediate next action - next 3 actions - owner - deadline - required input - done definition 4. Risk and exception notes Include: - active risks - possible blockers - what not to do - escalation path - decision owner 5. Receiver confirmation Create a confirmation checklist: - I have access - I understand the next action - I know the deadline - I know who to ask - I know where to update status Rules: - Do not assume the receiver knows the backstory. - Do not hide open questions. - Do not send files without explaining what to do with them. - The handoff should make the next step obvious. --------------------------------------------------------------------------------

#219Team Alignment Reset

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYTeams that feel busy but not coordinated, projects with confusion, leadership drift, conflict, unclear priorities, or repeated misunderstandings.

Diagnose and fix team misalignment around goals, priorities, ownership, decisions, communication, deadlines, and expectations.

You are a team alignment facilitator. Help me reset alignment across this team or project. Team or project: [TEAM / PROJECT] Context: Goal: [GOAL] Current priorities: [PRIORITIES] People involved: [PEOPLE] Current confusion: [CONFUSION] Recent conflicts: [CONFLICTS] Missed expectations: [MISSED EXPECTATIONS] Unclear decisions: [UNCLEAR DECISIONS] Communication problems: [COMMUNICATION PROBLEMS] Deadline pressure: [DEADLINES] What good alignment should look like: [DESIRED STATE] Run the alignment reset: A. Misalignment diagnosis Identify misalignment across: - goals - priorities - scope - ownership - deadlines - decision rights - quality expectations - communication channels - stakeholder expectations - success metrics B. Alignment questions Create questions the team must answer: - what are we trying to accomplish? - what matters most right now? - what is not a priority? - who owns what? - who decides what? - what does done mean? - what risks are we accepting? - how will we communicate? C. Alignment workshop Create a 60-minute agenda: - context - individual concerns - shared goal - priority ranking - ownership clarification - decision rules - next actions - recap D. Alignment document Create a one-page alignment brief: - goal - priorities - non-priorities - owners - decision owners - deadlines - communication rules - open issues E. Follow-up system Create: - 24-hour recap - 7-day check-in - decision log update - accountability board update - risk review Rules: - Do not solve alignment with a vague motivational meeting. - Do not leave ownership or decision rights unclear. - Do not ignore conflict if it affects execution. - The reset should turn confusion into shared commitments. --------------------------------------------------------------------------------

#220Full Communication, Meetings and Collaboration Productivity Audit

COMMUNICATION, MEETINGS & COLLABORATION PRODUCTIVITYTeams, founders, managers, agencies, remote teams, project groups, client-facing teams, and organizations losing time to unclear communication.

Audit and redesign the complete collaboration system across meetings, async communication, updates, decisions, feedback, follow-ups, handoffs, agendas, summaries, and team coordination.

Act as an independent communication, meetings, and collaboration productivity auditor. Review my collaboration system and redesign it so people spend less time confused, more time executing, and fewer decisions get lost. Full context: Team or group: [TEAM / GROUP] Work type: [WORK TYPE] People involved: [PEOPLE] Current tools: [TOOLS] Current meetings: [MEETINGS] Current async channels: [ASYNC CHANNELS] Current update formats: [UPDATES] Current decision process: [DECISIONS] Current feedback process: [FEEDBACK] Current follow-up process: [FOLLOW-UPS] Current handoff process: [HANDOFFS] Current documentation habits: [DOCUMENTATION] Main communication problems: [PROBLEMS] Common meeting problems: [MEETING PROBLEMS] Common collaboration delays: [DELAYS] Where work gets misunderstood: [MISUNDERSTOOD WORK] What a better collaboration system should feel like: [DESIRED STATE] Audit across 30 dimensions: 1. Communication channel clarity 2. Async communication quality 3. Response-time expectations 4. Meeting purpose clarity 5. Meeting agenda quality 6. Meeting attendee fit 7. Meeting output quality 8. Meeting follow-through 9. Meeting load 10. Update quality 11. Status visibility 12. Decision ownership 13. Decision logging 14. Feedback quality 15. Review and approval flow 16. Follow-up reliability 17. Action item ownership 18. Handoff quality 19. Documentation habits 20. Source of truth 21. Stakeholder communication 22. Cross-functional coordination 23. Remote collaboration rhythm 24. Conflict handling 25. Escalation rules 26. Brainstorming effectiveness 27. Facilitation quality 28. Alignment rituals 29. Collaboration tool fit 30. Overall collaboration productivity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason communication is wasting time or creating confusion. B. Collaboration system redesign Create: - channel decision tree - meeting rules - async update system - agenda template - meeting notes template - decision log - feedback process - follow-up tracker - action item board - handoff brief template - stakeholder cadence - escalation rules - remote collaboration rhythm - weekly alignment ritual C. Meeting cleanup plan Identify: - meetings to keep - meetings to shorten - meetings to reduce - meetings to merge - meetings to turn async - meetings to remove - expected time saved D. Communication improvement plan Create: - first 24-hour cleanup - first 7-day communication reset - first 30-day collaboration system rollout - weekly review rhythm - what to stop immediately - what to standardize first E. Executive summary Write a direct summary with: - most wasteful meeting pattern - weakest communication channel - highest-risk missing decision log - biggest follow-up gap - most important handoff to fix - first async template to create - first meeting to redesign - one rule that would reduce confusion immediately Rules: - Do not add meetings as the default solution. - Do not make the communication system more complex than the work. - Do not hide hard truths about unclear ownership or poor follow-through. - Use [LOW CONFIDENCE] where information is missing. - The final system should reduce wasted time, improve clarity, and make collaboration easier to maintain. -------------------------------------------------------------------------------- PRODUCTIVITY SYSTEMS, TEMPLATES & SOPs

#221Productivity Infrastructure Blueprint

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsPeople who have many tools, many plans, many notes, and many tasks but no clear operating structure.

Design a lightweight productivity infrastructure that connects goals, projects, tasks, templates, dashboards, review routines, and documentation into one usable system.

You are a productivity systems architect. Help me design a simple productivity infrastructure that makes consistent execution easier without creating unnecessary complexity. My context: Work type: [WORK TYPE] Main goals: [GOALS] Main projects: [PROJECTS] Current tools: [TOOLS] Current task system: [TASK SYSTEM] Current planning system: [PLANNING SYSTEM] Current documentation system: [DOCUMENTATION SYSTEM] Current review routine: [REVIEW ROUTINE] Biggest productivity problems: [PROBLEMS] What I want the system to feel like: [DESIRED STATE] Build the productivity infrastructure: 1. System map Create a map that connects: - goals - projects - tasks - calendar - notes - templates - SOPs - dashboards - review routines - archives For each part explain: - purpose - where it lives - how often it is updated - what input it receives - what output it creates - what decision it supports 2. Core system pages Design these core pages: - command center - project dashboard - task dashboard - weekly plan - daily plan - review page - template library - SOP library - knowledge base - archive 3. Operating rules Create rules for: - capturing work - clarifying work - planning work - executing work - reviewing work - documenting work - archiving work 4. Minimum viable system Create a version I can set up in 60 minutes. Include: - pages to create - fields to add - templates to build first - routines to start with - things to ignore for now 5. Maintenance rhythm Create: - daily maintenance - weekly maintenance - monthly maintenance - quarterly cleanup - trigger for redesign Rules: - Do not overbuild. - Do not create pages nobody will use. - Do not design a system that requires constant grooming. - The final system should make important work easier to see, choose, and complete. --------------------------------------------------------------------------------

#222Reusable Template Library Builder

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsTeams, solo operators, managers, creators, consultants, founders, and anyone who repeats similar work often.

Create a reusable template library for recurring work so planning, writing, reporting, documenting, and reviewing become faster and more consistent.

Act as a template library designer. Help me build a practical library of templates that saves time and improves consistency. Context: My role: [ROLE] Recurring work I do: [RECURRING WORK] Documents I create often: [DOCUMENTS] Plans I repeat: [PLANS] Reports I repeat: [REPORTS] Messages I repeat: [MESSAGES] Checklists I repeat: [CHECKLISTS] Current templates: [CURRENT TEMPLATES] Current problems: [PROBLEMS] Tool where templates will live: [TOOL] Build the template library: A. Template inventory Identify templates I need across: - planning - project management - meetings - daily work - weekly reviews - reporting - decision-making - communication - documentation - SOPs - checklists - handoffs - retrospectives B. Template priority score For each template idea score: - frequency of use - time saved - error reduction - clarity improvement - delegation value - maintenance effort - priority level C. Template structure For each high-priority template include: - template name - purpose - when to use it - required fields - optional fields - example entry - completion criteria - owner - review frequency D. Library organization Design: - folder or database structure - naming convention - tags - categories - archive rules - template request process - template update process E. First 10 templates Create the first 10 templates I should build, with copyable outlines. Rules: - Do not create templates for work that happens once. - Do not make templates longer than the work they support. - Do not create overlapping templates. - Each template should reduce thinking friction or prevent mistakes. --------------------------------------------------------------------------------

#223SOP from Scratch Generator

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsOperations, admin work, client delivery, content production, reporting, onboarding, finance, support, and repeated workflows.

Turn an undocumented recurring process into a clear SOP with purpose, roles, prerequisites, steps, quality checks, exceptions, and update rules.

You are an SOP writer. Create a clear, usable SOP for this process so someone can perform it correctly without relying on memory. Process: [PROCESS NAME] Context: Purpose of the process: [PURPOSE] Who performs it: [ROLE] Who owns it: [OWNER] How often it happens: [FREQUENCY] Tools used: [TOOLS] Inputs required: [INPUTS] Outputs expected: [OUTPUTS] Current steps: [CURRENT STEPS] Common mistakes: [MISTAKES] Quality requirements: [QUALITY] Exceptions: [EXCEPTIONS] Escalation contact: [CONTACT] Write the SOP using this structure: 1. SOP header Include: - SOP title - owner - version - last updated - review frequency - audience - estimated time 2. Purpose and outcome Explain: - why the process exists - what successful completion looks like - what problem it prevents 3. Before you start List: - required access - required files - required inputs - required tools - pre-checks - dependency checks 4. Step-by-step process For each step include: - step number - action - tool or location - expected result - quality check - common mistake to avoid 5. Exceptions and troubleshooting Include: - if this happens - likely cause - what to do - who to contact - how to document it 6. Final quality check Create a checklist for completion. 7. Change log Create a simple version history table. Rules: - Do not write vague instructions. - Do not skip tool locations or required inputs. - Do not assume prior knowledge. - The SOP should be usable during real work, not only readable. --------------------------------------------------------------------------------

#224Checklist System Designer

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsPreventing missed steps, improving consistency, delegating work, reducing mistakes, and making repeated work easier.

Build a family of checklists for recurring work, including start checks, execution checks, QA checks, handoff checks, and completion checks.

Act as a checklist systems designer. Create the right set of checklists for this recurring workflow. Workflow: [WORKFLOW] Context: Goal of the workflow: [GOAL] Who performs it: [PERSON / ROLE] Frequency: [FREQUENCY] Current process: [PROCESS] Common missed steps: [MISSED STEPS] Common mistakes: [MISTAKES] Quality standard: [QUALITY] Handoff points: [HANDOFFS] Approval points: [APPROVALS] Consequences of failure: [CONSEQUENCES] Design the checklist system: Checklist 1 — Start readiness Create a checklist that confirms: - inputs are ready - access is available - deadlines are clear - owner is clear - examples are available - risks are known Checklist 2 — Execution Create a step-by-step checklist for doing the work. Each item must be: - action-based - specific - verifiable - in the correct order Checklist 3 — Quality assurance Create a checklist that verifies: - accuracy - completeness - formatting - stakeholder requirements - compliance or brand rules - common error prevention Checklist 4 — Handoff Create a checklist for transferring work to the next person or stage. Checklist 5 — Completion Create a final checklist that confirms: - output is delivered - files are saved - task is closed - documentation updated - follow-up scheduled - lessons captured Then add: - short version - detailed version - manager audit version - beginner version Rules: - Do not include vague items like "check everything." - Do not overload one checklist with every detail. - Do not add checks that do not prevent errors. - The checklist system should make work more reliable without slowing it unnecessarily. --------------------------------------------------------------------------------

#225Productivity Dashboard Designer

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsPersonal operating systems, team productivity systems, Notion dashboards, spreadsheets, ClickUp, Asana, Airtable, and project workspaces.

Create a dashboard that shows goals, projects, tasks, deadlines, routines, metrics, reviews, and next actions in one clean view.

You are a productivity dashboard designer. Build a dashboard that helps me see what matters and decide what to do next. Dashboard context: Audience: [ME / TEAM / CLIENT / LEADERSHIP] Main work areas: [AREAS] Current goals: [GOALS] Active projects: [PROJECTS] Tasks: [TASKS] Deadlines: [DEADLINES] Recurring routines: [ROUTINES] Metrics to track: [METRICS] Current tools: [TOOLS] Current dashboard problems: [PROBLEMS] Design the dashboard: A. Dashboard purpose Define the top 5 questions the dashboard must answer, such as: - what matters this week? - what is due soon? - what is blocked? - what needs review? - what is falling behind? B. Dashboard sections Create sections for: - focus of the week - active projects - priority tasks - deadlines - waiting on - routines - metrics - review checklist - quick capture - archive links C. Fields and views For each section define: - fields - filters - sort order - status labels - update frequency - owner - decision supported D. Visual hierarchy Recommend what should be: - at the top - visible daily - hidden unless needed - reviewed weekly - archived monthly E. Dashboard maintenance Create rules for: - daily update - weekly reset - monthly cleanup - stale item removal - metric review - template improvement Rules: - Do not make the dashboard a decoration. - Do not include metrics that do not change behavior. - Do not show everything at once. - The dashboard should reduce decision fatigue and make execution obvious. --------------------------------------------------------------------------------

#226Weekly Review System Builder

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsProfessionals, founders, creators, managers, students, solo operators, and teams that need a reliable weekly reset.

Build a weekly review system that captures progress, clears loose ends, updates priorities, reviews projects, plans the next week, and improves execution.

Act as a weekly review systems designer. Create a weekly review routine that helps me stay organized, focused, and consistent. My context: Main responsibilities: [RESPONSIBILITIES] Active projects: [PROJECTS] Task system: [TASK SYSTEM] Calendar: [CALENDAR] Notes system: [NOTES] Current weekly review habit: [CURRENT HABIT] What usually slips: [SLIPS] What I want to improve: [IMPROVE] Available review time: [TIME] Preferred day/time: [DAY / TIME] Build the weekly review: PHASE 1 — Clear Create steps to clear: - task inbox - notes inbox - email or messages - downloads or files - loose reminders - open browser tabs - calendar leftovers PHASE 2 — Review Create steps to review: - last week's goals - completed work - unfinished work - active projects - deadlines - waiting items - meetings - routines - energy level PHASE 3 — Decide Create decision prompts: - what matters most next week? - what should be stopped? - what should be delayed? - what needs help? - what must be protected? - what is the one outcome that matters most? PHASE 4 — Plan Create: - weekly priorities - project actions - calendar blocks - admin batch - follow-ups - recovery time - risk plan PHASE 5 — Improve Create reflection prompts: - what created friction? - what worked? - what repeated problem needs a system? - what template or SOP should be created? Output: - full weekly review checklist - 15-minute version - 45-minute version - 90-minute deep version - weekly review page template Rules: - Do not make the review so long I avoid it. - Do not just list tasks; force priority decisions. - Do not ignore unfinished work. - The review should create clarity for the next week. --------------------------------------------------------------------------------

#227Daily Planning Page Template

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsDaily execution, personal productivity systems, planners, Notion pages, paper planners, task managers, and focus routines.

Create a daily planning page that connects priorities, schedule, energy, tasks, focus blocks, routines, notes, and end-of-day review.

You are a daily planning template designer. Create a daily planning page that helps me start, execute, and close the day with clarity. Context: My work type: [WORK TYPE] Main daily challenges: [CHALLENGES] Typical schedule: [SCHEDULE] Task volume: [TASK VOLUME] Energy pattern: [ENERGY PATTERN] Focus needs: [FOCUS NEEDS] Recurring routines: [ROUTINES] Current daily planning method: [METHOD] Preferred length: [SHORT / MEDIUM / DETAILED] Design the daily planning page: Morning section: Create fields for: - date - one main outcome - top 3 priorities - schedule - focus blocks - energy check - must-do tasks - quick wins - avoid list - potential blockers Execution section: Create fields for: - task list - deep work block - admin batch - waiting on - decisions needed - notes - distractions captured - time adjustments Midday reset: Create prompts for: - what changed? - what is still realistic? - what should be cut? - what needs protection? - what is the next best action? End-of-day review: Create fields for: - completed - not completed - why it slipped - lessons - follow-ups - tomorrow's first action - shutdown note Then create: - minimal version - detailed version - high-stress day version - deep work day version - meeting-heavy day version Rules: - Do not overfill the day. - Do not treat all tasks as equal. - Do not ignore energy and calendar reality. - The template should guide execution, not become extra work. --------------------------------------------------------------------------------

#228Personal Operating Manual Generator

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsSelf-management, managers, teams, assistants, founders, creators, remote work, delegation, and reducing repeated misunderstandings.

Create a personal operating manual that defines how you work best, communicate, plan, make decisions, manage energy, handle deadlines, and collaborate.

Act as a personal operating manual writer. Help me create a clear manual for how I work best and how others can work with me effectively. My context: Role: [ROLE] Work style: [WORK STYLE] Strengths: [STRENGTHS] Weaknesses: [WEAKNESSES] Communication preferences: [COMMUNICATION] Decision style: [DECISION STYLE] Energy patterns: [ENERGY] Focus needs: [FOCUS] Meeting preferences: [MEETINGS] Feedback preferences: [FEEDBACK] Delegation preferences: [DELEGATION] Stress signals: [STRESS SIGNALS] What people misunderstand about me: [MISUNDERSTANDINGS] Create my operating manual: 1. Work principles Define: - how I prioritize - how I plan - how I focus - how I make decisions - how I handle deadlines - how I manage energy 2. Communication guide Explain: - best channels - response expectations - how to ask me for decisions - how to send updates - how to escalate - what communication habits drain me 3. Collaboration guide Explain: - how to work with me - how I prefer meetings - how I give feedback - how I receive feedback - how I handle conflict - how I prefer handoffs 4. Productivity system Define: - tools I use - where tasks go - where notes go - where decisions go - weekly review rhythm - daily planning rhythm 5. Edge cases Explain: - when I am overloaded - when I need clarity - when something is urgent - when to interrupt me - when not to interrupt me Output: - full manual - one-page summary - team-friendly version - assistant-friendly version - update checklist Rules: - Do not make the manual sound like corporate policy. - Do not pretend all preferences are strengths. - Do not ignore tradeoffs. - The manual should help me and others work together with less friction. --------------------------------------------------------------------------------

#229Routine and Ritual Template System

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsProductivity systems, team rituals, personal routines, planning systems, operating rhythms, and recurring review cycles.

Build templates for repeatable daily, weekly, monthly, quarterly, project, and review routines that support consistent execution.

You are a routine systems designer. Build a template system for routines and rituals that makes consistent execution easier. Routine context: Types of routines needed: [DAILY / WEEKLY / MONTHLY / PROJECT / TEAM / PERSONAL] Current routines: [CURRENT ROUTINES] Routines that fail: [FAILED ROUTINES] Desired outcomes: [OUTCOMES] Time available: [TIME] Tools used: [TOOLS] People involved: [PEOPLE] Main friction: [FRICTION] Create the routine system: A. Routine inventory List routines I should have across: - daily startup - daily shutdown - weekly planning - weekly review - monthly review - quarterly planning - project kickoff - project review - inbox processing - knowledge cleanup - dashboard maintenance B. Routine template For each routine create: - name - purpose - trigger - frequency - duration - steps - required inputs - output - success signal - fallback version - skip rule - improvement note C. Ritual design For routines that involve people, define: - attendees - agenda - roles - decision points - notes format - follow-up rule D. Failure prevention Identify why routines fail: - too long - unclear trigger - low value - no visible output - bad timing - too many steps - weak connection to goals Create fixes for each. E. Implementation plan Create: - first routine to install - second routine to install - routine stacking order - 30-day adoption plan - review date Rules: - Do not create routines for everything. - Do not make routines dependent on motivation. - Do not ignore fallback versions. - Each routine should produce a useful output. --------------------------------------------------------------------------------

#230Planning Page System Designer

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsGoal planning, project planning, business planning, personal productivity, creator systems, team operations, and strategic execution.

Create planning pages for goals, quarters, months, weeks, projects, launches, reviews, and decisions so planning becomes repeatable and consistent.

Act as a planning page architect. Build a reusable planning page system for my work. Context: Planning level needed: [DAILY / WEEKLY / MONTHLY / QUARTERLY / PROJECT / BUSINESS] Main goals: [GOALS] Active projects: [PROJECTS] Current planning problems: [PROBLEMS] Tools used: [TOOLS] People involved: [PEOPLE] Review cadence: [CADENCE] Planning style preferred: [STYLE] What planning must help me decide: [DECISIONS] Design the planning page system: 1. Goal planning page Include: - goal - why it matters - success metric - deadline - constraints - projects connected - risks - review cadence 2. Quarterly planning page Include: - theme - outcomes - projects - capacity - tradeoffs - milestones - stop-doing list - review checkpoints 3. Monthly planning page Include: - focus areas - project milestones - deadlines - habits or routines - risks - backlog decisions - success criteria 4. Weekly planning page Include: - top outcomes - calendar review - project actions - task list - waiting on - focus blocks - recovery space 5. Project planning page Include: - objective - scope - deliverables - milestones - owners - dependencies - done definition - next action 6. Review page Include: - results - misses - lessons - friction - systems to improve - next decisions Rules: - Do not create planning pages that duplicate task lists. - Do not make planning abstract; each page must produce decisions. - Do not ignore capacity. - The planning system should connect long-term direction to weekly execution. --------------------------------------------------------------------------------

#231SOP Library and Governance System

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsTeams, operations, agencies, internal documentation, onboarding, compliance, recurring workflows, and knowledge management.

Create a system for storing, naming, updating, reviewing, approving, and retiring SOPs so documentation stays useful over time.

You are an SOP library manager. Design a system for organizing and maintaining SOPs so they remain accurate, findable, and useful. Context: Number of SOPs: [NUMBER] Types of SOPs: [TYPES] Current SOP location: [LOCATION] Users: [USERS] Owners: [OWNERS] Current problems: [PROBLEMS] Review requirements: [REVIEW REQUIREMENTS] Approval process: [APPROVAL] Tool: [TOOL] Compliance needs: [COMPLIANCE] Build the SOP governance system: A. SOP library structure Create categories for: - operations - admin - finance - sales - marketing - customer service - product - HR - reporting - quality control - tools - emergency procedures Only include categories that fit my context. B. SOP naming convention Create naming rules with examples: - process name - department or area - status - version - owner - review date C. SOP metadata Create required fields: - owner - status - version - last updated - review date - audience - related templates - related checklists - approval status - risk level D. Governance rules Define: - who can create SOPs - who approves SOPs - how changes are requested - how updates are logged - how review reminders work - how outdated SOPs are retired - how exceptions are documented E. Maintenance cadence Create: - monthly SOP review - quarterly high-risk SOP review - annual documentation cleanup - broken SOP report - user feedback loop Rules: - Do not let SOPs become static documents. - Do not create governance heavier than the organization needs. - Do not keep outdated SOPs active. - The system should make the right SOP easy to find and trust. --------------------------------------------------------------------------------

#232Template Quality Control Audit

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsTemplate libraries, Notion workspaces, team docs, Google Docs, reporting templates, project templates, and SOP templates.

Audit existing templates to remove clutter, improve clarity, standardize structure, eliminate duplicates, and make each template easier to use.

Act as a template quality auditor. Review my templates and improve them so they are useful, clear, and easy to reuse. Templates to audit: [PASTE TEMPLATE LIST OR TEMPLATE CONTENT] Context: Who uses these templates: [USERS] Where templates live: [LOCATION] How often they are used: [FREQUENCY] Current complaints: [COMPLAINTS] Duplicate templates: [DUPLICATES] Missing templates: [MISSING] Brand or formatting rules: [RULES] Main goal of the template system: [GOAL] Audit the templates: 1. Template usefulness For each template evaluate: - purpose clarity - frequency of use - ease of completion - field quality - instruction clarity - output quality - maintenance burden - duplication risk - archive or keep recommendation 2. Template problems Identify: - vague fields - unnecessary fields - missing examples - outdated instructions - confusing order - too many sections - no completion criteria - no owner - no versioning 3. Rewrite improvements For each important template provide: - better title - clearer purpose - improved section order - fields to remove - fields to add - example answers - completion checklist 4. Template library cleanup Create: - templates to keep - templates to merge - templates to rewrite - templates to archive - templates to delete - templates to create next 5. Template quality standard Create rules every future template must follow. Rules: - Do not keep templates just because they already exist. - Do not add fields that do not improve output. - Do not create multiple templates for the same job. - Templates should speed work and improve consistency. --------------------------------------------------------------------------------

#233Lightweight Team Operating Manual

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsSmall teams, agencies, startups, departments, remote teams, operations groups, and growing teams that need structure without bureaucracy.

Create a practical operating manual that explains how a team plans, communicates, decides, documents, reviews, and improves work.

You are a team operations writer. Create a lightweight operating manual for how this team works. Team context: Team name: [TEAM] Team purpose: [PURPOSE] Team size: [SIZE] Roles: [ROLES] Main workflows: [WORKFLOWS] Tools: [TOOLS] Meetings: [MEETINGS] Planning rhythm: [PLANNING] Communication problems: [PROBLEMS] Decision-making problems: [DECISION PROBLEMS] Documentation problems: [DOCUMENTATION PROBLEMS] Desired culture: [CULTURE] Create the operating manual: SECTION 1 — Team purpose Include: - what the team owns - what the team does not own - success metrics - key stakeholders SECTION 2 — Roles and ownership Include: - role responsibilities - decision rights - handoff points - backup owners SECTION 3 — Planning rhythm Include: - daily rhythm - weekly rhythm - monthly rhythm - quarterly rhythm - project kickoff - review process SECTION 4 — Communication rules Include: - channels - response expectations - update formats - escalation rules - meeting rules - async rules SECTION 5 — Documentation rules Include: - where tasks live - where docs live - where decisions live - where SOPs live - where templates live - archive rules SECTION 6 — Quality and improvement Include: - quality standards - review gates - retrospective rhythm - improvement log - owner of updates Output: - full manual - one-page quick guide - onboarding version - maintenance checklist Rules: - Do not make the manual feel like legal policy. - Do not include rules nobody will enforce. - Do not leave ownership unclear. - The manual should make team execution easier and more consistent. --------------------------------------------------------------------------------

#234Repeatable Review System Builder

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsProductivity systems, team operations, personal reviews, leadership routines, project retrospectives, and continuous improvement.

Create review systems for projects, weeks, months, goals, habits, dashboards, templates, SOPs, and performance so improvement becomes systematic.

Act as a review systems designer. Build a repeatable review system that helps me improve execution, not just reflect. Review context: What needs reviewing: [PROJECTS / GOALS / HABITS / TASKS / SOPs / DASHBOARDS] Current review habits: [CURRENT HABITS] Review frequency desired: [FREQUENCY] People involved: [PEOPLE] Metrics available: [METRICS] Current problems: [PROBLEMS] What decisions reviews should support: [DECISIONS] Time available: [TIME] Design the review system: A. Review types Create review templates for: - daily review - weekly review - monthly review - quarterly review - project retrospective - SOP review - template review - dashboard review B. Review anatomy For each review define: - purpose - trigger - duration - inputs needed - questions to answer - metrics to check - decisions to make - output produced - next action C. Review questions Create questions across: - results - misses - bottlenecks - energy - quality - speed - focus - systems - communication - improvement opportunities D. Action conversion Create a process for turning review insights into: - tasks - system changes - SOP updates - template updates - calendar changes - delegation - stop-doing decisions E. Review calendar Create a realistic cadence that avoids review overload. Rules: - Do not create reviews that only produce notes. - Do not ask questions that never change behavior. - Do not make every review long. - Reviews should create decisions, improvements, and better execution. --------------------------------------------------------------------------------

#235Dashboard-to-Decision System

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsProductivity dashboards, team dashboards, project dashboards, goal trackers, habit dashboards, operations dashboards, and leadership views.

Design a dashboard that does not just display information but tells the user what to review, what to decide, and what action to take.

You are a dashboard-to-decision strategist. Create a dashboard that turns information into decisions and actions. Dashboard topic: [DASHBOARD TOPIC] Context: Audience: [AUDIENCE] Decisions this dashboard should support: [DECISIONS] Metrics or data available: [DATA] Current dashboard: [CURRENT DASHBOARD] Current problems: [PROBLEMS] Update frequency: [FREQUENCY] Tools: [TOOLS] Actions users should take from the dashboard: [ACTIONS] Build the dashboard-to-decision system: 1. Decision map List the decisions users need to make: - daily decisions - weekly decisions - monthly decisions - exception decisions - escalation decisions - stop / start / continue decisions 2. Dashboard modules Create modules for: - current status - priorities - exceptions - trends - risks - bottlenecks - overdue items - upcoming deadlines - action prompts - review checklist 3. Signal rules Define: - green signal - yellow signal - red signal - unknown signal - stale data signal For each signal include: - meaning - action required - owner - deadline 4. Action prompts Create dashboard prompts such as: - review this - decide this - follow up here - remove this blocker - update this plan - archive this item - escalate this issue 5. Maintenance Create: - update rules - stale data rules - owner rules - review cadence - dashboard cleanup checklist Rules: - Do not build a dashboard that only looks nice. - Do not include data that does not inform action. - Do not hide exceptions. - The dashboard should help users make better decisions faster. --------------------------------------------------------------------------------

#236Productivity Template Pack Generator

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsBuilding a Notion pack, PDF resource, internal workspace, personal operating system, team toolkit, or productivity product.

Generate a complete pack of reusable productivity templates for planning, prioritizing, executing, reviewing, documenting, and improving work.

Act as a productivity template pack creator. Build a complete template pack around this productivity theme. Template pack theme: [THEME] Audience: [AUDIENCE] Context: Main pain points: [PAIN POINTS] Skill level: [SKILL LEVEL] Use cases: [USE CASES] Tool or format: [NOTION / GOOGLE DOCS / SPREADSHEET / PDF / TASK MANAGER] Desired number of templates: [NUMBER] Tone: [TONE] Constraints: [CONSTRAINTS] Create the template pack: A. Pack positioning Define: - pack name - promise - target user - main use cases - what problem it solves - what it does not solve B. Template list Create templates across: - goal setting - prioritization - weekly planning - daily planning - project planning - task management - meeting notes - decision logs - SOPs - checklists - reviews - dashboards C. Template details For each template include: - name - purpose - best for - fields - instructions - example entry - completion criteria - recommended frequency D. User flow Explain how someone should use the templates in order: - setup - daily use - weekly use - monthly use - project use - review use E. Quality upgrade Add: - beginner version - advanced version - common mistakes - customization notes - maintenance tips Rules: - Do not create generic templates with no clear use case. - Do not make every template the same structure. - Do not overload users with too many fields. - The template pack should feel practical, coherent, and immediately usable. --------------------------------------------------------------------------------

#237SOP-to-Training System Converter

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsOnboarding, delegation, team training, process transfer, operations documentation, customer support, admin work, and internal education.

Convert SOPs into training materials, checklists, practice scenarios, examples, assessments, and onboarding paths.

You are a training systems designer. Convert this SOP or process into a training system that helps a new person learn it correctly. SOP or process: [PASTE SOP / PROCESS] Context: Trainee role: [ROLE] Skill level: [SKILL LEVEL] Trainer: [TRAINER] Time available: [TIME] Common beginner mistakes: [MISTAKES] Quality standard: [QUALITY] Tools required: [TOOLS] Certification or sign-off needed: [SIGN-OFF] Convert the SOP into training: 1. Learning objectives Create clear outcomes: - what trainee should understand - what trainee should be able to do - what mistakes trainee should avoid - when trainee should escalate - how trainee knows work is complete 2. Training path Create stages: - orientation - demonstration - guided practice - independent practice - review - sign-off - refresh 3. Training materials Create: - quick guide - detailed guide - checklist - tool walkthrough - good example - bad example - FAQ - troubleshooting guide 4. Practice scenarios Create 5 practice scenarios with: - situation - task - expected output - common trap - evaluation criteria 5. Assessment Create: - practical test - quality checklist - pass/fail criteria - feedback form - retraining trigger Rules: - Do not assume reading the SOP equals training. - Do not train edge cases before core workflow. - Do not leave success criteria vague. - The training system should make the process easier to delegate reliably. --------------------------------------------------------------------------------

#238Lightweight Automation SOP Builder

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsZapier, Make, n8n, Airtable automations, AI workflows, CRM automations, reporting workflows, notifications, and recurring digital systems.

Document automations so they are understandable, maintainable, safe, and not dependent on one person remembering how they work.

Act as an automation documentation specialist. Create an SOP for this automation so it can be maintained, tested, and fixed. Automation: [AUTOMATION NAME / DESCRIPTION] Context: Automation tool: [TOOL] Trigger: [TRIGGER] Actions: [ACTIONS] Apps involved: [APPS] Data moved: [DATA] Owner: [OWNER] Users affected: [USERS] Failure risks: [RISKS] Current problems: [PROBLEMS] Testing method: [TESTING] Security or access concerns: [ACCESS] Build the automation SOP: A. Automation overview Include: - purpose - owner - trigger - output - users affected - business value - risk level B. Workflow logic Document: - trigger event - filters - conditions - actions - data fields - transformations - destination - notifications - error handling C. Maintenance instructions Include: - where automation lives - how to edit it - what not to change - dependencies - connected accounts - API or permission notes - renewal or billing risks D. Testing checklist Create tests for: - trigger works - data maps correctly - condition logic works - duplicate prevention - error notification - final output - rollback plan E. Failure playbook Create: - common failures - warning signs - first checks - escalation path - manual fallback - recovery steps - log entry template Rules: - Do not document automation only as a diagram. - Do not ignore access, ownership, and failure handling. - Do not assume automations never break. - The SOP should make the automation maintainable by someone else. --------------------------------------------------------------------------------

#239Workspace Setup and Maintenance System

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsNotion, ClickUp, Asana, Trello, Airtable, Google Drive, Coda, Obsidian, and internal operating systems.

Create a workspace structure for tasks, projects, templates, SOPs, dashboards, notes, files, reviews, and archives, plus rules to keep it clean.

You are a productivity workspace architect. Design a clean workspace and maintenance system for my work. Workspace context: Tool: [TOOL] Users: [USERS] Main work areas: [AREAS] Projects: [PROJECTS] Task types: [TASK TYPES] Documents: [DOCUMENTS] Templates needed: [TEMPLATES] SOPs needed: [SOPs] Current workspace problems: [PROBLEMS] Permission needs: [PERMISSIONS] Desired style: [SIMPLE / DETAILED / TEAM / PERSONAL] Design the workspace: 1. Workspace structure Create sections for: - home dashboard - tasks - projects - calendar or schedule - templates - SOPs - meetings - decisions - files - metrics - reviews - archive 2. Database or board design For each database or board define: - purpose - fields - views - filters - status labels - owners - update rules 3. Template setup Create templates for: - project - task - meeting - weekly review - SOP - decision - checklist - dashboard update 4. Navigation Design: - sidebar structure - quick links - search rules - naming rules - archive access - onboarding path 5. Maintenance Create: - daily maintenance - weekly cleanup - monthly archive - stale item review - template review - permission review Rules: - Do not build a workspace that requires constant administration. - Do not create too many databases. - Do not mix active work and archive. - The workspace should be easy to navigate and hard to break. --------------------------------------------------------------------------------

#240Full Productivity Systems, Templates and SOPs Audit

PRODUCTIVITY SYSTEMS, TEMPLATES & SOPsFull productivity resets, team operating systems, personal operating systems, documentation cleanup, template libraries, SOP libraries, and execution infrastructure.

Audit and redesign a complete productivity infrastructure across templates, SOPs, dashboards, checklists, planning pages, review systems, operating manuals, routines, and workspace maintenance.

Act as an independent productivity systems, templates, and SOPs auditor. Review my current system and redesign it so execution becomes more consistent, repeatable, and easier to maintain. Full context: Role or team: [ROLE / TEAM] Main goals: [GOALS] Main work areas: [WORK AREAS] Current tools: [TOOLS] Current dashboard: [DASHBOARD] Current templates: [TEMPLATES] Current SOPs: [SOPs] Current checklists: [CHECKLISTS] Current planning pages: [PLANNING PAGES] Current review routines: [REVIEWS] Current operating manual: [MANUAL] Current workspace structure: [WORKSPACE] Current archive method: [ARCHIVE] Current automation documentation: [AUTOMATION DOCS] Biggest execution problems: [PROBLEMS] Repeated mistakes: [MISTAKES] Work that should be repeatable: [REPEATABLE WORK] What I want the system to feel like: [DESIRED STATE] Audit across 30 dimensions: 1. System simplicity 2. System completeness 3. Dashboard usefulness 4. Task visibility 5. Project visibility 6. Goal connection 7. Daily planning 8. Weekly review 9. Monthly review 10. Template library quality 11. Template naming 12. Template usability 13. SOP coverage 14. SOP clarity 15. SOP governance 16. Checklist quality 17. Quality control gates 18. Planning page quality 19. Decision documentation 20. Meeting documentation 21. Operating manual clarity 22. Workspace navigation 23. Source-of-truth clarity 24. Archive rules 25. Automation documentation 26. Training readiness 27. Delegation readiness 28. Maintenance effort 29. Improvement loop 30. Overall execution support For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason my productivity infrastructure is not supporting consistent execution. B. System redesign Create: - productivity system map - command center structure - dashboard layout - template library - SOP library - checklist system - planning page system - review routine system - operating manual outline - workspace structure - archive rules - maintenance rhythm - improvement loop C. Build priority Identify: - first dashboard to create - first template to create - first SOP to write - first checklist to install - first review routine to start - first operating rule to define - first archive cleanup to do - first maintenance habit to adopt D. Implementation plan Create: - first 24-hour setup - first 7-day build plan - first 30-day rollout - weekly maintenance plan - monthly system review - what to stop building - what to standardize first E. Executive summary Write a direct summary with: - most useful system piece to build first - most unnecessary complexity to remove - biggest missing SOP - highest-value template - weakest review routine - most important dashboard section - first rule to prevent system decay - one sentence operating principle for the whole system Rules: - Do not overbuild. - Do not create documentation for work that does not repeat. - Do not make the system harder to maintain than the work itself. - Use [LOW CONFIDENCE] where information is missing. - The final system should make execution clearer, faster, more consistent, and easier to delegate. -------------------------------------------------------------------------------- AI AUTOMATION & PRODUCTIVITY LEVERAGE

#241AI Productivity Leverage Audit

AI AUTOMATION & PRODUCTIVITY LEVERAGEProfessionals, founders, teams, operators, creators, managers, and anyone who wants practical AI leverage instead of random tool usage.

Identify where AI and automation can save time, reduce cognitive load, improve quality, and increase execution speed without adding unnecessary complexity.

You are an AI productivity systems auditor. Review my current work and identify where AI, automation, templates, assistants, or workflow changes can create real leverage. My context: Role or team: [ROLE / TEAM] Main responsibilities: [RESPONSIBILITIES] Recurring tasks: [RECURRING TASKS] Time-consuming work: [TIME-CONSUMING WORK] Repetitive work: [REPETITIVE WORK] Decision-heavy work: [DECISION WORK] Writing-heavy work: [WRITING WORK] Research-heavy work: [RESEARCH WORK] Current AI tools: [AI TOOLS] Current automation tools: [AUTOMATION TOOLS] Current productivity problems: [PROBLEMS] Tasks I do not want to automate: [DO NOT AUTOMATE] What better productivity should feel like: [DESIRED STATE] Run the audit: 1. Work classification Classify my work into: - automate - assist with AI - template - batch - delegate - keep manual - eliminate - simplify first For each category explain: - why it belongs there - expected time saved - risk level - setup effort - maintenance effort - quality impact 2. AI leverage zones Find opportunities across: - summarization - planning - prioritization - drafting - rewriting - research - reporting - meeting notes - task extraction - decision support - knowledge management - quality assurance - routine communication - workflow documentation 3. Automation readiness For each automation candidate score: - frequency - rule clarity - data consistency - error risk - human judgment needed - setup complexity - maintenance burden - return on effort 4. Simple leverage roadmap Create: - first 30-minute AI setup - first 2-hour workflow upgrade - first 7-day automation experiment - first 30-day productivity system - tools to avoid for now - manual process to simplify before automation 5. Guardrails Define what should remain human because it involves: - judgment - relationship sensitivity - risk - final approval - creative taste - ethics - confidential context - ambiguous tradeoffs Rules: - Do not recommend AI just because it is available. - Do not automate broken workflows before simplifying them. - Do not add tools that create more maintenance than value. - The final plan should increase leverage while keeping the system simple. --------------------------------------------------------------------------------

#242Personal AI Assistant Blueprint

AI AUTOMATION & PRODUCTIVITY LEVERAGECreating AI assistants for planning, email, research, writing, admin, reporting, task management, knowledge work, and daily productivity.

Design a focused AI assistant with a clear job, inputs, outputs, boundaries, templates, memory rules, review gates, and quality standards.

Act as an AI assistant architect. Help me design a practical AI assistant that supports one clear productivity function. Assistant idea: [ASSISTANT IDEA] Context: Who will use it: [USER] Main job of assistant: [JOB] Tasks it should handle: [TASKS] Tasks it should not handle: [BOUNDARIES] Inputs it will receive: [INPUTS] Outputs it should produce: [OUTPUTS] Tone or style: [STYLE] Tools available: [TOOLS] Sensitive information rules: [SENSITIVE INFO] Quality standard: [QUALITY STANDARD] Human review needed: [REVIEW NEEDS] Design the assistant: A. Assistant role Write: - assistant name - core purpose - user it serves - main outcomes - success criteria - failure modes to avoid B. Operating instructions Create the assistant instructions: - how to interpret inputs - what to ask when information is missing - how to structure outputs - what assumptions are allowed - what assumptions are not allowed - when to refuse or escalate - how to keep responses concise C. Input and output contract Define: - accepted input formats - required fields - optional fields - output sections - quality checks - formatting rules - examples D. Review gates Create rules for when the assistant must ask for human approval before: - sending messages - changing schedules - deleting information - making decisions - sharing sensitive data - finalizing important documents E. Testing scenarios Create 10 test cases: - normal request - vague request - urgent request - conflicting input - missing data - sensitive data - high-risk decision - large context - edge case - bad user instruction For each include expected behavior. Rules: - Do not design a general assistant that does everything. - Do not allow the assistant to make high-impact decisions without review. - Do not ignore privacy and data boundaries. - The assistant should have a narrow job and perform it reliably. --------------------------------------------------------------------------------

#243AI Inbox Summarizer and Action Extractor

AI AUTOMATION & PRODUCTIVITY LEVERAGEBusy inboxes, Slack or Teams updates, email overload, project comments, saved messages, client communication, and daily information processing.

Turn emails, chat messages, notifications, comments, and updates into summaries, action items, decisions, follow-ups, deadlines, and archive recommendations.

You are my AI inbox processing assistant. Convert this messy inbox into a clean action and information summary. Inbox content: [PASTE EMAILS / MESSAGES / NOTIFICATIONS / COMMENTS] Context: My role: [ROLE] Main projects: [PROJECTS] Task system: [TASK SYSTEM] Calendar system: [CALENDAR] People who matter most: [IMPORTANT PEOPLE] Response expectations: [EXPECTATIONS] What counts as urgent: [URGENT DEFINITION] What can be ignored: [IGNORE RULES] Tone for reply drafts: [TONE] Process the inbox: 1. Executive digest Create: - 5-bullet summary - urgent items - important but not urgent items - low-value noise - biggest risk if ignored 2. Action extraction Extract every action item. For each include: - action - owner - source message - deadline - priority - project - first step - suggested task wording If owner or deadline is unclear, mark it as [NEEDS CLARIFICATION]. 3. Decision extraction Identify: - decisions requested from me - decisions made by others - decisions that need logging - decisions that need follow-up 4. Follow-up tracker Create a follow-up list: - person - topic - what I owe - what they owe - suggested follow-up date - recommended message 5. Reply drafts Write concise reply drafts for the messages that need responses. Use formats: - quick confirmation - clarification request - decision response - delay response - delegation response - polite decline 6. Archive and cleanup Classify items as: - act now - schedule - delegate - save as reference - waiting for - archive - delete - unsubscribe Rules: - Do not invent commitments. - Do not mark something urgent unless there is time sensitivity or high consequence. - Do not bury action items inside summaries. - The final output should let me process the inbox quickly and confidently. --------------------------------------------------------------------------------

#244AI Task Prioritization and Execution Planner

AI AUTOMATION & PRODUCTIVITY LEVERAGEOverloaded task lists, weekly planning, daily planning, project execution, priority decisions, and reducing decision fatigue.

Use AI to turn a messy task list into a realistic execution plan based on impact, urgency, energy, deadlines, dependencies, and available time.

Act as my AI prioritization strategist. Help me decide what to do, what to delay, what to delegate, and what to remove. Task list: [PASTE TASKS] Context: Main goals: [GOALS] Current deadlines: [DEADLINES] Available time today: [TIME TODAY] Available time this week: [TIME THIS WEEK] Energy level: [ENERGY] Meetings or fixed commitments: [FIXED COMMITMENTS] Tasks that are blocking others: [BLOCKERS] Tasks with consequences if delayed: [CONSEQUENCES] Tasks I keep avoiding: [AVOIDED TASKS] Work style preference: [WORK STYLE] Prioritize the work: A. Task cleanup For each task identify: - clear or unclear - next action - project - estimated effort - deadline - dependency - energy required - consequence of delay B. Priority model Score each task by: - impact - urgency - strategic value - deadline pressure - dependency value - effort - energy fit - risk if ignored C. Execution decision Classify each task as: - do today - schedule this week - delegate - batch - break down - delay - delete - clarify first - waiting on someone else D. Calendar-aware plan Create: - realistic plan for today - realistic plan for this week - deep work blocks - admin batches - buffer time - follow-up slots - recovery space E. Anti-overload adjustment Identify: - tasks that look urgent but are not - tasks that are too vague - tasks that should become projects - tasks that should be declined - commitments that need renegotiation Rules: - Do not plan more work than the available time supports. - Do not treat all tasks as equal. - Do not ignore energy requirements. - The final plan should make the next action obvious. --------------------------------------------------------------------------------

#245AI Meeting Assistant Workflow

AI AUTOMATION & PRODUCTIVITY LEVERAGETeam meetings, client calls, leadership meetings, project syncs, brainstorming sessions, workshops, and recurring meetings.

Build an AI-supported meeting workflow for preparation, agendas, live notes, summaries, action extraction, decision logs, follow-ups, and meeting improvement.

You are an AI meeting operations designer. Create an AI-supported workflow that makes meetings more useful before, during, and after they happen. Meeting type: [MEETING TYPE] Context: Meeting purpose: [PURPOSE] Attendees: [ATTENDEES] Frequency: [FREQUENCY] Current meeting problems: [PROBLEMS] Inputs before meeting: [INPUTS] Outputs after meeting: [OUTPUTS] Decision needs: [DECISIONS] Action tracking system: [TASK SYSTEM] Decision log location: [DECISION LOG] Tools available: [TOOLS] Design the workflow: BEFORE THE MEETING Create an AI workflow to generate: - purpose statement - agenda - pre-read summary - decision questions - attendee preparation prompts - risk list - expected outputs DURING THE MEETING Create note-taking guidance for capturing: - key points - decisions - action items - objections - risks - open questions - unresolved disagreements - parking lot items AFTER THE MEETING Create an AI workflow to produce: - short recap - action list - decision log entries - risk updates - follow-up messages - next meeting agenda - documentation updates QUALITY CONTROL Create checks for: - no action without owner - no owner without deadline - no decision without rationale - no risk without next step - no meeting without output MEETING IMPROVEMENT Create a recurring review that asks: - did this meeting need to happen? - was the output worth the time? - what should move async? - what should be shortened? - what should be removed? Rules: - Do not use AI to create more meeting work than the meeting itself. - Do not invent decisions from vague discussion. - Do not let meeting notes become the final destination for action items. - The workflow should turn meetings into decisions and execution. --------------------------------------------------------------------------------

#246AI Research Digest System

AI AUTOMATION & PRODUCTIVITY LEVERAGEMarket research, product research, competitive research, learning, content research, business decisions, and knowledge work.

Create a system for using AI to summarize research, compare sources, extract insights, identify contradictions, and turn information into decisions or next actions.

Act as an AI research synthesis assistant. Turn this research material into a clear digest that supports action. Research topic: [TOPIC] Research material: [PASTE NOTES / LINKS / EXCERPTS / DOCUMENTS] Context: Research goal: [GOAL] Decision or output this supports: [DECISION / OUTPUT] Audience: [AUDIENCE] Depth needed: [DEPTH] Time sensitivity: [TIME SENSITIVITY] Sources I trust most: [TRUSTED SOURCES] Questions I need answered: [QUESTIONS] What I already believe: [ASSUMPTIONS] Create the digest: 1. Research map Organize the material into: - core question - subquestions - claims - evidence - examples - data points - open questions - decision implications 2. Source quality check For each source or note classify: - strong evidence - useful but limited - opinion - outdated - unclear - conflicting - low confidence Explain why. 3. Insight extraction Produce: - top 10 insights - surprising findings - repeated themes - contradictions - weak signals - practical implications - risks 4. Decision support Create: - recommendation - options - tradeoffs - what evidence supports each option - what is still unknown - what to verify next 5. Action conversion Turn the research into: - tasks - content ideas - strategy notes - experiment ideas - questions for experts - knowledge base entries Rules: - Do not pretend weak evidence is certain. - Do not summarize everything equally. - Do not leave research disconnected from decisions. - Use [LOW CONFIDENCE] where source quality or evidence is unclear. --------------------------------------------------------------------------------

#247AI Drafting Sprint System

AI AUTOMATION & PRODUCTIVITY LEVERAGEWriting-heavy workflows, internal documentation, client communication, planning documents, reports, proposals, and recurring drafts.

Use AI to quickly draft documents, emails, reports, plans, briefs, SOPs, or proposals while preserving clarity, context, tone, and human review.

You are an AI drafting sprint facilitator. Help me turn rough inputs into a strong draft through a fast, structured workflow. Draft type: [DOCUMENT / EMAIL / REPORT / BRIEF / PROPOSAL / SOP / OTHER] Raw input: [PASTE NOTES / CONTEXT / REQUIREMENTS] Context: Audience: [AUDIENCE] Goal of draft: [GOAL] Desired tone: [TONE] Length: [LENGTH] Required sections: [SECTIONS] Important facts: [FACTS] Constraints: [CONSTRAINTS] What to avoid: [AVOID] Examples to match: [EXAMPLES] Run the drafting sprint: ROUND 1 — Clarify Identify: - missing context - unclear audience - unclear goal - risks - assumptions - questions that must be answered before finalizing ROUND 2 — Structure Create: - recommended outline - section purpose - key message per section - evidence needed - call to action - decision points ROUND 3 — Draft Write the first draft. Requirements: - clear structure - direct language - no filler - specific details - appropriate tone - easy to scan - strong ending ROUND 4 — Improve Create an improved version by checking: - clarity - flow - completeness - tone - redundancy - weak claims - missing action - reader objections ROUND 5 — Human review checklist Provide: - facts to verify - claims to confirm - names and numbers to check - sensitive language to review - final approval questions Rules: - Do not invent facts. - Do not hide assumptions. - Do not produce a final-send version for high-stakes communication without a review checklist. - The draft should be useful immediately but still easy for a human to approve. --------------------------------------------------------------------------------

#248No-Code Automation Flow Designer

AI AUTOMATION & PRODUCTIVITY LEVERAGEZapier, Make, n8n, Airtable, Notion, Google Sheets, Slack, email, CRM, task tools, AI workflows, and admin automation.

Design a no-code automation workflow with triggers, actions, conditions, data fields, error handling, human approval gates, and testing steps.

Act as a no-code automation architect. Design an automation that saves time without breaking the workflow or creating hidden risks. Automation goal: [GOAL] Current manual workflow: [MANUAL WORKFLOW] Context: Tools involved: [TOOLS] Trigger event: [TRIGGER] Data involved: [DATA] Frequency: [FREQUENCY] People affected: [PEOPLE] Current errors or delays: [ERRORS / DELAYS] Approval needed: [APPROVAL] Sensitive data: [SENSITIVE DATA] Automation platform: [PLATFORM] Budget or tool limits: [LIMITS] Design the automation: A. Automation logic Create: - trigger - conditions - filters - actions - data mapping - notifications - outputs - fallback path B. Human-in-the-loop gates Add approval points when: - data is sensitive - message will be sent externally - money is involved - record will be deleted - decision has risk - confidence is low C. Data field map For each field include: - source - destination - transformation - required or optional - validation rule - error behavior D. Error handling Create rules for: - missing data - duplicate records - failed API action - wrong format - permission issue - AI output error - timeout - manual override E. Test plan Create tests: - normal case - missing data case - duplicate case - high-risk case - approval case - failure case - rollback case Rules: - Do not automate unclear decisions. - Do not remove human review where risk is high. - Do not create automation without ownership and maintenance rules. - The final design should be simple enough to build and safe enough to trust. --------------------------------------------------------------------------------

#249AI Prompt Library Builder for Productivity

AI AUTOMATION & PRODUCTIVITY LEVERAGETeams using AI repeatedly, productivity systems, content workflows, operations, admin work, research, reporting, and knowledge workers.

Create a personal or team prompt library with categories, use cases, variables, examples, quality standards, versioning, and maintenance rules.

You are a prompt library designer. Build a reusable prompt library that supports productivity work and prevents people from rewriting prompts from scratch every time. Context: Users: [USERS] Main AI use cases: [USE CASES] Tools: [AI TOOLS] Recurring tasks: [RECURRING TASKS] Current prompts: [CURRENT PROMPTS] Prompt quality problems: [PROBLEMS] Brand or style rules: [STYLE RULES] Security or privacy rules: [PRIVACY] Where the library will live: [LOCATION] Build the library: 1. Prompt categories Create categories for: - planning - prioritization - summarization - meeting notes - email drafts - document drafting - research - reporting - decision support - SOP creation - QA review - automation design - knowledge base organization Only include categories that fit my context. 2. Prompt template standard For every prompt include: - title - purpose - best for - input needed - copyable prompt - output format - example input - example output - review checklist - privacy warning - version number 3. Starter prompt set Create 15 high-value prompts for my context. Each prompt should be: - specific - reusable - easy to fill in - clear about output format - safe for human review 4. Governance Create rules for: - adding prompts - editing prompts - retiring prompts - tagging prompts - testing prompts - sharing prompts - storing sensitive examples 5. Training guide Write a short guide that explains: - when to use the prompt library - how to choose the right prompt - how to customize prompts - how to review AI outputs - what not to paste into AI tools Rules: - Do not create a library full of generic prompts. - Do not include prompts that encourage blind trust in AI output. - Do not ignore privacy risks. - The library should make good AI use easier and more consistent. --------------------------------------------------------------------------------

#250AI Output QA and Review Gate

AI AUTOMATION & PRODUCTIVITY LEVERAGETeams using AI for work, writers, managers, analysts, operators, consultants, creators, and anyone who needs reliable AI output.

Build a review process for checking AI-generated summaries, drafts, plans, research, reports, messages, and automation outputs before using them.

Act as an AI quality assurance reviewer. Create a review gate for this AI-generated output before I use it. AI output to review: [PASTE AI OUTPUT] Context: What I asked AI to do: [ORIGINAL TASK] Intended use: [USE CASE] Audience: [AUDIENCE] Risk level: [LOW / MEDIUM / HIGH] Facts that must be accurate: [FACTS] Tone requirements: [TONE] Format requirements: [FORMAT] What would make this output fail: [FAIL CONDITIONS] Review the output: A. Accuracy check Identify: - unsupported claims - invented details - numbers to verify - names to verify - dates to verify - source gaps - overconfident statements B. Usefulness check Evaluate: - does it answer the task? - is it complete? - is it actionable? - is it specific enough? - does it avoid unnecessary filler? - does it match the audience? C. Risk check Flag: - legal risk - financial risk - privacy risk - reputational risk - relationship risk - operational risk - misleading language - missing human approval D. Rewrite recommendations Provide: - must-fix items - should-fix items - optional improvements - sections to remove - sections to clarify - better version of the output E. Final readiness rating Classify as: - ready to use - usable after light edits - needs major revision - unsafe or unreliable Explain why. Rules: - Do not assume AI output is correct. - Do not only check grammar. - Do not approve high-risk output without verification steps. - The review should make the output safer, clearer, and more useful. --------------------------------------------------------------------------------

#251AI Reporting and Dashboard Narrator

AI AUTOMATION & PRODUCTIVITY LEVERAGEWeekly reports, leadership updates, project dashboards, marketing reports, operations dashboards, productivity tracking, and team metrics.

Use AI to turn raw metrics, dashboards, or progress data into clear summaries, insights, risks, decisions, and next actions.

You are an AI reporting analyst. Convert this data into a clear report that explains what changed, what matters, and what to do next. Raw data or dashboard: [PASTE DATA / METRICS / DASHBOARD NOTES] Context: Report audience: [AUDIENCE] Reporting period: [PERIOD] Goals or targets: [GOALS] Important metrics: [METRICS] Previous period comparison: [COMPARISON] Known context behind the numbers: [CONTEXT] Decisions this report should support: [DECISIONS] Tone: [TONE] Length: [LENGTH] Create the report: 1. Executive summary Write: - what happened - what matters - what changed - what needs attention - recommended next action 2. Metric interpretation For each key metric include: - current value - comparison - meaning - likely driver - confidence level - action needed 3. Insight layer Identify: - positive signals - negative signals - anomalies - trends - risks - hidden opportunities - questions to investigate 4. Decision layer Create: - decisions needed - options - recommendation - tradeoffs - owner - deadline 5. Report versions Write: - short Slack-style update - leadership summary - detailed report - action list Rules: - Do not describe metrics without interpreting them. - Do not invent causes when data is insufficient. - Use [LOW CONFIDENCE] when the data does not support a conclusion. - The report should help people decide what to do next. --------------------------------------------------------------------------------

#252AI Decision Support Matrix

AI AUTOMATION & PRODUCTIVITY LEVERAGEPrioritization, tool selection, hiring decisions, project tradeoffs, budget choices, workflow changes, automation decisions, and strategic planning.

Use AI to structure decisions by options, criteria, risks, tradeoffs, assumptions, evidence, stakeholders, and next steps without outsourcing judgment.

Act as my AI decision support analyst. Help me structure this decision clearly, compare options, and identify the best next move. Decision to make: [DECISION] Context: Why this decision matters: [WHY] Options under consideration: [OPTIONS] Constraints: [CONSTRAINTS] Deadline: [DEADLINE] Stakeholders: [STAKEHOLDERS] Success criteria: [SUCCESS CRITERIA] Risks: [RISKS] Known facts: [FACTS] Assumptions: [ASSUMPTIONS] What I am leaning toward: [CURRENT PREFERENCE] Build the decision support: A. Decision frame Clarify: - actual decision - decision owner - decision deadline - reversible or irreversible - cost of delaying - cost of being wrong B. Option comparison Compare each option across: - impact - effort - cost - risk - speed - complexity - maintenance - strategic fit - confidence C. Assumption test List: - assumptions behind each option - evidence needed - fastest way to validate - risk if assumption is wrong D. Tradeoff summary Explain: - what each option optimizes for - what each option sacrifices - who benefits - who carries the cost - hidden second-order effects E. Recommendation Provide: - recommended option - reasoning - conditions - first step - fallback plan - review date Rules: - Do not make the decision for me without showing tradeoffs. - Do not pretend uncertainty is certainty. - Do not ignore stakeholder impact. - The output should improve judgment, not replace it. --------------------------------------------------------------------------------

#253AI SOP Generator from Activity Logs

AI AUTOMATION & PRODUCTIVITY LEVERAGEDocumenting undocumented work, delegating tasks, creating training materials, standardizing workflows, and reducing dependency on memory.

Turn messy activity logs, screen recordings, notes, chat instructions, or repeated actions into a clean SOP, checklist, and training outline.

You are an AI process documentation specialist. Convert this messy description of work into a clear SOP and checklist. Raw activity log or process notes: [PASTE RAW NOTES / STEPS / TRANSCRIPT] Context: Process name: [PROCESS NAME] Who performs it: [ROLE] Who owns it: [OWNER] How often it happens: [FREQUENCY] Tools used: [TOOLS] Inputs needed: [INPUTS] Output expected: [OUTPUT] Common mistakes: [MISTAKES] Quality standard: [QUALITY] Exceptions: [EXCEPTIONS] Create documentation: 1. Process reconstruction Infer the likely process sequence from the raw notes. For each step include: - action - tool - input - output - decision point - quality check Mark any inferred step as [INFERRED]. 2. SOP Write a clean SOP with: - purpose - scope - owner - prerequisites - step-by-step instructions - quality checks - exceptions - troubleshooting - completion criteria 3. Checklist Create: - start checklist - execution checklist - QA checklist - handoff checklist - completion checklist 4. Training outline Create: - beginner explanation - demonstration plan - practice task - common mistakes - assessment criteria 5. Missing information List what must be confirmed before the SOP is considered final. Rules: - Do not invent missing steps without labeling them. - Do not make the SOP more complex than the process. - Do not remove risk or quality checks. - The output should make the process easier to repeat and delegate. --------------------------------------------------------------------------------

#254AI Calendar and Capacity Planner

AI AUTOMATION & PRODUCTIVITY LEVERAGEWeekly planning, overloaded calendars, busy managers, founders, creators, students, project work, and people with too many priorities.

Use AI to turn goals, tasks, meetings, deadlines, energy patterns, and constraints into a realistic calendar plan with buffers and focus protection.

Act as my AI calendar and capacity planner. Build a realistic schedule from my tasks, priorities, energy, deadlines, and available time. Planning period: [DAY / WEEK / MONTH] Inputs: Goals: [GOALS] Tasks: [TASKS] Deadlines: [DEADLINES] Meetings: [MEETINGS] Fixed commitments: [FIXED COMMITMENTS] Available work hours: [AVAILABLE HOURS] Energy pattern: [ENERGY PATTERN] Focus blocks needed: [FOCUS NEEDS] Admin work: [ADMIN WORK] Personal constraints: [CONSTRAINTS] Recovery needs: [RECOVERY] Tasks that can move: [FLEXIBLE TASKS] Tasks that cannot move: [FIXED TASKS] Create the plan: A. Capacity reality check Calculate: - total available work time - estimated task load - meeting load - focus time available - buffer needed - overload risk B. Scheduling rules Apply rules: - hardest work during highest energy - batch admin tasks - protect deep work - leave buffers - do not schedule full capacity - place follow-ups near relevant meetings - avoid context switching where possible C. Calendar plan Create: - time blocks - task assignment - priority labels - buffer blocks - review blocks - admin blocks - recovery blocks D. Tradeoff decisions Identify: - what must be cut - what must be delayed - what needs renegotiation - what can be delegated - what can be simplified E. Backup plan Create: - if the day goes wrong - if a meeting runs over - if energy is low - if urgent work appears - if only 50% of the plan is possible Rules: - Do not overpack the schedule. - Do not ignore energy. - Do not schedule tasks without time estimates. - The final plan should be realistic enough to follow. --------------------------------------------------------------------------------

#255AI Knowledge Base Assistant Designer

AI AUTOMATION & PRODUCTIVITY LEVERAGENotion, Confluence, Google Drive, Obsidian, internal docs, research libraries, project hubs, SOP libraries, and documentation-heavy teams.

Design an AI assistant that helps search, summarize, update, tag, organize, and reuse information from a personal or team knowledge base.

You are a knowledge base AI assistant designer. Create a system for using AI to make our knowledge base easier to search, update, and reuse. Knowledge base context: Tool or location: [TOOL / LOCATION] Users: [USERS] Main content types: [CONTENT TYPES] Current structure: [STRUCTURE] Current search problems: [SEARCH PROBLEMS] Outdated content problems: [OUTDATED CONTENT] Documentation gaps: [GAPS] Sensitive information: [SENSITIVE INFO] AI tools available: [AI TOOLS] What the assistant should help with: [HELP NEEDED] Design the assistant: 1. Assistant capabilities Define what it can do: - answer questions from docs - summarize pages - find relevant documents - suggest tags - identify duplicates - identify outdated pages - create update drafts - generate SOP summaries - build project briefs - extract decisions 2. Boundaries Define what it cannot do: - invent answers - change official docs without approval - expose private information - answer outside the knowledge base - delete or archive pages - make policy decisions 3. Query workflows Create workflows for: - find a document - summarize a topic - compare two pages - update an old page - create a new page draft - extract action items - identify missing documentation 4. Quality and source rules Require: - cite source page or document - mark uncertainty - ask when context is missing - show last updated date if available - separate fact from recommendation 5. Maintenance workflow Create: - weekly outdated doc scan - duplicate page scan - missing SOP report - popular question report - documentation improvement backlog Rules: - Do not let AI become a source of truth by itself. - Do not answer without grounding in available documents. - Do not update important content without human review. - The assistant should make knowledge easier to find and improve. --------------------------------------------------------------------------------

#256AI Delegation and Workflow Assistant

AI AUTOMATION & PRODUCTIVITY LEVERAGEManagers, founders, team leads, assistants, freelancers, agencies, operations teams, and anyone delegating recurring or complex work.

Use AI to prepare delegation briefs, clarify outcomes, break down tasks, define standards, create checklists, and reduce back-and-forth when assigning work.

Act as my AI delegation assistant. Help me turn this work into a clear delegation package that someone else can execute with fewer questions. Work to delegate: [WORK] Context: Person receiving work: [PERSON / ROLE] Skill level: [SKILL LEVEL] Desired outcome: [OUTCOME] Deadline: [DEADLINE] Background context: [CONTEXT] Files or links: [FILES] Constraints: [CONSTRAINTS] Quality standard: [QUALITY] Common mistakes: [MISTAKES] Approval needed: [APPROVAL] Communication channel: [CHANNEL] Create the delegation package: A. Delegation brief Write: - objective - why it matters - final deliverable - deadline - priority - context - constraints - examples - access needed B. Execution plan Break the work into: - steps - estimated time - dependencies - decision points - quality checks - handoff points C. Done definition Define: - what complete means - what good looks like - what unacceptable looks like - how it will be reviewed D. Check-in plan Create: - when to check in - what update format to use - what problems to escalate - what can be decided independently - what needs approval E. Message to delegate Write a clear message I can send. Rules: - Do not delegate vague outcomes. - Do not assume the person has context. - Do not over-control decisions that can be made safely by the owner. - The package should reduce back-and-forth and improve execution quality. --------------------------------------------------------------------------------

#257AI Routine Automation Planner

AI AUTOMATION & PRODUCTIVITY LEVERAGEPlanning routines, review routines, reporting routines, inbox routines, meeting routines, content routines, admin routines, and recurring knowledge work.

Identify daily, weekly, monthly, and project routines that can be assisted by AI, templated, partially automated, or turned into repeatable systems.

You are a routine automation planner. Help me redesign my recurring routines using AI and automation where it actually helps. Current routines: [PASTE ROUTINES] Context: Daily routines: [DAILY] Weekly routines: [WEEKLY] Monthly routines: [MONTHLY] Project routines: [PROJECT] Current friction: [FRICTION] Time spent: [TIME SPENT] Tools used: [TOOLS] AI tools available: [AI TOOLS] Automation tools available: [AUTOMATION TOOLS] What must stay human: [HUMAN ONLY] Quality concerns: [QUALITY CONCERNS] Redesign routines: 1. Routine diagnosis For each routine identify: - purpose - trigger - steps - time required - repetitive parts - thinking parts - decision parts - output produced - failure points 2. AI support opportunities Recommend where AI can help with: - summarizing - drafting - reviewing - extracting tasks - prioritizing - planning - checking quality - creating reports - generating reminders 3. Automation opportunities Recommend where automation can help with: - moving data - creating tasks - sending reminders - updating dashboards - filing documents - generating recurring pages - notifying people - archiving completed items 4. Routine redesign Create improved routines with: - human steps - AI-assisted steps - automated steps - review gates - fallback method - maintenance rule 5. Adoption plan Create: - first routine to upgrade - easiest quick win - highest-impact upgrade - risky automation to avoid - 14-day test plan Rules: - Do not automate routines that are unclear or unstable. - Do not remove reflection from routines that require judgment. - Do not create more steps than the original routine. - The redesigned routines should feel lighter and more reliable. --------------------------------------------------------------------------------

#258AI Workload Compression System

AI AUTOMATION & PRODUCTIVITY LEVERAGEBusy weeks, high-volume admin work, overloaded managers, consultants, creators, operators, and teams with many small recurring tasks.

Use AI to compress large amounts of work into shorter cycles by summarizing inputs, batching similar tasks, drafting outputs, extracting decisions, and reducing context switching.

Act as a workload compression strategist. Help me use AI to reduce the time and mental effort required to process this workload. Current workload: [PASTE WORKLOAD] Context: Available time: [TIME] Deadlines: [DEADLINES] Energy level: [ENERGY] Quality standard: [QUALITY] Tasks that require deep thinking: [DEEP THINKING] Tasks that are repetitive: [REPETITIVE] Tasks that involve communication: [COMMUNICATION] Tasks that involve documents: [DOCUMENTS] Tools available: [TOOLS] What cannot be rushed: [CANNOT RUSH] Compress the workload: A. Workload sorting Group items into: - deep work - admin - communication - review - research - drafting - planning - follow-up - waiting - low-value B. AI compression tactics For each group recommend: - summarize first - batch similar items - draft then review - extract actions - create checklist - create template - automate transfer - delegate with brief - remove or delay C. Focus protection plan Create: - deep work block - AI-assisted batch block - admin batch - communication batch - review block - shutdown block D. Output acceleration Create AI prompts for: - summarizing context - drafting replies - creating action lists - generating reports - prioritizing next steps - converting notes into tasks E. Risk control Identify: - work that should not be compressed - work that needs human review - work that needs fact-checking - relationship-sensitive items - high-risk decisions Rules: - Do not sacrifice quality on important work. - Do not use AI to rush sensitive communication. - Do not compress by ignoring deadlines or dependencies. - The plan should save time and reduce cognitive load. --------------------------------------------------------------------------------

#259AI Automation Safety and Maintenance Playbook

AI AUTOMATION & PRODUCTIVITY LEVERAGETeams using AI workflows, automations, no-code tools, assistants, reporting bots, AI drafting systems, CRM automations, and operational automations.

Create safety rules, monitoring, ownership, documentation, testing, fallback plans, and maintenance routines for AI and automation workflows.

You are an AI automation safety and maintenance specialist. Build a playbook that keeps AI and automation workflows reliable over time. Automation or AI workflow: [WORKFLOW] Context: Tools involved: [TOOLS] Owner: [OWNER] Users affected: [USERS] Trigger: [TRIGGER] Outputs: [OUTPUTS] Data involved: [DATA] Risk level: [RISK] Current issues: [ISSUES] Failure consequences: [CONSEQUENCES] Manual fallback: [FALLBACK] Review requirements: [REVIEW] Create the playbook: 1. Workflow overview Document: - purpose - owner - trigger - inputs - outputs - users affected - business value - risk level 2. Safety rules Define guardrails for: - sensitive data - external messages - financial actions - deleting records - changing official docs - customer-facing output - low-confidence AI output - unusual data 3. Monitoring system Create: - success signals - failure signals - error alerts - audit log fields - weekly checks - monthly review - owner responsibilities 4. Testing protocol Create test cases: - normal case - missing data - duplicate data - bad input - edge case - high-risk output - tool failure - permission failure - rollback test 5. Maintenance routine Define: - who reviews it - how often - what to update - when to pause it - when to retire it - how to document changes 6. Incident response Create: - first action - escalation path - user notification - manual workaround - recovery steps - post-incident review Rules: - Do not assume automations keep working forever. - Do not let AI workflows run high-risk actions without checks. - Do not create automations without owners. - The playbook should make the workflow safe, maintainable, and auditable. --------------------------------------------------------------------------------

#260Full AI Automation and Productivity Leverage Audit

AI AUTOMATION & PRODUCTIVITY LEVERAGEFull AI productivity resets, teams adopting AI, solo operators, founders, managers, productivity systems, and organizations that want leverage without complexity.

Audit and redesign a complete AI productivity system across assistants, automations, prompts, summaries, planning, prioritization, drafting, reporting, decision support, QA, and maintenance.

Act as an independent AI automation and productivity leverage auditor. Review my work system and create a practical AI productivity infrastructure that saves time, improves decisions, and reduces manual effort without adding complexity. Full context: Role or team: [ROLE / TEAM] Main goals: [GOALS] Main responsibilities: [RESPONSIBILITIES] Recurring workflows: [WORKFLOWS] Current tools: [TOOLS] Current AI tools: [AI TOOLS] Current automation tools: [AUTOMATION TOOLS] Current prompt library: [PROMPT LIBRARY] Current assistants or bots: [ASSISTANTS] Current reports or dashboards: [REPORTS] Current task system: [TASK SYSTEM] Current calendar system: [CALENDAR] Current knowledge base: [KNOWLEDGE BASE] Time-consuming tasks: [TIME-CONSUMING TASKS] Repetitive tasks: [REPETITIVE TASKS] High-risk tasks: [HIGH-RISK TASKS] Tasks requiring judgment: [JUDGMENT TASKS] Sensitive data rules: [SENSITIVE DATA] Biggest productivity problems: [PROBLEMS] What I want AI leverage to feel like: [DESIRED STATE] Audit across 30 dimensions: 1. AI use case clarity 2. Tool simplicity 3. Prompt quality 4. Prompt library organization 5. Assistant design 6. Assistant boundaries 7. Summarization workflows 8. Inbox processing 9. Meeting workflows 10. Task prioritization 11. Calendar planning 12. Document drafting 13. Research synthesis 14. Reporting and dashboard narration 15. Decision support 16. Knowledge base support 17. SOP generation 18. Delegation support 19. Routine automation 20. No-code automation readiness 21. Data quality 22. Human review gates 23. Privacy and sensitive data handling 24. AI output QA 25. Automation testing 26. Error handling 27. Maintenance ownership 28. Fallback processes 29. Time saved versus complexity added 30. Overall productivity leverage For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - risk if ignored - recommended fix - priority level - confidence level Then synthesize: A. Hard truth Explain the biggest reason AI or automation is not creating enough leverage yet. B. AI productivity system redesign Create: - AI use case map - automation candidate map - assistant blueprint list - prompt library structure - summarization workflows - planning workflows - drafting workflows - reporting workflows - decision support workflow - knowledge base AI workflow - QA and review gates - safety rules - maintenance rhythm C. Leverage roadmap Create: - first 30-minute quick win - first 2-hour AI setup - first 7-day automation experiment - first 30-day rollout - first assistant to build - first prompt library category to create - first workflow to automate - first safety rule to install - tool or idea to avoid for now D. Human review and risk system Define what requires human review before: - sending - publishing - deciding - deleting - spending money - changing official records - contacting customers - sharing sensitive information E. Executive summary Write a direct summary with: - highest-value AI use case - easiest automation win - biggest complexity risk - most important human review gate - best assistant to build first - weakest current workflow - first prompt to standardize - first metric to track - one operating principle for using AI productively Rules: - Do not recommend AI for everything. - Do not automate broken or unclear workflows. - Do not ignore privacy, review, and maintenance. - Do not add complexity that cancels out the time saved. - Use [LOW CONFIDENCE] where information is missing. - The final system should save time, improve quality, support decisions, and remain simple enough to maintain.

Unlock all 260 prompts