design-sprint-plan
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
Works with
--- name: design-sprint-plan description: Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`. license: MIT --- # 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
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

