skills.rest
s3nex-com
s3nex-comCOMMUNITY
Explore all skills by this author →
GitHub

design-doc-generator

Generate a comprehensive DESIGN.md from PRD and upstream artifacts.

Updated Apr 8, 2026
Search Tags:#design#architecture#documentation#requirements#adr#system-design#design-doc
One-click install
npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill design-doc-generator-s3nex-com
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-doc-generator
Source: https://github.com/s3nex-com/sdlc-skills-library/tree/main/skills/phase1/design-doc-generator
Command: npx skills add https://github.com/s3nex-com/sdlc-skills-library --skill design-doc-generator-s3nex-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A technical design document is the central artifact that translates what to build (PRD and requirements) into how to build it (components, data flows, API contracts, and an implementation plan). This skill consolidates inputs from PRD, requirements-tracer, specification-driven-development, and architecture-decision-records into a single, implementation-ready DESIGN.md that engineers can reference and act on.

Core Features & Use Cases

  • Synthesizes outputs from upstream skills into one coherent design document with a consistent structure.
  • Produces Section 1–5 (Context, Components, Data flows, Data & security, Implementation phases) plus an appendable execution log, ready for handoff to code-implementer.
  • Supports governance checks (design review gate) and traceability back to PRD and ADRs for audits.

Quick Start

Generate DESIGN.md from PRD, requirements, ADRs, and API specs to begin the design handoff.

Frequently Asked Questions about design-doc-generator

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

FAQPage Schema
How do I generate a technical design document from PRD and requirements?▼

Generate a design document by consolidating PRD, requirements, ADRs, and API specs into a single DESIGN.md file containing context, components, data flows, security, and implementation phases.

What sections are included in a system design document for architecture handoff?▼

A complete design document includes Section 1–5 covering Context, Components, Data flows, Data & security, and Implementation phases, plus an appendable execution log for engineering handoff.

Can I use upstream artifacts like architecture decision records to build a design doc?▼

Yes, you can use upstream artifacts like architecture decision records, PRD, and requirements to build a design doc, ensuring traceability back to original requirements for audits and governance.

Does design doc generation support governance checks and traceability for audits?▼

Design doc generation supports governance checks through a design review gate and enforces traceability back to PRD and architecture decision records to satisfy audit requirements across the SDLC.

What is the best way to structure implementation phases in a DESIGN.md file?▼

The best way to structure implementation phases in a DESIGN.md file is to synthesize upstream requirements into distinct execution phases, ready for direct handoff to a code-implementer.

Related Skills

Explore More Software Engineering Skills→
yknothingyknothing
1

system-design

Plan high-level architecture and component boundaries from reviewed requirements.

Community
Advanced
Arman-KudaibergenovArman-Kudaibergenov
151

subagent-dev

Execute tasks.md tasks via implementer and reviewer subagents.

Community
Advanced
stevolandstevoland

adr

Create and manage MADR-compliant Architecture Decision Records across projects.

Community
Basic
coolguy1771coolguy1771

architecture-diagrams

Generate system architecture diagrams using Mermaid and PlantUML code.

Community
Intermediate