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

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

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