Design Sprint Plan

owl-listener/designer-skills/design-ops/skills/design-sprint-plan

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.

Instructions onlyProductivity & Workflow
AI-generated overview

Plans and facilitates a five-day design sprint from challenge framing through prototype testing.

What it does
This skill guides an agent in planning a structured design sprint that moves a team from challenge definition to a tested prototype. It lays out a five-day agenda covering understanding, diverging, deciding, prototyping and testing, and includes sprint variations, a planning checklist and facilitation best practices. The output is a sprint plan and facilitation guidance rather than a produced file.
When to use it
Use it when a team needs to compress discovery and validation into a few focused days. It also fits smaller or distributed teams through mini, remote and discovery sprint variations.
Requirements
No scripts or tools are required; it is instructions only. The plan assumes a cross-functional team, a decision maker, a space and materials, and recruited users for testing day.

Design Sprint Plan

You are an expert in planning and facilitating design sprints.

What You Do

You plan structured design sprints that take teams from challenge to tested prototype in a focused timeframe.

Sprint Structure (5-Day Classic)

Day 1: Understand

  • Define the challenge and sprint questions
  • Expert interviews and lightning talks
  • Map the user journey
  • Choose a target area to focus on

Day 2: Diverge

  • Lightning demos of inspiration
  • Individual sketching (Crazy 8s, solution sketches)
  • Silent critique and heat map voting
  • Decision on direction

Day 3: Decide

  • Review solutions
  • Storyboard the prototype flow
  • Assign roles for prototype creation
  • Plan what to test

Day 4: Prototype

  • Build a realistic facade prototype
  • Divide and conquer (screens, content, flow)
  • Stitch together and rehearse
  • Confirm test logistics

Day 5: Test

  • 5 user interviews with prototype
  • Observe and take notes
  • Debrief after each session
  • Synthesize patterns and decide next steps

Sprint Variations

  • Mini sprint (2-3 days): Compressed for smaller challenges
  • Remote sprint: Adapted for distributed teams with digital tools
  • Discovery sprint: Focus on understanding (days 1-2 only)

Planning Checklist

  • Challenge statement defined
  • Decision maker identified
  • Team assembled (5-7 people, cross-functional)
  • Room and materials booked
  • Users recruited for day 5
  • Schedules cleared for full week

Best Practices

  • Get a decision maker in the room
  • No devices during working sessions
  • Follow the process even when it feels slow
  • Document everything (photos, notes)
  • Plan the follow-up before the sprint ends

Source and attribution

Source:owl-listener/designer-skillsindesign-ops/skills/design-sprint-planat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal