design-sprint

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

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill design-sprint-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-sprint
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/design-sprint
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill design-sprint-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams often spend months debating and building products without knowing if customers actually want them. This Skill compresses that risk into a structured five-day process that maps the problem, sketches solutions, picks a winner, builds a realistic prototype, and tests it with five real users before any production code is written. ## Core Features & Use Cases - Day-by-Day Sprint Facilitation: Step-by-step exercises for Map, Sketch, Decide, Prototype, and Test phases, including Crazy 8s, HMW notes, storyboarding, and the Five-Act Interview. - Decision & Prototyping Frameworks: Structured voting (heat maps, straw polls, Decider supervote) and guidance on building facade prototypes with tools like Figma or Keynote. - User Testing Playbook: Interview scripts, note-taking grids, and pattern-recognition methods for extracting clear findings from five customer interviews. - Use Case: A product team debating three onboarding redesigns runs a sprint: Monday they map the signup journey, Wednesday the Decider picks one solution, Thursday they build a clickable Figma facade, and Friday five target users reveal which flow actually works. ## Quick Start Ask the assistant to plan and facilitate a five-day design sprint for your product challenge, starting with Monday's mapping exercises.

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 vote and storyboard the winner, Thursday build a realistic facade prototype, and Friday test it with five target customers using structured interviews.

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

Test with five customers. Patterns emerge after three to five interviews, returns diminish after five, and five one-hour sessions fit in a single day. Recruit six participants to cover one expected no-show.

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

Yes. Remote sprints use digital whiteboards like Miro or FigJam for mapping and sketching, and video calls for interviews, while keeping the same five-day schedule and exercises. The skill includes a dedicated remote-sprints reference.

When should I not run a design sprint?▼

Skip a sprint when the problem is clear and the solution obvious, when you only need execution, when the team is not bought in, or when the decision maker cannot commit to the full week. Sprints are for high-stakes, ambiguous challenges.

What fidelity should a design sprint prototype have?▼

Aim for Goldilocks fidelity: realistic enough to get honest reactions but not working code. Use linked slides in Keynote, Figma click-throughs, or video walkthroughs that can be built in one day and walked through in five to fifteen minutes.