跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

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 · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add cuellarfr/design-skills --skill design-ops

技能说明


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

SignalSprint Is RightSprint Is Wrong
Problem clarityBig problem, unclear solutionSolution already known — just build it
StakesHigh — wrong direction costs monthsLow — easy to course-correct later
Team alignmentDisagreement on approachTeam already aligned
Time pressureNeed answers this weekCan run a longer discovery process
ComplexityCross-functional problemSingle-discipline task

The 5-Day Structure

DayFocusKey ActivityOutput
MondayMapDefine the challenge, set a 2-year goal, map the problem space, pick a targetSprint questions, problem map, target area
TuesdaySketchReview existing solutions, each person sketches solutions individuallySolution sketches (one per person)
WednesdayDecidePresent sketches, vote (dot voting + decider picks), create storyboardStoryboard for prototype
ThursdayPrototypeBuild a realistic facade — just enough to testTestable prototype
FridayTest5 user interviews, observe together, identify patternsGo/no-go decision with evidence

Sprint Team

RoleCountResponsibility
Decider1Has authority to make final calls. Usually PM or founder
Facilitator1Runs the process, keeps time, manages energy
Designer1-2Leads sketching, builds prototype
Engineer1-2Feasibility gut-checks, helps prototype
Domain expert1-2Customer support, sales, marketing — whoever knows the user
Total5-7More than 7 is counterproductive

Sprint Rules

  1. No devices during working sessions — full attention
  2. Work alone together — individual sketching, not group brainstorming
  3. The Decider decides — democracy is slow; one person breaks ties
  4. Prototype, don't build — facade quality, not production quality
  5. 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

LevelDescriptionSymptom
1. ScreenshotDesigner sends a static imageEngineers guess spacing, states, behavior
2. Annotated mockupRedlines, spacing calloutsBetter, but still missing states and edge cases
3. Interactive specFigma/design tool with inspect mode, component linksEngineers can extract values, but behavior is undocumented
4. Full specAll states, transitions, error handling, responsive behavior, tokensEngineers build exactly what was designed
5. IntegratedDesign and code share a component system; handoff is a conversation, not a documentMinimal 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:

CategoryRequired Items
LayoutSpacing (in tokens, not pixels), alignment, responsive breakpoints, container behavior
ContentFinal copy (not lorem ipsum), character limits, truncation rules, localization notes
StatesDefault, hover, focus, active, disabled, loading, empty, error, success — for every interactive element
BehaviorWhat happens on click/tap, keyboard interaction, drag, swipe. Transition details
ResponsiveHow the layout adapts at each breakpoint. What reflows, stacks, hides, or changes
TokensColor tokens, typography tokens, spacing tokens — never raw hex/px values
AccessibilityFocus order, ARIA roles, screen reader announcements, touch targets, color contrast
Edge casesLong strings, empty data, error recovery, offline behavior, permissions
AssetsIcons (SVG), images (with alt text), animations (specs or files)

Handoff Anti-Patterns

Anti-PatternProblemFix
"It's in Figma"No context, engineer must reverse-engineer intentWrite behavior notes on every frame
Happy path onlyOnly the ideal flow is designedDesign 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 handoffEntire feature dropped on engineering at onceHand 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

RitualFrequencyDurationPurposeWho Attends
Design critiqueWeekly45-60 minImprove work-in-progress through structured feedbackAll designers
Design-eng syncWeekly30 minAlign on upcoming work, resolve handoff questionsDesign lead + eng lead
Design reviewPer milestone30-60 minStakeholder sign-off on directionPM, design, eng leads, stakeholders
Handoff sessionPer story/feature30-45 minWalk engineering through sp
阅读完整来源 ↗