Convert PDF specs, Figma exports, and markdown notes into structured 11-section product requirements documents.
npx skills add https://github.com/Elmanuel1/skills --skill design-to-prd
Please help me install this Agent Skill. Skill: design-to-prd Source: https://github.com/Elmanuel1/skills/tree/main/design-to-prd Command: npx skills add https://github.com/Elmanuel1/skills --skill 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
### 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.
High-intent search queries and answers about installing and using this skill.
To convert a Figma design export into a product requirements document, you can use automated tools that ingest design artifacts and generate a structured PRD. The output includes standardized sections for executives and engineers, avoiding implementation details.
Yes, you can publish a generated PRD directly to Confluence. The process optionally publishes the finished product requirements document to a specified Confluence space and parent page with correct formatting.
The best way to translate PDF design specifications into high-level requirements is using an automated design-to-PRD process. It converts design specs into an 11-section structured document, explicitly marking missing information as TBD to avoid inventing unsupported context.
Gap handling during product requirements generation explicitly marks missing information as TBD instead of inventing unsupported context, metrics, or personas. This ensures the final PRD surfaces unresolved questions for cross-team input.
A structured product requirements document generated from design artifacts includes a standardized 11-section structure. It features sections tailored for executive readers like TL;DR, problem, and success metrics, alongside functional requirements and dependencies for engineering.
johnlindquistExtract design tokens, components, and styles from Figma files.
testdoublePublish Markdown content to a Confluence page via the Atlassian MCP server.
vZulinAutomate Confluence page creation, search, labeling, and hierarchy navigation.
joseph-c-mcguireClassify product plan statements by confidence and check cross-document consistency.
