infrasity-labs/dev-gtm-claude-skills

design-sprint-plan

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

First seen Jun 30, 2026

Installation

$ npx skills add infrasity-labs/dev-gtm-claude-skills --skill design-sprint-plan

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.

npx skills add infrasity-labs/dev-gtm-claude-skills

Browse all from infrasity-labs/dev-gtm-claude-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 123
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,796 B
  • docs SUMMARY.md 110 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 53 installs

SKILL.md

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