Skip to content
Marketplace

design-sprint-plan

by owl-listener

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`.

Overview

SKILL.mdRead at 9a6930c

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

Files 1 file

Install it by hand

Deska runs this for you, for every agent you pick. To run it yourself in a terminal:

npx skills add owl-listener/designer-skills --skill design-sprint-plan

More from owl-listener

  • presentation-deckowl-listenerStructure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.2,800 installs on skills.sh0
  • typography-scaleowl-listenerCreate a modular type scale with size, weight, and line-height relationships. Use when establishing typographic structure. For line length only use `readable-measure`; for judging type on an existing screen use `critique-typography` (visual-critique).2,300 installs on skills.sh0
  • visual-hierarchyowl-listenerEstablish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).2,300 installs on skills.sh0
  • color-systemowl-listenerBuild a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).2,200 installs on skills.sh0
  • dark-mode-designowl-listenerAdapt an existing palette to dark mode — surface elevation, contrast rebalancing, and desaturation rules. Use when you already have a light palette to translate. For building the base palette first, use `color-system`.2,200 installs on skills.sh0
All skills by owl-listener