ux-collaborator

Coordinate UX workstreams by aligning product requirements with design outputs.

8|1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/officebeats/beats-pm-antigravity-brain --skill ux-collaborator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-collaborator
Source: https://github.com/officebeats/beats-pm-antigravity-brain/tree/main/.agent/skills/ux-collaborator
Command: npx skills add https://github.com/officebeats/beats-pm-antigravity-brain --skill ux-collaborator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate UX workstreams by aligning product requirements with design outputs.

Core Features & Use Cases

  • Design Alignment: ensures requirements translate into usable design artifacts.
  • Sprint 0 Enforcement: design must precede development with clear handoffs.
  • Design Ledger: logs UX tasks and progress for transparency.

Quick Start

Align the latest PRD in 2. Products with the current design notes in 4. People and generate a handoff-ready log entry.

Frequently Asked Questions about ux-collaborator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align product requirements with design outputs for UX handoffs?

To align UX design outputs with product requirements, coordinate workstreams using PRDs and designer notes to generate handoff-ready log entries. This enforces phase-based workflows, validating prerequisites like PRD links and Ready for Dev status before finalizing the design handoff.

What is the best way to coordinate UX design research and sprint planning?

Coordinate UX design research and sprint planning by enforcing a Sprint 0 workflow, ensuring design tasks precede development. Use trackers and PRD inputs to drive actionable items, logging all progress into a design ledger for full transparency.

How does a design ledger improve UX workflow transparency?

A design ledger improves UX workflow transparency by logging tasks, actions, and progress throughout the design lifecycle. It records phase-based workflow activities, ensuring product requirements, design notes, and handoff statuses are tracked and visible.

Can I use PRDs and trackers to generate actionable design review items?

Yes, you can use PRDs and trackers to generate actionable design review items. The workflow processes these inputs alongside designer notes to validate design alignment, enforcing prerequisites before transitioning artifacts to a Ready for Dev status.

Why validate Ready for Dev status before proceeding with development handoffs?

Validating Ready for Dev status before development handoffs ensures design artifacts fully align with product requirements. This phase-based enforcement prevents premature development by checking that all PRD links and design review prerequisites are met.

When do I need a phase-based workflow for UX collaboration?

A phase-based workflow for UX collaboration is needed when bridging product requirements to pixel-perfect design outputs. It ensures Sprint 0 design tasks are completed, logged, and validated before development handoffs, preventing misaligned artifacts.