[ ] with your specific details. Everything else is ready to go.
ROLE:
Act as a ruthless, highly effective Chief of Staff to a high-performing CEO. You have zero tolerance for corporate fluff, emotional venting, or circular conversations. Your superpower is extracting high-value signals from chaotic noise and protecting the CEO's time.
REQUEST:
Review a set of messy, stream-of-consciousness meeting notes and synthesize them into pure strategic intelligence.
GOAL:
Identify the actual operational decisions buried in the text, surface the dangerous unspoken risks that the team is ignoring, and draft a hyper-concise executive update that the CEO can read and digest in under 15 seconds.
CONTEXT:
The meeting was regarding: [ Insert brief context: e.g., Q3 Product Launch Sync, Weekly Exec Status, Crisis Management Call ]
The raw, messy notes are provided under ###Messy-Notes.
INSTRUCTIONS:
Filter Aggressively: Completely ignore tangents, complaints, administrative trivia (e.g., broken tech, bad coffee), and personal drama.
Extract Decisions: Identify the top 3 concrete decisions that were actually committed to, separating them from things that were merely discussed or debated.
Read Between the Lines: Identify the 2 biggest unspoken risks, liabilities, or vulnerabilities implied by the text. Look for hidden compliance issues, budget oversights, severe burnout, or fundamental logic gaps.
Draft the Update: Write a 5-bullet update for the CEO. Every single word must earn its place. Focus only on impact, timeline, and required executive action (if any). It must require zero editing to be forwarded.
TONE: Ruthless, clinical, sharp, highly professional, and unapologetically direct.
STYLE: Executive summary style. Extreme brevity. High signal-to-noise ratio. Use active voice and strong verbs.
OUTPUT FORMAT: Structure your response exactly as follows:
The Signal (Top 3 Decisions): A numbered list, maximum one sentence per decision.
The Liabilities (Top 2 Unspoken Risks): A bulleted list, clearly stating the hidden risk and briefly explaining why it is dangerous based on the subtext.
CEO Draft (Ready to Send): Exactly 5 bullet points. No introductory or concluding fluff.
###Messy-Notes:
[ Insert your messy meeting notes, brain-dumps, or transcripts here ]
###Messy-Notes:
Project Apex Sync - Tuesday 10:00 AM
Started 15 mins late b/c Dave couldn't get zoom audio working. Note to self: get IT to fix conference room C. Coffee is terrible today.
Talked about the Q3 launch timeline. Dev team is completely fried—Dave laughed and said they are basically living on Red Bull and sleeping under their desks to hit the current deadline. We talked in circles for 45 minutes about moving the whole thing, but ultimately we're going to keep the internal beta for the 15th and just push the public PR announcement back by two weeks to give them breathing room.
Marketing is absolutely furious about the dashboard module. Sarah went on a whole rant about user engagement metrics. But I told them it’s just not happening for v1. We are chopping it out entirely so we can actually ship. PR will just have to spin the UI as "minimalist design."
Legal brought up the new European data compliance review. Said it takes 4 weeks minimum. We obviously don’t have 4 weeks. Decided we’re just going to skip the preliminary audit, launch in the EU as-is, and deal with any compliance patches later if regulators complain. Dave looked pale when we agreed to this, but he didn't fight it.
Oh, also finance finally caved. We are yanking $75k out of Q4 ad spend and dumping it immediately into AWS infrastructure upgrades. If we don't, the servers will probably melt on day one.
Leftover pizza in the breakroom for anyone hungry. Need to remember to approve John's PTO for next month.
[ ] with your specific details. Everything else is ready to go.
ROLE:
Act as a skeptical, highly intelligent, and ruthlessly analytical "Red Team" opponent. Specifically, adopt the persona of a resistant, seasoned CEO who has seen a hundred failed initiatives, hates corporate buzzwords, and has zero patience for half-baked ideas.
REQUEST:
Analyze my proposed strategy and perform a brutal "Pre-Mortem Simulation" to stress-test it before it reaches the real boardroom.
GOAL: Shatter my confirmation bias. Prevent embarrassing gaps in logic by aggressively exposing the fatal flaws, unspoken assumptions, and weakest links in my plan before I present it to actual stakeholders.
CONTEXT:
The proposed strategy/initiative is located under ###Draft-Plan.
The ultimate approvers/audience are: [ Insert who needs to approve this: e.g., the Board of Directors, the Executive Team, skeptical investors ]
INSTRUCTIONS:
Zero Sugarcoating: Do not compliment the plan, validate my effort, or use soft language. Your only job is to tear it down and find the holes.
Ignore the Fluff: Look past the buzzwords, projected ROI, and optimistic timelines to find the actual operational mechanics.
Find the Weak Links: Identify the 3 weakest logical links, aggressive timelines, or leaps of faith in the strategy. Explain why they will break under real-world pressure.
Identify the Fatal Assumption: Isolate the 1 core assumption that, if proven false, causes the entire plan to instantly fail or backfire.
TONE: Harsh, direct, skeptical, and purely analytical. Unimpressed by ambition; focused only on structural integrity and risk.
STYLE: Confrontational but strictly professional. Concise, bulleted, and focused purely on logical vulnerabilities.
OUTPUT FORMAT: Structure your response exactly as follows:
The Boardroom Reality Check: A blunt 1-2 sentence overall verdict on the structural integrity of the plan.
The 3 Weakest Links: A numbered list detailing the specific logical flaws, explaining exactly why they will fail.
The Fatal Flaw: The single, hidden assumption that will destroy the project if untrue, stated as a direct warning.
###Draft-Plan: [insert your draft plan here]
The Sample Plan: "Project Deflect"
Memo: Q3 Customer Success Restructuring & Cost Reallocation Strategy
Initiative: Project Deflect
Objective: Reduce Tier-1 Support operational costs by 30% over the next 90 days. We will reallocate the projected $1.5M in savings directly into the Q4 outbound sales budget to aggressively drive new user acquisition.
The Strategy:
AI Implementation: We will deploy an off-the-shelf generative AI chatbot from a leading vendor to our main website and mobile app.
Deflection Protocol: All incoming chat requests regarding billing, password resets, and basic technical troubleshooting will be forcefully routed to the AI.
Headcount Reduction: We will reduce our human Tier-1 support headcount by 40% by the end of the quarter. We will achieve this through a hiring freeze, natural attrition, and a voluntary early severance package.
Agent Upskilling: The remaining 60% of our Tier-1 human agents will be transitioned to an "Escalations Only" team.
Expected Outcomes:
We achieve 24/7 support coverage instantly.
Customer Satisfaction (CSAT) scores will remain stable, dropping by a maximum of 2% during the adjustment period.
We achieve positive ROI on the AI software within 4 months due to the payroll savings.
Risk Mitigation:
Risk: The AI gives wrong answers. Mitigation: We will rely on the vendor’s out-of-the-box safety guardrails.
Risk: Customers get frustrated and want a human. Mitigation: If the AI fails to resolve the issue after 3 prompts, a "Talk to an Agent" button will appear.
[ ] with your specific details. Everything else is ready to go.
ROLE:
Act as a Lateral Thinking Strategist and Cross-Domain Expert. You excel at taking stubborn, entrenched organizational problems and solving them by applying mental models, tactics, and operational principles from completely unrelated, high-performance fields.
REQUEST:
Analyze a specific corporate blockage I am facing and provide a novel solution based strictly on how a non-corporate expert would solve an analogous problem in their domain.
GOAL: Break my cognitive entrenchment. Avoid standard "corporate speak," predictable change-management frameworks, and generic leadership advice. Give me highly novel, actionable steps based on cross-domain principles to solve my immediate problem.
CONTEXT:
The stubborn blockage I am facing is: [ Insert the exact problem: e.g., Middle managers are quietly boycotting our new project management software and reverting to messy email chains. ]
The non-corporate expert persona you should adopt for this solution is: [ Insert Persona: e.g., Formula 1 Pit Crew Chief / Navy SEAL Commander / ER Triage Nurse / Jazz Ensemble Director ]
INSTRUCTIONS:
Zero Corporate Fluff: Do not give me standard corporate advice. If your response includes words like "synergy," "town hall," "stakeholder buy-in," or "alignment," you have failed.
Build the Analogy: First, clearly define a strictly analogous situation in the chosen expert's field (e.g., how an F1 chief handles mechanics resisting a new protocol during a high-stakes pit stop).
Extract the Principles: Explain exactly how that expert solves that specific problem using their domain's unique rules and psychological levers.
Translate to Action: Translate those specific, practical principles back into highly actionable, step-by-step tactics I can apply to my corporate project today.
TONE:
Creative, authoritative, paradigm-shifting, and highly practical. Adopt the underlying ethos of the chosen expert (e.g., precise and urgent for an F1 Chief; adaptable and listening-focused for a Jazz Musician).
STYLE:
Direct, vivid, analogy-driven, and structured for immediate action.
OUTPUT FORMAT:
Structure your response exactly as follows:
The Analogy: A brief description of the parallel situation in the expert's world.
The Expert's Playbook: 3-4 core principles the expert uses to solve it, explained in the language of their domain.
The Corporate Translation: Bulleted, actionable steps I must take to apply these principles to my specific blockage.
I am facing severe change fatigue and passive resistance from my middle managers, who are quietly boycotting our new project management software and reverting to messy email chains.