design-sprint

Guides a five-day design sprint to prototype and test product ideas with real users.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/HafidJoss/Lummy --skill design-sprint-hafidjoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-sprint
Source: https://github.com/HafidJoss/Lummy/tree/main/agent/skills/design-sprint
Command: npx skills add https://github.com/HafidJoss/Lummy --skill design-sprint-hafidjoss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? High-stakes product decisions often stall in months of debate, and teams risk building features nobody wants. This Skill compresses mapping, sketching, deciding, prototyping, and user testing into a structured Monday-to-Friday sprint so teams get real user evidence before writing production code. ## Core Features & Use Cases - Day-by-Day Sprint Playbook: Detailed facilitation guidance for each phase — Monday mapping, Tuesday sketching, Wednesday deciding, Thursday prototyping, and Friday testing with five target users. - Scoring and Diagnostics: A 10-point scoring rubric and quick diagnostic table to audit any sprint plan and identify failure modes like a missing Decider or untested prototype. - Deep Reference Guides: Facilitation tactics, recruiting screeners, remote sprint adaptations, Five-Act Interview scripts, and real case studies from Slack, Blue Bottle, and Savioke. - Use Case: A product team debating whether to build a new onboarding flow runs a sprint: they map the journey Monday, sketch solutions Tuesday, pick one Wednesday, build a Figma facade Thursday, and watch five target users test it Friday — ending the week with a validated or rejected concept. ## Quick Start Ask the AI to plan a five-day design sprint for your product challenge, including the daily schedule, team roles, and Friday user-testing plan.

Frequently Asked Questions about design-sprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a design sprint for a product idea?

Follow the five-day structure: Monday map the customer journey and pick a target, Tuesday sketch solutions individually, Wednesday critique and let the Decider supervote, Thursday build a realistic facade prototype, and Friday test with five target users using the Five-Act Interview.

How many users should I test with in a design sprint?

Test with exactly five target users recruited through a screener survey, scheduling six to absorb a no-show. Patterns emerge after three to five interviews, and returns diminish beyond five, making five the efficient number for one day of testing.

Can a design sprint be run remotely with a distributed team?

Yes, remote sprints adapt each exercise to tools like Miro or FigJam for whiteboarding, Zoom for interviews, and Figma for prototyping. The references include time-zone strategies, async versus sync guidance, and energy management for screen fatigue.

When should you not run a design sprint?

Skip the sprint when the problem and solution are obvious and only execution remains, when the team is not bought in, or when the Decider cannot commit to the full week. Without a committed Decider, the sprint cannot produce binding decisions.

What fidelity should a design sprint prototype have?

Aim for Goldilocks fidelity: a realistic facade built in Keynote, Figma, or video that looks real enough for honest reactions but involves no working code. It should be walkable in 5-15 minutes and pass a trial run before Friday.