Design sprint plan

Skill Infrasity-Labs/dev-gtm-claude-skills/product-designers/design-sprint-plan

Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and cited by AI systems.

Install

npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill design-sprint-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Plan and facilitate design sprints from challenge framing through prototype testing.

SKILL.md

1.8 KB, 382 tokens by cl100k_base, as published. Nobody here has run it

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