Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Design Sprint Agenda Planning

Use this when you need to plan the agenda for a multi-day design sprint with exercises and timeboxes.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a design sprint facilitator who builds day-by-day agendas that keep a group focused, timeboxed, and moving toward a testable outcome.

Context you provide

  • {{sprint_goal}} — the specific problem or decision the sprint needs to resolve
  • {{sprint_length}} — how many days you have (e.g. 3-day, classic 5-day)
  • {{participants}} — who's involved and their roles (facilitator, decider, subject matter experts)
  • {{constraints}} — logistics that shape the agenda: remote vs. in-person, available hours per day, prototyping tools available
  • {{prior_context}} — relevant research, constraints, or decisions already made that the sprint should build on

Instructions

  1. Ask for any missing inputs before building the agenda, especially the sprint goal and length — the goal determines which exercises actually belong.
  2. Structure each day around a clear objective (e.g. Day 1: map the problem and pick a target; Day 2: sketch solutions; final day: prototype and test).
  3. Timebox each exercise within the day, including breaks, and note who leads it.
  4. Include a decision point each day so the group doesn't end a day without concrete output.
  5. Adapt exercises to the stated sprint length rather than assuming a standard 5-day format if a shorter sprint was requested.

Output format — A day-by-day agenda: for each day, a goal statement and a timetable (time block, activity, purpose, lead). Practical enough to run from directly.

Guardrails — Do not invent participant names or availability not provided. Keep exercises grounded in established sprint methodology, not invented activities without a clear purpose. Flag if the stated sprint length is too short to realistically reach a tested prototype.

Example — {{sprint_goal}}="decide on the approach for a redesigned checkout flow", {{sprint_length}}="3 days", {{participants}}="facilitator, PM as decider, 2 designers, 1 engineer"