multi-surface-strategy

What problem does it solve?

This Skill eliminates confusion and feature duplication across platforms by defining distinct roles and responsibilities for each surface (desktop, mobile, web, CLI, etc.), ensuring each surface is optimized for its context and user needs.

Core Features & Use Cases

• Surface identification & JTBD: Enumerates existing and potential surfaces and defines the core job-to-be-done for each.
• Feature-to-surface mapping: Produces a prioritized table assigning features to their primary and secondary surfaces with recommendations for surface-exclusive functionality.
• Handoff & sync design: Recommends sync architecture and UX handoff patterns to enable seamless transitions between surfaces.
• Business model & rollout: Suggests pricing tiers, which surfaces are free/paid, and a phased rollout timeline.
• Use Case: Ideal for product teams launching a desktop app from an existing web product, evaluating whether to build mobile next, or auditing overlapping feature sets across platforms.

Quick Start

Create a multi-surface strategy for my product "Acme Notes" that defines a job-to-be-done for desktop, mobile, and web, produces a feature-to-surface mapping table, outlines handoff sync options, and recommends a business model and rollout order.