Skip to content
cccskills
FreePublished on GitHub

design-sprint-plan

Plan and facilitate a design sprint that moves a team from a defined challenge to a tested prototype in days. Organize daily activities, roles, preparation, user interviews, and follow-up, with shorter and remote variations.

OriginalShow the original description

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

Run score Not tested

See how to install

Good for

  • Planning a five-day sprint from challenge to user testing
  • Compressing a smaller challenge into a two- or three-day sprint
  • Adapting sprint activities for a distributed team
  • Preparing prototype tests and follow-up decisions

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a-b-test-design

FreeSummary

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

affinity-diagram

FreeSummary

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill