design-sprint

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product decision, or wants to de-risk a costly idea before investing in development. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday. For ongoing experimentation and MVPs, see lean-startup. For customer job analysis, see jobs-to-be-done. For non-leading user interviews, see mom-test.

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured facilitation skill with concrete, sequenced guidance and excellent progressive disclosure into real reference files. The only weakness is minor non-essential padding (author bio, affiliate book link, marketing intro) that inflates the token budget without aiding execution.

Suggestions

Remove or trim the "About the Author" section and the Amazon affiliate Further Reading link — they add tokens without helping Claude run a sprint.

Trim the marketing-style framing in the intro ("used by Google, Slack, Airbnb, and hundreds of startups") to a single lean sentence.

Consider moving the Common Mistakes and Quick Diagnostic tables into a reference file to keep SKILL.md as a tighter overview, since the per-day reference files already absorb detail.

Dimension	Reasoning	Score
Conciseness	The day-by-day body is dense and actionable, but minor padding could be trimmed — the "About the Author" bio, the Amazon affiliate Further Reading link, and the marketing-style intro ("used by Google, Slack, Airbnb, and hundreds of startups") add tokens Claude does not need.	4 / 5
Actionability	Highly concrete throughout: hard time-boxes (Crazy 8s in 8 min, 45-min interviews), a role assignment table, a timed Five-Act Interview, prototype checklists, a 10-point scoring rubric, and a common-mistakes table — fully executable facilitation guidance.	5 / 5
Workflow Clarity	The Monday-to-Friday spine is clearly sequenced with per-day morning/afternoon structure, explicit prerequisites, per-day outputs, and checkpoints (Thursday trial run, Friday debrief decision, the 10/10 scoring audit and Quick Diagnostic).	5 / 5
Progressive Disclosure	The body is an overview that signals nine one-level-deep reference files (facilitation, monday–friday, recruiting, case-studies, remote-sprints), each introduced with a one-line purpose statement; all referenced paths resolve to real bundle files, giving clean navigation.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does, when to trigger it via natural user phrases, and how it differs from adjacent skills. Every dimension lands at the top anchor with no vague fluff.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "prototype, test, and validate product ideas with real users" and "Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday" — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what ("Run a structured 5-day process to prototype, test, and validate") and when ("Use when the user mentions...", "Also trigger when...") with concrete trigger phrases, and adds disambiguation pointers to related skills.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("design sprint", "validate before we build", "rapid prototype", "test with users", "should we build this") plus situational triggers like "stuck in endless debate over a high-stakes product decision".	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (the GV-style 5-day design sprint) with distinct triggers and explicit boundary pointers to lean-startup, jobs-to-be-done, and mom-test, minimizing wrong-skill activation.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wondelai/skills
Path: design-sprint/SKILL.md
Commit: c172996

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.