design-ops
Run design sprints, manage handoff, establish team rituals, documentation standards, and design QA processes. Covers the operational side of design — how teams organize work, collaborate with engineering, and ship quality.
cuellarfr · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add cuellarfr/design-skills --skill design-opsAbout this skill
name: design-ops description: Run design sprints, manage handoff, establish team rituals, documentation standards, and design QA processes. Covers the operational side of design — how teams organize work, collaborate with engineering, and ship quality.
Design Ops & Handoff
Operational processes that make design teams effective — sprints, handoff, rituals, documentation, and quality assurance.
Design Sprints
A 5-day process for solving big problems and testing ideas before committing engineering resources. Based on Jake Knapp's Sprint methodology developed at Google Ventures.
When to Sprint
| Signal | Sprint Is Right | Sprint Is Wrong |
|---|---|---|
| Problem clarity | Big problem, unclear solution | Solution already known — just build it |
| Stakes | High — wrong direction costs months | Low — easy to course-correct later |
| Team alignment | Disagreement on approach | Team already aligned |
| Time pressure | Need answers this week | Can run a longer discovery process |
| Complexity | Cross-functional problem | Single-discipline task |
The 5-Day Structure
| Day | Focus | Key Activity | Output |
|---|---|---|---|
| Monday | Map | Define the challenge, set a 2-year goal, map the problem space, pick a target | Sprint questions, problem map, target area |
| Tuesday | Sketch | Review existing solutions, each person sketches solutions individually | Solution sketches (one per person) |
| Wednesday | Decide | Present sketches, vote (dot voting + decider picks), create storyboard | Storyboard for prototype |
| Thursday | Prototype | Build a realistic facade — just enough to test | Testable prototype |
| Friday | Test | 5 user interviews, observe together, identify patterns | Go/no-go decision with evidence |
Sprint Team
| Role | Count | Responsibility |
|---|---|---|
| Decider | 1 | Has authority to make final calls. Usually PM or founder |
| Facilitator | 1 | Runs the process, keeps time, manages energy |
| Designer | 1-2 | Leads sketching, builds prototype |
| Engineer | 1-2 | Feasibility gut-checks, helps prototype |
| Domain expert | 1-2 | Customer support, sales, marketing — whoever knows the user |
| Total | 5-7 | More than 7 is counterproductive |
Sprint Rules
- No devices during working sessions — full attention
- Work alone together — individual sketching, not group brainstorming
- The Decider decides — democracy is slow; one person breaks ties
- Prototype, don't build — facade quality, not production quality
- 5 users is enough — you'll see 85% of usability issues with 5 participants
Design-to-Development Handoff
Handoff is the #1 source of quality loss in product teams. The goal: engineers should never have to guess.
Handoff Maturity Levels
| Level | Description | Symptom |
|---|---|---|
| 1. Screenshot | Designer sends a static image | Engineers guess spacing, states, behavior |
| 2. Annotated mockup | Redlines, spacing callouts | Better, but still missing states and edge cases |
| 3. Interactive spec | Figma/design tool with inspect mode, component links | Engineers can extract values, but behavior is undocumented |
| 4. Full spec | All states, transitions, error handling, responsive behavior, tokens | Engineers build exactly what was designed |
| 5. Integrated | Design and code share a component system; handoff is a conversation, not a document | Minimal spec needed — shared language does the work |
Target: Level 4 minimum. Level 5 for mature teams.
What a Complete Handoff Includes
Every screen or component handoff must cover:
| Category | Required Items |
|---|---|
| Layout | Spacing (in tokens, not pixels), alignment, responsive breakpoints, container behavior |
| Content | Final copy (not lorem ipsum), character limits, truncation rules, localization notes |
| States | Default, hover, focus, active, disabled, loading, empty, error, success — for every interactive element |
| Behavior | What happens on click/tap, keyboard interaction, drag, swipe. Transition details |
| Responsive | How the layout adapts at each breakpoint. What reflows, stacks, hides, or changes |
| Tokens | Color tokens, typography tokens, spacing tokens — never raw hex/px values |
| Accessibility | Focus order, ARIA roles, screen reader announcements, touch targets, color contrast |
| Edge cases | Long strings, empty data, error recovery, offline behavior, permissions |
| Assets | Icons (SVG), images (with alt text), animations (specs or files) |
Handoff Anti-Patterns
| Anti-Pattern | Problem | Fix |
|---|---|---|
| "It's in Figma" | No context, engineer must reverse-engineer intent | Write behavior notes on every frame |
| Happy path only | Only the ideal flow is designed | Design all states before handoff |
| Pixel specs | "24px left margin" | Use tokens: spacing-md |
| Verbal handoff | "I'll explain it in standup" | If it's not written down, it doesn't exist |
| Big-bang handoff | Entire feature dropped on engineering at once | Hand off in slices that match sprint stories |
| No error states | "We'll figure out errors later" | Error states are designed first, not last |
Team Rituals and Cadences
Core Design Rituals
| Ritual | Frequency | Duration | Purpose | Who Attends |
|---|---|---|---|---|
| Design critique | Weekly | 45-60 min | Improve work-in-progress through structured feedback | All designers |
| Design-eng sync | Weekly | 30 min | Align on upcoming work, resolve handoff questions | Design lead + eng lead |
| Design review | Per milestone | 30-60 min | Stakeholder sign-off on direction | PM, design, eng leads, stakeholders |
| Handoff session | Per story/feature | 30-45 min | Walk engineering through sp |