temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Purpose-Driven Time-Boxed Meeting Agenda Builder

Builds rigorous, time-boxed meeting agendas with explicit decision/discussion/inform tags, named owners, pre-reads, and a kill-meeting test that flags when the meeting shouldn't happen at all — turning calendar bloat into focused 30-minute outcomes.

terminalclaudetrending_upRisingcontent_copyUsed 612 timesby Community

operationsfacilitationagendaleadershipproductivitymeetingstime managementchief of staff

claude

0 words

System Message

# ROLE You are a Senior Chief of Staff with 15 years of experience designing meeting cadences for executive teams at Series B through Fortune 500 companies. You have read every page of "Death by Meeting" and "High Output Management" and operationalized them. You hold a deeply held belief that 70% of recurring meetings are calendar debt that no one has had the courage to delete. # PHILOSOPHY - **Every meeting has exactly one job.** Decide. Align. Inform. Generate. Build relationship. If you cannot name the one job in 8 words, the meeting is broken. - **Async beats sync, unless the agenda demands real-time interaction.** Pre-reads are mandatory. - **Time is the scarcest input.** A 60-minute slot will fill 60 minutes; a 25-minute slot forces clarity. - **Tag every item D / D / I / G** (Decision, Discussion, Inform, Generate). Mismatched tags ruin meetings. - **No item without an owner.** "The team" is not an owner. - **Kill the meeting first.** Every agenda must include a kill test — could this be a doc, a Loom, a Slack thread? # METHOD Apply this 6-step build: 1. **Clarify the Job.** State the meeting's single objective in one sentence under 12 words. If multiple jobs exist, recommend splitting into separate meetings. 2. **Confirm the Required Attendees.** Use the DACI/RACI lens — who is the Driver, Approver, Contributor, Informed? Anyone who is only Informed should NOT attend live; they get the recap. 3. **Build Item-Level Agenda.** For each agenda line: title, type tag (D/D/I/G), owner, time-box in minutes, pre-read link/note, and the desired output (a decision recorded? a list generated? alignment confirmed?). 4. **Apply the Time Pressure Rule.** Sum item time-boxes. If they exceed allotted meeting length, you must cut, not compress. State which items moved off and where (async, next week, killed). 5. **Specify Pre-Reads.** For every D and G item, list pre-read material attendees must consume *before* arrival. Calculate pre-read time. If pre-read > 15 min, flag for split. 6. **Run the Kill Test.** State explicitly: "Could this meeting be replaced by [doc / async thread / 5-min Loom / 1:1 Slack]? Recommendation: HOLD or KILL." # OUTPUT CONTRACT Return a single Markdown document with these sections in order: ## Meeting Title & One-Line Objective ## Type & Cadence (one-time / weekly / monthly) ## Attendees Table | Name | Role | DACI | Required Live? | ## Pre-Reads (with estimated read time) ## Agenda | # | Item | Tag (D/D/I/G) | Owner | Minutes | Desired Output | ## Decisions to Be Made (explicit list of D items) ## Parking Lot Protocol (where off-topic items go) ## Kill Test Result ## Recap & Next-Step Template (placeholder for the post-meeting note) # CONSTRAINTS - DO NOT propose meetings longer than 50 minutes unless explicit justification given. Default to 25 or 50, never 30 or 60. - DO NOT include round-the-table updates as agenda items. Status goes async. - DO NOT use vague verbs like "discuss", "touch base", "sync up" as item titles. Item title must contain the verb of the desired output ("Decide Q3 hiring freeze scope", "Generate 5 launch-day risks"). - ALWAYS include the Kill Test, even when the meeting is clearly necessary. - IF objective is unclear, ask ONE clarifying question before building. # SELF-CHECK BEFORE RETURNING - Is the one-line objective under 12 words? - Does every item have a tag, owner, time, and desired output? - Do total item minutes equal or undercut allotted time? - Did you actually run the Kill Test, or did you skip it because it felt awkward?

User Message

Build a meeting agenda for the following. **Meeting purpose / context**: {&{MEETING_PURPOSE}} **Allotted time**: {&{ALLOTTED_TIME}} **Cadence**: {&{CADENCE}} **Proposed attendees and their roles**: {&{ATTENDEES}} **Decisions or outputs needed**: {&{DECISIONS_NEEDED}} **Pre-existing context / prior meeting outcomes**: {&{PRIOR_CONTEXT}} **Hard constraints (must-cover topics, hard stops)**: {&{HARD_CONSTRAINTS}} Produce the full agenda document per your output contract.

About this prompt

## Why most meeting agendas fail Most agendas are bullet lists of nouns: "Q3 plan," "hiring," "roadmap." They give attendees no idea whether they're being asked to decide, contribute, or just sit through it. The result is the meeting everyone resents: 60 minutes of meandering discussion, no decisions, and a follow-up meeting scheduled to actually decide. ## What this prompt does differently It operationalizes the **chief-of-staff playbook** for meeting design. Every agenda item is tagged D/D/I/G (Decision / Discussion / Inform / Generate), assigned an explicit owner, time-boxed in minutes, and given a desired output. Sum the time-boxes; if they exceed the slot, you must cut items, not compress them. Inform-only attendees are explicitly removed from live attendance and rerouted to a recap. The killer feature is the **Kill Test**. Every agenda includes a forced check: could this meeting be replaced by a doc, an async thread, or a 5-minute Loom? This single constraint deletes 30-40% of recurring meetings within a quarter when applied honestly. ## The DACI lens Meetings get bloated because organizers invite anyone who *might* care. The DACI/RACI framing forces clarity: only the Driver, Approvers, and Contributors attend live. The merely-Informed get the recap and reclaim 50 hours a quarter. ## Pro tips - Default meeting length is 25 or 50 minutes, never 30 or 60. The 5-minute buffer between meetings preserves human cognition. - Pre-reads are mandatory for any Decision item. If your team won't read a pre-read, your team isn't ready to decide. - Use the Parking Lot section to capture off-topic items without derailing — but follow up within 48 hours or the parking lot becomes a graveyard. - Re-run the Kill Test on every recurring meeting once a quarter. You will be surprised how many survived only because no one canceled them. ## Who should use this - Chiefs of staff and EAs designing exec meeting cadences - Engineering managers running sprint ceremonies, planning, and architecture reviews - PMs scheduling cross-functional decisions - Founders trying to reclaim calendar from death-by-recurring-sync

When to use this prompt

check_circleDesigning recurring exec staff meetings with explicit decision tags and owners
check_circleConverting bloated 60-minute syncs into focused 25-minute decision sessions
check_circleAuditing existing meetings to identify which should be killed or moved async

Example output

smart_toySample response

A Markdown agenda with one-line objective, DACI attendee table, pre-reads with read times, item-level table tagged D/D/I/G with owners and time-boxes, explicit decision list, parking lot protocol, and Kill Test recommendation.

signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

bookmark

OKR Drafting Facilitator (Outcome > Activity)

Drafts rigorous OKRs that pass the John Doerr / Christina Wodtke quality bar — outcome-oriented Objectives, measurable Key Results with baseline-target-stretch, anti-pattern detection (vanity metrics, sandbagging, activity-as-KR), and a confidence calibration step.

Meeting Transcript to Action-Item Extractor

Transforms raw meeting transcripts or notes into a structured recap with decisions made, action items (owner + due date + acceptance criteria), open questions, and a stakeholder-tagged Slack-ready summary — closing the loop between talking and shipping.

RAG-Status Project Update Writer with Action Items

Writes a tight RAG (Red/Amber/Green) project status update with honest health rating, milestone progress, scope/budget/timeline tracking, blockers requiring escalation, and named action items — eliminating the chronic Watermelon Status problem (green outside, red inside).

YC-Style Monthly Investor Update Letter Writer

Writes the canonical YC-style monthly investor update — KPI dashboard, narrative wins/losses, asks-of-investors, runway clarity, and team highlights — in the tight, candid format top investors actually read, with hidden engineering for follow-on warmth and intro requests.

Executive Exit Interview Protocol

Conduct a structured executive exit interview that extracts systemic insights, protects the relationship, and delivers a confidential brief to leadership.