design

Translate PRD requirements into architecture documentation and ADRs.

Updated Aug 27, 2026

Search Tags:#design #architecture #documentation #requirements #adr #risk-analysis

Ready to run

npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill design-gudzenkov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design
Source: https://github.com/gudzenkov/SuperClaudeZero/tree/main/.claude/skills/design
Command: npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill design-gudzenkov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates PRD requirements into architecture documentation and Architecture Decision Records (ADRs), enabling consistent design decisions and traceability across the project lifecycle.

Core Features & Use Cases

Architecture Documentation: produce ARCHITECTURE.md with components, interfaces, data flows, and constraints.
ADR Creation: generate Architecture Decision Records capturing rationales and trade-offs.
Guided Design Process: map requirements to design artifacts and validation steps.

Quick Start

Provide the PRD path or focus area to generate architecture artifacts and ADRs.

Frequently Asked Questions about design

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

FAQPage Schema

How do I translate PRD requirements into architecture documentation?▼

To generate architecture documentation from PRD requirements, provide the PRD path to map requirements into an ARCHITECTURE.md file. This artifact captures components, interfaces, data flows, and constraints.

What is an Architecture Decision Record and when do I need one?▼

An Architecture Decision Record (ADR) captures design rationales and trade-offs for specific decisions. You generate ADRs to ensure consistent design decisions and traceability across the project lifecycle.

How do I generate ADRs from existing requirements?▼

You generate ADRs from existing requirements by providing a PRD focus area. The design process maps requirements to artifacts and validation steps, outputting ADRs that capture rationales and trade-offs.

Can I map PRD constraints and risk analysis directly into design artifacts?▼

Yes, you can map PRD constraints and risk analysis into design artifacts. The architecture documentation process explicitly targets constraints, risks, and trade-offs, capturing them within generated design documents and ADRs.

What is the best way to document component interfaces and data flows?▼

The best way to document component interfaces and data flows is by generating an ARCHITECTURE.md file from your PRD. This guided design process produces supporting design documents with clear interfaces and data flows.

Does this architecture design process work without external dependencies?▼

Yes, the architecture design process works without external dependencies. It operates independently to translate PRD requirements into architecture documentation and ADRs, requiring only a PRD path or focus area to generate artifacts.