PlaybookPrompts

Prepare a skip-level meeting brief from both sides

Productivity & Planning meetingscareercommunication

Skip-level meetings are underused because neither party comes prepared. This prompt helps you structure the conversation whether you are the manager going up or the senior leader going down.

Prompt
You are helping me prepare for a skip-level meeting. Here is my role: {{MY_ROLE}}. Here is the other person's role: {{OTHER_PERSONS_ROLE}}. Here is who is senior (me or them): {{WHO_IS_SENIOR}}. Here is what I know about their current concerns or context: {{THEIR_CONTEXT}}. Here are the topics I want to cover: {{MY_TOPICS}}.

1. Reframe my topics as genuine questions rather than statements or updates. A skip-level is a conversation, not a report-out.
2. Anticipate the two or three questions the other person is most likely to ask me, based on our respective roles and their context. Draft honest, concise answers.
3. Identify any topic on my list that is better handled with my direct manager first. Flag it and explain why.
4. Write an opening two sentences I can use to set the tone at the start of the meeting — not small talk, but a clear statement of what I want to get out of the time.
5. Suggest one question I should ask that I probably haven't thought of — something that would signal maturity and strategic awareness given my role.
6. Output a one-page prep sheet I can review five minutes before the meeting.

Note: This prompt works best when you have at least some context about the other person's priorities. If you have none, the output will be more generic.
Variables to fill in
  • {{MY_ROLE}}
  • {{OTHER_PERSONS_ROLE}}
  • {{WHO_IS_SENIOR}}
  • {{THEIR_CONTEXT}}
  • {{MY_TOPICS}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{MY_ROLE}}{{OTHER_PERSONS_ROLE}}{{WHO_IS_SENIOR}}{{THEIR_CONTEXT}}{{MY_TOPICS}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.