functional-design

Convert PRDs into functional design documents with system diagrams and data models.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yuch4/dx-selecta --skill functional-design-yuch4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: functional-design
Source: https://github.com/yuch4/dx-selecta/tree/main/.claude/skills/functional-design
Command: npx skills add https://github.com/yuch4/dx-selecta --skill functional-design-yuch4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill converts PRDs into actionable functional design documents, ensuring alignment between requirements and design while reducing manual effort.

Core Features & Use Cases

  • Output documentation: generates/updates docs/functional-design.md from PRD.
  • Input integration: reads docs/product-requirements.md (required) to extract MVP requirements, user flows, and non-functional requirements.
  • Output artifacts: creates sections for system architecture diagrams, data models, ER diagrams, use-case flows, and error handling.
  • Use-case examples: fills design items from existing PRD and supports incremental updates.
  • References: leverages references/template.md and references/guide.md as baselines.

Quick Start

Place the PRD at docs/product-requirements.md and run the skill to generate docs/functional-design.md. If docs/functional-design.md already exists, the tool will update it while preserving user-added content. The templates in references provide a baseline when creating a new doc.

Frequently Asked Questions about functional-design

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

FAQPage Schema
How do I generate a functional design document from a PRD?

To generate a functional design document from a PRD, place your product requirements at docs/product-requirements.md and run the skill to automatically map requirements into system architecture, data models, and use-case flows.

What is included in a functional design document for software engineering?

A functional design document includes sections for system architecture diagrams, data models, ER diagrams, component responsibilities, use-case flows, and error handling to guide implementation from product requirements.

Does generating a functional design doc overwrite existing content?

Generating a functional design doc does not overwrite existing content; if docs/functional-design.md already exists, the tool updates it while preserving user-added content and supporting incremental updates.

Do I need a specific PRD format to create system diagrams and data models?

You need your PRD placed at docs/product-requirements.md to create system diagrams and data models, ensuring the skill can extract MVP requirements, user flows, and non-functional requirements accurately.

What's the best way to map non-functional requirements into an ER diagram?

The best way to map non-functional requirements into an ER diagram is using a baseline template from references, transforming extracted PRD data into structured data models and component responsibilities automatically.