back_office_ops · saas · workflow
Uber builds agentic system uSpec to automate design specs in minutes instead of weeks
Uber's design systems team faced an enterprise-scale documentation bottleneck: manually producing component specs for hundreds of components across 7 implementation stacks was slow, inconsistent across authors, and drifted out of date whenever a component changed, turning documentation into a dedicated workstream that still could not keep pace.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Designer shares Figma link and context
A designer opens Cursor, references an agent skill with a Figma component link, and adds context about states, variants, or platform-specific behavior the agent cannot infer from the design alone.
Tools used
uSpecCursorFigma Console MCPFigma
Outcome
The agentic system generates complete component specs in minutes instead of weeks; a full screen reader spec covering 3 platforms now generates in under 2 minutes, and a system of hundreds of components that previously required months of spec-writing can generate complete specs in days.
Results
Time savedminutes instead of weeks
Grounding & classification
Source type: technical build writeup
25 fields verified against source quotes.
agentic workflowai agentcontent generationdocument aiknowledge basefailure mode describedmetric backednamed customerproduction runtime claimedtools describedworkflow describedsoftwarecycle time reductionemployee productivitytime savedtechnical build writeupback office opsagentic task executiondocument to record