doc-design

Generate technical design documentation with C4 diagrams and standardized templates.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill doc-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-design
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/doc-design
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill doc-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of starting technical documentation from scratch by providing a structured, template-driven approach to architectural design.

Core Features & Use Cases

  • Standardized Templates: Automatically generates design documents using pre-defined organizational standards.
  • Context-Aware Generation: Integrates existing PRDs, ADRs, and source code analysis to ensure design consistency.
  • Visual Documentation: Supports the creation of C4 diagrams to clearly communicate system architecture and component relationships.

Quick Start

Ask the agent to write a design document for the new authentication service feature.

Frequently Asked Questions about doc-design

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

FAQPage Schema
How do I generate technical design documentation from existing project context?

Generate technical design documentation by synthesizing existing project context, architectural patterns, and source code analysis. The skill integrates existing PRDs and ADRs to ensure design consistency and automatically outputs standardized specifications for cross-team technical alignment.

What is the best way to create C4 diagrams for system architecture planning?

Create C4 diagrams for system architecture planning by using a template-driven generation approach. This supports visual documentation to clearly communicate system architecture, component relationships, and data flow analysis within formal design specifications.

How do I write a design document for a new software engineering feature?

Write a design document for a new feature by asking the agent to process the feature requirements. It produces comprehensive technical design documentation covering component design, data flow analysis, and test planning, satisfying standardized documentation requirements.

Can I use existing ADRs and PRDs to maintain consistency in architectural design?

Existing ADRs and PRDs can be used to maintain architectural design consistency. Context-aware generation integrates these existing documents and source code analysis to ensure the output design specifications align with pre-defined organizational standards.

Does this approach support standardized templates for component design and test planning?

Standardized templates are supported for generating design documents that include component design and test planning. This template-driven approach eliminates starting from scratch and provides structured output for formal design specifications and data flow analysis.

What should technical design documentation include for cross-team technical alignment?

Technical design documentation for cross-team alignment should include component design, data flow analysis, test planning, and C4 diagramming requirements. This ensures standardized output that communicates system architecture and architectural patterns effectively across teams.