Login
owl-listener/designer-skills1 file

Design Sprint Plan

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

Use this skillView repositoryView on skills.sh
Specification
Skill ID
owl-listener/designer-skills/design-sprint-plan
Publisher
owl-listener
Repository
designer-skills
Installs
0
Files
1
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

owl-listener/designer-skills/design-sprint-planInstalls these files
  • SKILL.md

What this skill tells the agent

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

More from owl-listener

owl-listener/designer-skills

A B Test Design

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

owl-listener/designer-skills

Accessibility Audit

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

owl-listener/designer-skills

Accessibility Test Plan

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Use this skill in a project

Open any RiverX project, search the Skills panel for owl-listener/designer-skills/design-sprint-plan, and install it in one click.

Use this skill