The Problem
You don't know what you don't know, and you can't build a learning plan until you have an honest map of where your skills actually stand right now.

The Outcome
A complete, honest skills audit across your role or domain, with every skill rated by proficiency level, a clear gap analysis, and a prioritized list of what to develop first.

Time Required: 30 min
Difficulty Level: Intermediate
Best Platform: Claude (stronger at structured self-assessment frameworks and nuanced gap analysis)

The Recipe

Read more

The Problem
You need to cut 30% of your writing without losing meaning or starting over.

The Outcome
Tighter writing that says the same thing in fewer words, with improved flow and punch.

Time Required: 10 min
Difficulty Level: Beginner
Best Platform: ChatGPT (faster at line editing)

The Recipe

I need to cut this writing by approximately 30% while keeping the meaning.

Current word count: [NUMBER]

Target word count: [NUMBER - should be about 30% less]

Content to tighten: [PASTE YOUR SECTION - up to 1000 words works well]

Cut the word count by:

1. Removing redundant phrases and repeated ideas

2. Eliminating filler words and weak qualifiers (”very,” “really,” “quite,” “fairly”)

3. Replacing wordy phrases with concise alternatives

4. Cutting entire sentences that don’t add value

5. Keeping every sentence that directly serves the main point

Show me the edited version with the same flow and tone but 25-30% shorter. Mark what you cut and briefly explain why so I can learn.

DO NOT:

• Cut so much that meaning becomes unclear

• Remove important examples or supporting evidence

• Change my voice or tone while tightening

• Make it choppy by only cutting transition phrases

Ingredients Needed

• Content that’s too long (draft, email, article section)

• Current and target word counts

• Honest assessment of what’s truly necessary

• Your core message clearly in mind

Cooking Instructions

1. Read and mark - Identify obviously redundant sections yourself first (3 minutes)

2. Set targets - Calculate 30% reduction (30 seconds)

3. Run the edit - Let AI tighten the piece (2 minutes)

4. Compare versions - See what got cut and why (3 minutes)

5. Restore the essential - Add back anything AI removed that you actually need (2 minutes)

What You’ll Get

Your content reduced by 25-30% with better flow and punch. About 80% of cuts improve the piece - you’ll wonder why you included the fluff. The other 20% might cut too deep - that shows you what was actually essential. Either way, you end up with tighter writing.

Variations

Quick Version: Just paste content and say “Cut this by 30% without losing meaning”
Deep Version: Add “Show before/after examples of the tightest cuts so I can learn the pattern”

Combine With

• Recipe #1.1 (The 15-Minute First Draft) when your draft is way too long

• Recipe #1.8 (The Sentence Simplifier) if sentences are also too complex

• Recipe #19.1(The Tightener) for advanced line-by-line editing

Chef’s Tips

• Almost everything can lose 20-30% without losing meaning - we all write long first drafts

• If AI cuts something and you feel the loss, that tells you it was important - add it back and cut something else

• Common cuts: introductory phrases (”It’s important to note”), hedging (”somewhat,” “fairly”), and saying the same thing twice

• After using this recipe 10 times, you’ll start writing tighter first drafts because you’ll recognize the patterns

Success Metric: If the edited version communicates your point faster and more clearly, you successfully cut fat without hitting muscle.

Subscribe now

Note that the ‘Combine with’ suggestions reference recipes in The Prompt Hackers Cookbook

The Problem

A customer cancels and you get either no response or a vague "it's not you, it's me" that tells you nothing actionable.

The Outcome

A short, non-defensive message that makes people actually want to tell you the real reason they left, giving you data to fix retention problems.

Time Required: 10 minutes
Difficulty Level: 🔧 Intermediate
Best Platform: Claude (better at empathetic, conversational tone)

What You’ll Get

A short, personal message that feels like an actual human wrote it. About 30-40% of people will respond with honest feedback, much higher than typical cancellation surveys. The responses you get will be more detailed and useful because you're asking one focused question instead of a survey barrage.

Variations

• Quick Version: Skip the incentive offer, just ask the one question

• Deep Version: Add "If they mention [SPECIFIC PAIN POINT], include a follow-up question asking for details"

Combine With

• Recipe #15.1 (The Feedback Deliverer) to use their input in team discussions

• Recipe #11.10 (The Follow-Up Sequence) if they express interest in returning later

• Recipe #16.4 (The Scope Expander) to identify what features they needed that you didn’t have

Chef’s Tips

• Best question format: “What’s the one thing that would have made you stay?” (Forces prioritization over laundry list)

• Timing matters: Send within 24 hours of cancellation. After 48 hours, response rate drops by half

• Don’t defend: If they say something harsh, resist the urge to explain why they’re wrong, this kills future responses

• Track patterns: After 10-15 responses, you’ll see 2-3 reasons that keep repeating, those are your real retention problems

• The incentive sweet spot: $10-25 gift card gets responses without feeling like you’re bribing them. Too high feels manipulative.

• When to skip this recipe: If you have high-volume, low-touch cancellations (B2C subscriptions under $20/month), the data gets noisy. Focus on patterns in your cancellation flow instead.

Success Metric: If fewer than 25% respond, your message sounds too corporate or asks too much. If responses are vague ("just didn't need it anymore"), your question wasn't specific enough. Aim for 30-40% response rate with specific, actionable answers.

Read more

Note that the ‘Combine with’ suggestions reference recipes in The Prompt Hackers Cookbook

The Problem

You have a topic but no episode structure, so you ramble or run out of things to say.

The Outcome

A complete episode outline with timed segments, talking points, and transitions that keeps listeners engaged for your target length.

Time Required: 15 min
Difficulty Level: Beginner
Best Platform: Claude (better at logical structure and pacing)

What You’ll Get

A structured outline with 3-5 main segments, realistic time allocations, and specific talking points for each section. About 80% of episodes following this structure feel cohesive and well-paced. You'll still need to add your personality and examples, but the skeleton prevents rambling or awkward gaps.

Variations

• Quick Version: Skip the "What I already know" section and just provide topic + length

• Deep Version: Add "Include specific questions to ask myself in each segment" and "Suggest 2-3 stories or examples that would work for each point"

Combine With

• Recipe #9.2 (The Hook in 3 Seconds) to craft a compelling opening

• Recipe #3.7 (Expert Interview Prep) if you’re interviewing someone

• Recipe #2.1 (The Content Multiplier) to repurpose episode into social content

Chef’s Tips

• Most first-time episode structures are too ambitious - cut 20% of what you think you can cover

• If your target length is 30 minutes, plan for 25 minutes of content (you’ll always go over)

• The hook matters more than anything else - spend extra time on those first 60 seconds

• If you can’t explain why a segment matters to listeners, cut it

Success Metric: If you can record the episode without constantly checking notes or losing your place, the structure works.

The Recipe

I need to plan a podcast episode with clear structure and timing.

Episode Details:

• Topic: [SPECIFIC TOPIC OR ANGLE]

• Target length: [15 min | 30 min | 45 min | 60 min]

• Format: [Solo | Interview | Co-hosted | Panel]

• Audience: [WHO LISTENS AND WHAT THEY CARE ABOUT]

• Goal: [Educate | Entertain | Inspire | Sell | Build authority]

What I already know:

• [3-5 bullet points of key ideas, stories, or points you want to cover]

Create an episode structure that includes:

1. Hook (30-60 seconds) - Why someone should keep listening

2. Intro/Setup (2-3 minutes) - Context and what they’ll learn

3. Main segments (3-5 segments with clear focus for each)

4. Transition language between segments

5. Outro/CTA (1-2 minutes) - What to do next

For each segment, provide:

• Estimated time

• Core message or point

• 3-4 specific talking points or questions

• Why this segment matters to the listener

Use conversational language. Avoid podcast clichés like “without further ado” or “before we dive in.” Make transitions feel natural.

DO NOT create a script - I need talking points, not word-for-word copy.

Ingredients Needed

• Your episode topic (specific, not vague)

• Target episode length

• 3-5 key points or stories you want to include

• Clear understanding of who listens and why

• Your episode format (solo, interview, etc.)

Cooking Instructions

1. Fill in all five Episode Details sections - be specific about audience and goal

2. List your 3-5 key ideas in the “What I already know” section

3. Paste into AI and run

4. Review the structure for logical flow and realistic timing

5. Adjust segments that feel too long or don’t serve your goal

Note that the ‘Combine with’ suggestions reference recipes in The Prompt Hackers Cookbook

The Problem

You schedule tasks randomly throughout the day instead of matching high-focus work to your peak energy periods.

The Outcome

A personalized schedule that maps your task types to your natural energy patterns, increasing productivity without working more hours.

Time Required: 30 minutes
Difficulty Level: Intermediate
Best Platform: Claude (better at analyzing patterns and nuance)

What You’ll Get

A schedule that respects your biology instead of fighting it. About 60-70% will feel immediately better than your current approach. The remaining 30-40% needs real-world testing since everyone's energy patterns are unique. You'll likely discover your true peak hours aren't when you assumed.

Variations

• Quick Version: Just list tasks and ask "When should I do each based on typical energy patterns?"

• Deep Version: Add "Include a 2-week testing protocol with daily tracking questions to refine my energy map"

Combine With

• Recipe #20.2 (The Checklist Creator) to systemize your new schedule

• Recipe #14.7 (The Milestone Definer) to protect your power hours for important work

• Recipe #15.3 (The Goal Setter) to ensure high-energy time goes to high-impact goals

Chef’s Tips

• Most people are wrong about their energy patterns - track for a week before trusting your guess

• Your “power hours” are sacred - protect them ruthlessly from meetings and interruptions

• If you hit afternoon slumps, that’s your admin/email/calls window, not your creative work time

• Energy patterns change with seasons, sleep quality, and life circumstances - remap quarterly

• The biggest mistake is putting deep work after lunch when most people’s focus is lowest

Success Metric:If you complete one major task before noon without feeling drained, and handle afternoon admin without resentment, your energy map is working.

The Recipe

I need to create a personalized energy-based schedule that matches my tasks to my natural energy levels throughout the day.

My typical workday: [START TIME] to [END TIME]

My current energy pattern (best guess):

• Morning (first 3 hours): [high/medium/low energy]

• Late morning: [high/medium/low energy]

• After lunch: [high/medium/low energy]

• Mid-afternoon: [high/medium/low energy]

• Late afternoon/evening: [high/medium/low energy]

My typical tasks (list 8-15):

• [Task 1]

• [Task 2]

• [Task 3]

• [etc.]

For each task, categorize it by energy requirement:

• Deep Focus: Requires sustained concentration, creativity, strategic thinking

• Moderate Focus: Requires attention but is familiar/routine

• Low Focus: Administrative, repetitive, or social tasks

Then create a daily schedule template that:

1. Maps each task type to my optimal energy windows

2. Includes specific time blocks (not just “morning”)

3. Accounts for realistic transition time between tasks

4. Identifies my “power hours” for most important work

5. Suggests buffer zones for unexpected items

Format as a daily schedule I can actually follow. Be specific about timing, not generic.

Ingredients Needed

• Your typical work start and end times

• Honest assessment of when you feel most/least energized

• Complete list of your regular tasks and responsibilities

• Understanding of which tasks drain you vs. energize you

• One week to test and adjust the schedule

Cooking Instructions

1. List all your regular tasks without categorizing them yet

2. Note your current energy patterns (even rough guesses work)

3. Paste into prompt and generate your first energy map

4. Test the schedule for 3 days, noting what works and what doesn’t

5. Adjust and regenerate based on real experience, not theory

Note that the ‘Combine with’ suggestions reference recipes in The Prompt Hackers Cookbook

The Problem

Your product description lists features but doesn't create desire, answer objections, or give customers a clear reason to buy instead of comparing more options.

The Outcome

A conversion-focused product description that addresses customer skepticism, builds desire, and guides them toward purchase.

Time Required: 20 minutes
Difficulty Level: Intermediate
Best Platform: Claude (better at balancing persuasion with authenticity)

What You’ll Get

A 200-300 word product description structured for conversion. Typically 70% is ready to publish immediately. The opening and promise sections are usually strong; the "how it works" section might need refinement to better match your specific features. You'll likely need to adjust tone slightly to match your exact brand voice. The structure ensures you're hitting all persuasion elements without feeling pushy.

Variations

• Quick Version: Skip the detailed structure requirements and just ask for "persuasive product description for [product] that addresses [objection]"
  Deep Version: Add "Include 3 alternative opening hook options" and "Provide A/B test version focusing on different primary benefit"

Combine With

• Recipe #10.2 (The Feature-Benefit Converter) to translate your feature list before writing the description

• Recipe #11.2 (The Objection Anticipator) to identify objections you need to address in the copy

• Recipe #10.4 (The CTA) to write the specific call-to-action that follows this description

Chef’s Tips

• The best product descriptions address the customer’s internal dialogue: “Will this work for me?” “Is this worth the price?” “What if it doesn’t work?”

• Open with the problem or desire, not your product—customers need to see themselves in the story before they care about your solution

• Specificity builds credibility: “Saves 3 hours per week” beats “Saves you time”

• Your main objection usually isn’t price—it’s “Will this actually work for MY situation?” Address the unique worry, not generic concerns

• If your description could work for a competitor’s product by swapping the name, it’s too generic—add more specific differentiation

• Test removing any sentence that starts with “Our product...” and rewriting it starting with “You’ll...” or “This means...”

• The opening sentence is 50% of conversion power—test 3-5 different hooks and A/B test them

• If you sell through retailers (Amazon, etc.), front-load the benefits—many customers never scroll past the first 3 sentences

Success Metric: If a qualified prospect reads your description and their next action is adding to cart (not opening 5 more tabs to compare), your description is working. Track bounce rate and time-on-page - effective descriptions reduce comparison shopping.

The Recipe

Read more

Note that the ‘Combine with’ suggestions reference recipes in The Prompt Hackers Cookbook

The Problem

You need a memorable product name that stands out, sounds professional, and isn't already claimed by competitors or domain squatters.

The Outcome

15-20 naming options across different styles with trademark availability insights and domain name suggestions.

Time Required: 30 minutes
Difficulty Level: Intermediate
Best Platform: Claude (better at creative nuance and avoiding generic suggestions)

What You’ll Get

20 name options split across different naming styles. Typically 4-6 will feel immediately promising. 2-3 will have available .com domains. About 30% will be genuinely creative options you wouldn't have thought of yourself. The rationales help you understand why each name works, making it easier to defend your final choice to stakeholders.

Variations

• Quick Version: Skip trademark concerns and domain suggestions, just get 15 names organized by style

• Deep Version: Add "Include 3 tagline options for the top 5 names" and "Explain target customer response to each top name"

Combine With

• Recipe #11.1 (The Value Proposition Builder) to ensure your name aligns with positioning

• Recipe #12.5 (The Differentiation Statement) to verify the name supports your unique angle

• Recipe #10.1 (The Headline That Stops) to test names in actual marketing copy context

Chef’s Tips

• Run this recipe twice with slightly different product descriptions - sometimes reframing reveals better name directions

• The “invented word” category often produces the most memorable names, but they require bigger marketing budgets to establish meaning

• If all .com domains are taken, .io and .ai domains are now professionally acceptable for tech products

• Name generators are tempting, but they don’t understand your market context - this recipe factors in positioning and competitive landscape

• The best names often feel slightly “wrong” at first but grow on you over 48 hours - don’t dismiss unusual options immediately

• Test your finalists in an email signature and social media handle format - some names that look good in isolation don’t work in practice

Success Metric: If you can say the name once to someone unfamiliar with your product and they can spell it correctly when searching for it later, you have a strong candidate.

The Recipe

Read more

Note that the ‘Combine with’ suggestions reference recipes in The Prompt Hackers Cookbook

The Problem

You’re leaving money on the table with existing customers, but can’t identify where the natural upgrade paths exist.

The Outcome

A prioritized list of 5-10 specific upsell opportunities with implementation difficulty, revenue potential, and customer readiness scores for each.

Time Required: 30 minutes
Difficulty Level: Advanced
Best Platform: Claude (better at strategic analysis and pattern recognition)

What You’ll Get

A strategic roadmap of 5-10 specific upsell opportunities ranked by priority. About 60-70% will be genuinely viable options you could implement. 20-30% will require more research or validation. 10-20% might not fit your business model, but will spark ideas for what could work. The prioritization framework gives you clear next steps rather than an overwhelming list of possibilities.

Variations

Quick Version: Remove the detailed scoring system and just ask: “Give me the top 3 upsell opportunities I’m missing based on [customer data]”

Deep Version: Add: “For each opportunity, create a launch plan including positioning, pricing structure, and first 30 days of rollout”

Combine With

• Recipe #11.7 (The Pricing Justification) to determine how to price your upsells

• Recipe #11.8 (The Case Study Creator) to build proof for new offerings

• Recipe #17.2 (The Quarterly Plan) to sequence your upsell rollout over time

• Recipe #4.5 (The Risk Assessor) to evaluate risks before committing resources

Chef’s Tips

• The best upsell opportunities already exist in your support tickets and customer questions. You don’t need to invent new problems to solve

• If fewer than 20% of your customers could potentially buy the upsell, it’s probably too narrow. Look for opportunities that serve broader segments

• “Done-for-you” versions of your existing offering are almost always viable upsells (people will pay to not have to do the work themselves)

• Upsells that solve problems your product creates or reveals are the easiest to sell (example: if you teach people to podcast, selling them audio editing is natural)

• The implementation difficulty score matters more than revenue potential. A $10K opportunity you can’t deliver well is worth $0

• Don’t confuse “customers are asking for it” with “customers will pay for it.” Validate willingness to pay before building

• If an upsell requires you to become good at something you’re not currently good at, that’s not an upsell opportunity, it’s a pivot

Success Metric: If you can identify at least 2 "Quick Win" opportunities that you could launch within 30 days and have 10+ customers who'd likely buy them, the recipe worked. If everything scores high on difficulty or low on readiness, your inputs weren't specific enough or you're trying to force upsells that don't naturally exist.

The Recipe

Read more

Note that the ‘Combine with’ suggestions reference recipes in The Prompt Hackers Cookbook

The Problem

Your job description reads like every other company's, attracts candidates who aren't a fit, and doesn't help you filter for what actually matters.

The Outcome

A job description that clearly communicates what the role actually involves, attracts qualified candidates who match your reality, and helps wrong fits self-select out.

Time Required: 25 minutes
Difficulty Level: Intermediate
Best Platform: Claude (better at capturing nuance and tone)

What You’ll Get

A job description that sounds like a real company talking about a real job. About 70-80% will be ready to use immediately. The other 20-30% needs your specific examples, inside jokes, or technical details AI can't know. You'll get clear "apply if" and "don't apply if" sections that do heavy filtering before you ever read resumes. The screening questions are usually spot-on for testing what actually matters versus checking boxes.

Variations

Quick Version: Skip the 30/60/90 day milestones and company reality check, just focus on role description
Deep Version: Add "Write 3 example interview questions with scoring rubrics for each non-negotiable requirement"

Combine With

• Recipe #17 (The Interview Question Designer) to build out your full hiring process

• Recipe #12.5 (The Differentiation Statement) if you’re struggling to articulate what makes your company different

• Recipe #11.2 (The Objection Anticipator) to address concerns great candidates might have about joining

Chef’s Tips

• If you can’t articulate why the last person left, you’re not ready to write this JD yet

• The “You Probably Shouldn’t Apply If” section is the most valuable part - it saves you from 50 bad interviews

• Job titles matter less than you think - describing reality matters more

• If you list more than 5 requirements, you’re describing a unicorn that doesn’t exist

• The best JDs make 20% of readers immediately know they’re perfect and 60% immediately know they’re not - that’s good filtering

• Remote vs. office matters more than salary to most candidates - be crystal clear

• If you wouldn’t want to do this job based on the description, rewrite it until you would

Success Metric: If you get fewer total applicants but a higher percentage of qualified candidates worth interviewing, it worked. If you get the same generic pile of resumes, your description is still too generic.

The Recipe

Read more

Note that the ‘Combine with’ suggestions reference recipes in The Prompt Hackers Cookbook

The Problem

You’re busy all day but can’t explain what you actually accomplished or where 8 hours disappeared to.

The Outcome

A clear breakdown of where your time is really going, what’s stealing hours without delivering value, and specific changes to reclaim 5-10 hours per week.

Time Required: 20 minutes
Difficulty Level: Intermediate
Best Platform: Claude (better at pattern recognition and nuanced analysis)

What You’ll Get

A data-driven breakdown that usually surprises you in 2-3 categories. Most people discover they spend 40-60% more time in communication than they thought, and 50-70% less time in deep work than they estimated. The reclaim opportunities are specific to your actual patterns, not generic advice. The one-week experiment gives you a concrete test to run. Success rate is about 85% for identifying at least one major time leak you weren't aware of.

Variations

Quick Version: Track just 2 days and skip the energy-time mismatch analysis
Deep Version: Add "Track your energy level (1-10) for each activity" to identify when you're wasting high-energy time on low-value work

Combine With

• Recipe #1 (The Daily Prioritizer) to ensure your priorities match your available time blocks

• Recipe #20.6 (The Bottleneck Finder) if time analysis reveals process problems

• Recipe #15.6 (The Delegation Guide) for activities that shouldn’t be on your plate at all

Chef’s Tips

• Most people underestimate communication time by 50% and overestimate focus time by 70%

• If you have fewer than 3 blocks of 90+ minutes uninterrupted time per week, that’s your problem

• Context switching costs 15-30 minutes of recovery time that most people don’t track

• Activities that happen every day but “only take a few minutes” often add up to 5-10 hours per week

• If you can’t identify 5 hours to reclaim, you didn’t track honestly enough - try again

• The hardest finding to accept is usually the most valuable one to fix

Success Metric: If you find at least 5 hours per week of reclaimable time and can articulate exactly where it’s being lost, the audit worked.

The Recipe

Read more

For the next 24 hours, newsletter subscribers get an extra $10 off the launch price. That’s the complete cookbook for just $7 with code LAUNCH26 at prompthackerscookbook.com

The Problem

You have 20 tasks on your list but only time for 5, and you’re guessing which ones actually matter.

The Outcome

A ranked list of your top 5 priorities with clear reasoning for why they beat everything else today.

Time Required: 10 minutes
Difficulty Level: Beginner
Best Platform: ChatGPT (faster processing for quick decisions)

What You’ll Get

A ruthlessly prioritized list that cuts through decision paralysis. About 80% of the time, the top 5 will feel right immediately. 20% of the time, you’ll want to swap something based on context AI doesn’t have - that’s fine, the framework still did the heavy lifting. You’ll also get clear reasoning for what to postpone, helping you feel good about what you’re NOT doing.

Variations

Quick Version: Just list tasks and weekly goal, skip energy/time context
Deep Version: Add “Strategic importance to 6-month goals” as an evaluation criteria

Combine With

• Recipe #4.2 (The Decision Matrix) when priorities involve major strategic choices

• Recipe #14.2 (The Timeline Builder) to map out when postponed tasks should happen

• Recipe #15.6 (The Delegation Guide) for tasks that shouldn’t be on your list at all

[Note that these reference recipes in The Prompt Hackers Cookbook]

Chef’s Tips

• The more honest you are about available time, the better the prioritization

• If more than 3 tasks are marked “urgent,” you have a planning problem, not a prioritization problem

• Run this Sunday night for the week ahead, then use daily for adjustments

• If you consistently disagree with the AI’s rankings, your weekly goal might be wrong

• Tasks that never make the top 5 after 3 weeks should be deleted entirely

Success Metric: If you finish 4 out of 5 priorities and feel good about what you didn’t do, it worked.

The Recipe

I need to prioritize my tasks for today. I have limited time and need to focus on what truly matters.

Here are all my potential tasks for today: [LIST ALL TASKS - include everything, even small items]

Context about my current situation:

• Most important goal this week: [YOUR WEEKLY GOAL]

• Biggest deadline or pressure point: [WHAT’S URGENT]

• Available working time today: [HOURS]

• Energy level: [HIGH/MEDIUM/LOW]

For each task, evaluate:

1. Impact on my weekly goal (0-10)

2. Urgency (does it have to be today?)

3. Time required (realistic estimate)

4. Energy required (high/medium/low focus)

5. Dependencies (does anything else depend on this?)

Then provide:

• Top 5 priorities ranked with reasoning

• What to postpone with suggested dates

• What to delegate or delete with rationale

• Suggested order based on my energy level

DO NOT give me motivational advice. DO NOT suggest I “do my best.” Just tell me what should win and why, using concrete reasoning.

Ingredients Needed

• Complete task list (don’t filter anything out yet)

• Your #1 weekly goal or objective

• Honest assessment of available time today

• Current energy level (be realistic)

• Any hard deadlines or commitments

Cooking Instructions

1. Brain dump everything - List every task, even 5-minute items, without judging

2. Add your context - Fill in weekly goal, deadlines, time available, energy

3. Run the prompt - Paste everything and let AI evaluate each task

4. Review the reasoning - Check if AI’s logic matches your reality

5. Commit to the top 5 - Write these on a separate list and ignore everything else today