design-to-prdlisted

# Design-to-PRD Translator Transform conceptual and design documentation into structured requirements, user stories, and complete PRDs. --- ## The Job 1. Receive design documentation (vision docs, concept docs, wireframes, architecture docs, etc.) 2. Analyze and extract core concepts, goals, and features 3. Identify stakeholders and user personas 4. Generate structured requirements 5. Create user stories with acceptance criteria 6. Produce a complete PRD ready for implementation **This is a meta-workflow that bridges the gap between "idea" and "actionable specification."** --- ## Supported Input Types This skill handles various conceptual document types: | Document Type | What to Extract | |--------------|-----------------| | **Vision Document** | Goals, success metrics, target users, high-level features | | **Concept Document** | Problem statement, proposed solution, key capabilities | | **Wireframes/Mockups** | UI elements, user flows, interactions, states | | **Architecture Doc** | Components, integrations, data models, constraints | | **Meeting Notes** | Decisions made, requirements mentioned, action items | | **Brainstorm/Ideas** | Core features, nice-to-haves, out-of-scope items | | **Competitor Analysis** | Features to include, features to differentiate | | **User Research** | Pain points, needs, desired outcomes | --- ## Phase 1: Document Analysis First, understand what you're working with. ### Ask These Clarifying Questions: ``` 1. What type of document