You are a [type of expert] with [years] years of experience 
in [specific domain]. You're known for giving [quality: 
practical, detailed, strategic] advice.

I'm [your role/situation] facing this challenge:
[Describe your situation in 2-3 sentences]

Specific question: [Your actual question]

Please provide your advice, including:
1. Your direct recommendation
2. The reasoning behind it
3. Potential pitfalls to avoid
4. First steps to take

You are a SaaS pricing strategist with 15 years of 
experience in B2B software. You're known for giving 
practical, data-informed advice.

I'm a startup founder with a product management tool 
at $49/month with 500 customers. Growth has stalled.

Specific question: Should I raise prices, add a 
premium tier, or focus on volume?

Please provide your advice, including:
1. Your direct recommendation
2. The reasoning behind it
3. Potential pitfalls to avoid
4. First steps to take

Create a [document type] for [purpose].

Background:
- Who it's from: [sender/author]
- Who it's for: [recipient/audience]
- Context: [relevant situation]
- Goal: [what this should accomplish]

Requirements:
- Length: [word count or pages]
- Tone: [formal/casual/etc.]
- Must include: [required elements]
- Must avoid: [things to exclude]

Format the document with appropriate sections and 
professional formatting.

Create a project proposal for a website redesign.

Background:
- Who it's from: Marketing department
- Who it's for: Executive leadership team
- Context: Current website is 5 years old, conversion 
  rate dropping, competitors have modernized
- Goal: Get approval and budget for Q2 redesign

Requirements:
- Length: 1-2 pages
- Tone: Professional, confident
- Must include: Problem statement, proposed solution, 
  timeline, budget estimate, expected ROI
- Must avoid: Technical jargon, unsubstantiated claims

Format the document with appropriate sections and 
professional formatting.

Analyze the following [type of content] and provide insights.

[Paste your content here]

Analysis parameters:
- Focus on: [specific aspects to analyze]
- For the purpose of: [how you'll use this analysis]
- Audience: [who will see this analysis]

Provide:
1. Key findings (3-5 bullet points)
2. Patterns or themes you notice
3. Potential implications
4. Questions this raises
5. Recommended actions

[Optional: Compare to [benchmark/standard/previous version]]

Analyze the following customer survey responses and 
provide insights.

[Survey data]

Analysis parameters:
- Focus on: Pain points and feature requests
- For the purpose of: Prioritizing our Q1 roadmap
- Audience: Product team

Provide:
1. Key findings (3-5 bullet points)
2. Patterns or themes you notice
3. Potential implications
4. Questions this raises
5. Recommended actions

Compare to: Our satisfaction targets of 4.0+ average

Write a [communication type] about [topic].

Situation:
- From: [sender and their role]
- To: [recipient(s) and relationship]
- Context: [what prompted this/background]
- Desired outcome: [what you want to happen]

Tone considerations:
- This relationship is: [new/established/strained/etc.]
- The topic is: [sensitive/routine/urgent/etc.]
- I want to come across as: [professional/friendly/direct/etc.]

Message requirements:
- Length: [brief/medium/detailed]
- Include: [key points that must be covered]
- Avoid: [things that could backfire]

Write an email about postponing our product launch.

Situation:
- From: Product Director
- To: Executive team and stakeholders
- Context: Critical bug discovered in testing, needs 
  2 more weeks to fix properly
- Desired outcome: Approval to delay without panic, 
  maintain confidence in the team

Tone considerations:
- This relationship is: Established, high-stakes
- The topic is: Sensitive (nobody wants delay news)
- I want to come across as: Confident, responsible, 
  solution-focused

Message requirements:
- Length: Brief (under 200 words)
- Include: The delay, the reason (high-level), the new 
  timeline, why this is the right call
- Avoid: Blame, excessive apologizing, technical details

Generate [number] ideas for [topic/challenge].

Context:
- Goal: [what these ideas should accomplish]
- Constraints: [limitations to work within]
- Target audience: [who these ideas serve]
- What we've tried: [previous attempts, if any]

Idea requirements:
- Range from: [safe/conventional] to [bold/innovative]
- Must be: [practical/inspiring/actionable/etc.]
- Consider: [specific factors to incorporate]

For each idea, provide:
1. The idea (one sentence)
2. Why it might work
3. First step to explore it

Generate 10 ideas for increasing employee engagement.

Context:
- Goal: Improve engagement scores by 15% in 6 months
- Constraints: $10K annual budget, remote-first team 
  of 50, no travel
- Target audience: Software engineers, average age 28-35
- What we've tried: Virtual happy hours (low attendance), 
  more Slack channels (not used)

Idea requirements:
- Range from: Quick wins to bigger initiatives
- Must be: Practical for a remote team
- Consider: Introverts, different time zones, work-life 
  balance concerns

For each idea, provide:
1. The idea (one sentence)
2. Why it might work
3. First step to explore it

Create a [type of process/procedure] for [task/goal].

Context:
- Who will use this: [role/experience level]
- When it's used: [trigger/frequency]
- Current state: [how it's done now, if at all]
- Tools available: [software, resources]

Process requirements:
- Number of steps: [maximum or approximate]
- Level of detail: [high-level overview / detailed / 
  extremely detailed with sub-steps]
- Include: [checklists, templates, tips, examples]
- Format: [numbered steps, flowchart description, etc.]

Also include:
- Common mistakes to avoid
- Signs the process is working
- When to deviate from the process

Create an onboarding process for new customers.

Context:
- Who will use this: Customer Success team (CSMs)
- When it's used: When a new customer signs contract
- Current state: Ad hoc, each CSM does it differently
- Tools available: Salesforce, Loom, Google Docs, 
  Calendly

Process requirements:
- Number of steps: 8-12 main steps
- Level of detail: Detailed with sub-steps and timing
- Include: Email templates, checklists, success 
  metrics for each phase
- Format: Numbered steps with substeps

Also include:
- Common mistakes to avoid
- Signs the process is working
- When to deviate from the process

Review the following [type of work] and provide feedback.

[Paste your work here]

Review criteria:
- Evaluate for: [specific qualities to assess]
- Assume audience of: [who will see the final version]
- Compare to: [standard, best practices, example]

Provide:
1. Overall assessment (one paragraph)
2. Top 3 strengths
3. Top 3 areas for improvement (with specific suggestions)
4. Any red flags or concerns
5. Quick wins that would improve it immediately

Be [direct/gentle/thorough]—I want honest feedback 
to improve, not validation.

Review the following sales email and provide feedback.

[Email draft]

Review criteria:
- Evaluate for: Persuasiveness, clarity, call to action
- Assume audience of: IT managers who receive 20+ 
  sales emails daily
- Compare to: Best practices for cold outreach

Provide:
1. Overall assessment (one paragraph)
2. Top 3 strengths
3. Top 3 areas for improvement (with specific suggestions)
4. Any red flags or concerns
5. Quick wins that would improve it immediately

Be direct—I want honest feedback to improve, not validation.

Compare [Option A] vs [Option B] for [decision/purpose].

Context:
- Decision maker: [who/role]
- Key priorities: [what matters most, ranked]
- Constraints: [budget, timeline, resources]
- Current situation: [relevant background]

For each option, analyze:
- Pros and cons
- Fit with priorities
- Risks and mitigation
- Cost (money, time, opportunity)
- Long-term implications

Then provide:
1. Side-by-side comparison table
2. Your recommendation
3. Under what circumstances you'd recommend the other option
4. What additional information would change the analysis

Compare building in-house vs using a SaaS tool for 
our analytics needs.

Context:
- Decision maker: CTO at 50-person startup
- Key priorities: 1) Speed to implement, 2) Customization, 
  3) Long-term cost
- Constraints: $50K annual budget, 2 developers could 
  work on this, need something in 6 weeks
- Current situation: Using spreadsheets, growing 
  frustration, data-driven culture is a priority

For each option, analyze:
- Pros and cons
- Fit with priorities
- Risks and mitigation
- Cost (money, time, opportunity)
- Long-term implications

Then provide:
1. Side-by-side comparison table
2. Your recommendation
3. Under what circumstances you'd recommend the other option
4. What additional information would change the analysis

Explain [complex topic] to [audience].

Audience profile:
- Knowledge level: [beginner/intermediate/expert in 
  what areas]
- They care about: [what's relevant to them]
- They struggle with: [common confusion points]
- Time available: [how much detail they want]

Explanation requirements:
- Use analogies from: [familiar domain]
- Avoid or define: [jargon/terms]
- Focus on: [most important concepts]
- End with: [key takeaway, next step, or question]

Format: [paragraph, bullets, structured sections, etc.]

Explain how machine learning works to small business owners.

Audience profile:
- Knowledge level: Comfortable with computers, no 
  technical background, understand basic statistics
- They care about: How it applies to their business, 
  whether it's worth investing in
- They struggle with: How it differs from traditional 
  software, why it needs data
- Time available: 5 minutes of attention

Explanation requirements:
- Use analogies from: Running a small business, 
  common office work
- Avoid or define: Technical terms like algorithms, 
  neural networks, training data
- Focus on: What it does, how it learns, realistic 
  applications for small business
- End with: Three questions to ask before adopting ML

Format: 4-5 short paragraphs with clear headers

Transform the following [original format] into [new format].

Original content:
[Paste content]

Transformation requirements:
- Preserve: [what must stay the same: key messages, 
  data, tone]
- Change: [what should be different: length, structure, 
  style]
- Add: [new elements needed for the new format]
- Remove: [what doesn't work for the new format]

New format specifications:
- Length: [target length]
- Structure: [how it should be organized]
- Style: [how it should read]
- Must include: [required elements for this format]

If the original has issues, [flag them / fix them / 
preserve them].

Transform the following meeting transcript into an 
action-item summary email.

Original content:
[Meeting transcript]

Transformation requirements:
- Preserve: All decisions made, action items, deadlines
- Change: Remove tangents, small talk, repeated points
- Add: Owner for each action item, priority level
- Remove: Discussion that didn't lead to decisions

New format specifications:
- Length: Under 300 words
- Structure: Brief context, decisions list, action 
  items table, next steps
- Style: Professional, scannable
- Must include: Date of meeting, attendees, next 
  meeting date if mentioned

If the original has unclear action items, flag them 
with [UNCLEAR - verify].