tool-design-sprint-sketch
starsforks
How to install tool-design-sprint-sketch?
product-on-purpose/pm-skills/tool-design-sprint-sketch
$npx -y skills add product-on-purpose/pm-skills --skill tool-design-sprint-sketchDay 2 (Tuesday) move of a Design Sprint that structures lightning demos and the four-step independent solution sketch protocol (Notes, Ideas, Crazy 8s, Solution Sketch). Each team member produces one solution sketch individually; the skill orchestrates the day but does not author
SKILL.md
| 1 | <!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> |
| 2 | |
| 3 | # Design Sprint Sketch (Tuesday) |
| 4 | |
| 5 | Structure Tuesday's solo-but-together work. Each team member, working independently and silently, produces lightning demos in the morning and a four-step solution sketch in the afternoon. The skill structures the activity; the humans produce the sketches. Wednesday's heat-map orientation depends on having a cohort of independent sketches that did NOT contaminate each other through group brainstorming. |
| 6 | |
| 7 | Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This skill is a member of `design-sprint-skills`. |
| 8 | |
| 9 | ## When to Use |
| 10 | |
| 11 | - It is Day 2 of the Design Sprint and Monday's Map and Target artifact is signed off. |
| 12 | - Each team member brings at least 3 lightning demo sources (existing products, references, analogies that bear on the challenge). |
| 13 | - The team has accepted the silent-independent-sketching constraint and will NOT lapse into group brainstorming. |
| 14 | - Sketches are due Tuesday end-of-day for Wednesday morning heat-map. |
| 15 | |
| 16 | ## When NOT to Use |
| 17 | |
| 18 | - Monday is not closed. Return to `tool-design-sprint-map-and-target`. |
| 19 | - The team's instinct is to brainstorm as a group. Sprint method explicitly avoids this; if the team will not commit to independent work, the sprint will not produce diverse sketches and the heat-map becomes a popularity contest. |
| 20 | - The sketch step is being treated as the prototype. Sketches are concept exploration on paper or Figma frames, not Thursday's working prototype. |
| 21 | - Sketches are due Tuesday morning. Tuesday is the full day; rushing to lunch produces sketches the team cannot read Wednesday. |
| 22 | |
| 23 | ## What This Skill Produces |
| 24 | |
| 25 | A single bundled artifact with four sections: |
| 26 | |
| 27 | 1. **Lightning demo board**: each team member presents 3 demos (3 minutes each); the Facilitator extracts the reusable pattern from each demo into a one-line note. Result is a board with 12-21 patterns (4-7 team members x 3 demos). |
| 28 | 2. **Sketch assignment plan**: divide (each person sketches a different part of the target moment) or swarm (everyone sketches the same target). Default is swarm for v0.1 Design Sprints; divide is for teams running their second sprint with the same target who want to broaden coverage. |
| 29 | 3. **Four-step sketches from each team member**: Notes (20 min reviewing Monday output + lightning demos), Ideas (20 min rough doodles), Crazy 8s (8 minutes, 8 variations of the strongest Idea), Solution Sketch (30-90 min final 3-panel storyboard-style sketch). |
| 30 | 4. **Recruiting tracker update**: Riley (or the recruiter) confirms Friday slots; surfaces any cancellations and triggers buffer-slot activation if needed. |
| 31 | |
| 32 | See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog Tuesday artifact. |
| 33 | |
| 34 | ## Tuesday Time Structure |
| 35 | |
| 36 | The full Tuesday workshop is approximately 7 hours (09:00-12:30 + 13:30-17:00). The skill's bundled artifact emerges across the day: |
| 37 | |
| 38 | - **09:00-09:15**: Welcome + Monday recap + Tuesday agenda |
| 39 | - **09:15-10:45**: Lightning demos (each person 3 demos x 3 min + 1 min Facilitator extraction = ~12 min per person; 4-person team = ~50 min; 7-person team = ~85 min) |
| 40 | - **10:45-11:00**: Break |
| 41 | - **11:00-11:30**: Sketch assignment plan + Notes step (each person silently reviews Monday output and lightning demo board) |
| 42 | - **11:30-12:30**: Ideas step (each person silently doodles ideas in their notebook or Figma frame) |
| 43 | - **12:30-13:30**: Lunch + (in parallel) recruiting tracker check-in |
| 44 | - **13:30-13:40**: Crazy 8s (8 minutes, 8 variations of strongest Idea) |
| 45 | - **13:40-15:30**: Solution Sketch (final 3-panel |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
