Leverage AI. Automate Work. Maximize Output.

# [C] CONTEXT
I am a [INSERT ROLE, e.g., Founder / Product Manager / Agency Lead] managing a distributed workload. I have [INSERT HOURS, e.g., 40] working hours available this week, and my cognitive peak hours are between [INSERT PEAK HOURS, e.g., 9:00 AM and 12:30 PM].

# [O] OBJECTIVE
Transform my unstructured brain-dump of tasks below into a scientifically optimized 5-Day Deep-Work Sprint Schedule and Delegation Matrix.

# [S] STYLE & [T] TONE
Operational, decisive, zero-fluff executive coaching style.

# [A] AUDIENCE
An operator who needs strict calendar protection and clear daily execution blocks.

# [R] RESPONSE FORMAT
1. **Bottleneck Diagnosis:** Identify the single highest-leverage constraint task (the 20% driving 80% of outcomes).
2. **Eisenhower & Leverage Triage Table:** Classify every task into (A) Deep Work Core, (B) Shallow Batch, (C) Automate/AI-Assist, or (D) Delegate/Drop.
3. **5-Day Time-Blocked Calendar (Mon–Fri):** Group tasks by cognitive mode (Creation vs. Admin vs. Meetings) to eliminate context-switching penalties.
4. **3 Daily Non-Negotiable Rules:** Guardrails to prevent scope creep this week.

# MY RAW TASK LIST & DEADLINES:
[PASTE YOUR UNORDERED TASKS, PROJECTS, AND MEETINGS HERE]

# ROLE
Act as a Principal Chief of Staff and Operations Documentation Architect.

# TASK
Analyze the raw meeting transcript or rough call notes provided below and extract a zero-ambiguity Executive Summary, RACI Action Matrix, and Reusable SOP.

# STRICT CONSTRAINTS
- Never invent deadlines or owners not implied in the text; flag missing owners explicitly as [NEEDS OWNER].
- Strip all small talk, repetition, and filler.
- Use active verbs for every action item.

# REQUIRED OUTPUT SECTIONS
1. **BLUF Executive Brief (Max 4 Sentences):** Core decisions made, budget/timeline impacts, and primary blocker.
2. **RACI Action Item Table:** Columns: | Deliverable | Responsible (Owner) | Accountable | Deadline | Status/Blocker |
3. **Standard Operating Procedure (SOP) Draft:** If a repeatable workflow was discussed, document it as a numbered Step 1 → Step N checklist with inputs, tools, and definition of done.
4. **Ready-to-Send Follow-Up Slack/Email Note:** A concise 120-word recap message ready to paste to attendees.

# RAW TRANSCRIPT / MEETING NOTES:
[PASTE TRANSCRIPT OR NOTES HERE]

# ROLE & METHODOLOGY
You are an elite Commercial Negotiation Strategist trained in Harvard PON principles and Chris Voss's Tactical Empathy framework.

# SCENARIO INPUTS
- Counterparty: [INSERT COUNTERPARTY, e.g., Enterprise Client / Hiring VP / Vendor]
- Their Stated Position / Objection: [INSERT WHAT THEY SAID OR ASKED FOR]
- My Target Outcome: [INSERT IDEAL PRICE, SALARY, OR SCOPE]
- My Walk-Away Floor (BATNA): [INSERT MINIMUM ACCEPTABLE TERMS]

# INSTRUCTIONS (STEP-BY-STEP CHAIN OF THOUGHT)
First, analyze the hidden power dynamics, anxieties, and constraints driving the counterparty's objection.
Second, draft 3 distinct written response options calibrated by assertive posture:
- **Option A (Collaborative Value-Anchor):** Preserves warmth while tying price/compensation directly to quantified ROI.
- **Option B (Scope-Trade / Conditional Concession):** Uses "If you need X, then we adjust Y" framing so you never discount for free.
- **Option C (Calibrated No-Oriented Question):** Uses a polite "How am I supposed to do that?" pivot to make them solve your constraint.

# FORMAT
Keep each email/message under 140 words, free of weak qualifiers ("just", "sorry", "hopefully").

# [R] ROLE
You are a Senior Automation Systems Engineer specializing in Make.com, n8n, REST APIs, and LLM webhook orchestration.

# [I] INSTRUCTIONS
Design a complete, fault-tolerant automation blueprint that connects [SOURCE APP/TRIGGER, e.g., Typeform / HubSpot / Gmail] to [DESTINATION APP, e.g., Notion / Slack / Airtable] with an AI processing layer in between.

# [S] STEPS TO GENERATE
1. **Node-by-Node Architecture Diagram:** List every module in sequence (Trigger → Data Filter → HTTP/AI Node → Router → Action Nodes).
2. **Strict JSON Schema for the AI Node:** Provide the exact `response_format` JSON schema the LLM must return so downstream nodes never break.
3. **Data Mapping & Expressions:** Show the exact variable mapping syntax (e.g., `{{1.body.email}}` or `.data`) between steps.
4. **Idempotency & Error Handling:** Specify how to prevent duplicate runs and where to route failed webhook payloads (HTTP 429 / 500 retry logic).

# [E] END GOAL
A copy-paste technical specification I can build in Make.com or n8n in under 30 minutes.

# [N] NARROWING CONSTRAINTS
My specific business workflow is: [DESCRIBE WHAT YOU WANT TO AUTOMATE IN 2-3 SENTENCES]