design-to-prd

## What problem does it solve? Manually translating design documents into product requirements documents is time-consuming, inconsistent, and often leads to missing context for leadership and engineering stakeholders. This Skill automates the process, ensuring PRDs are structured, gap-aware, and aligned with both business and technical needs.

## Core Features & Use Cases

• Multi-format input support: Accepts PDF design specs, Figma exports, and markdown design notes as input.
• Structured PRD generation: Produces a standardized 11-section PRD tailored for both executive readers (TL;DR, problem, success metrics) and engineering readers (functional requirements, key flows, dependencies).
• Gap handling: Explicitly marks missing information as TBD instead of inventing unsupported context, metrics, or personas.
• Confluence publishing: Optionally publishes the finished PRD directly to a specified Confluence space and parent page with correct formatting.
• Use case: A product manager receives a PDF design spec for a new expense report feature from the design team, and uses this Skill to generate a complete, publication-ready PRD in minutes, with all required sections and open questions flagged for follow-up.

### Quick Start Use the design-to-prd skill to turn the attached calendar sync v2 design notes into a high-level PRD and publish it to the Product team's Confluence space.