skills.rest
patrickrmoore
patrickrmooreCOMMUNITY
Explore all skills by this author →
GitHub

system-design

Draft and maintain a project-level Software Architecture Document in specs/sad.md.

Updated Mar 22, 2026
Search Tags:#architecture#documentation#mermaid#adr#software-architecture#system-design#project-context
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill system-design-patrickrmoore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.github/skills/system-design
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill system-design-patrickrmoore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Draft and maintain a project-level Software Architecture Document (SAD) to codify the technical context.

Core Features & Use Cases

  • Define a canonical technical context document (specs/sad.md) for the project.
  • Capture architecture style, system boundaries, ADRs, and cross-cutting concerns to support governance.
  • Provide a repeatable workflow to bootstrap and maintain architecture decisions across repo lifecycles.

Quick Start

Create or update specs/sad.md to reflect the current system architecture and decisions.

Frequently Asked Questions about system-design

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

FAQPage Schema
How do I document software architecture for a project to capture technical context?▼

You can capture architecture decisions by drafting ADRs within a project-level Software Architecture Document (SAD), preserving all updates in the Project Context Baseline Updates section of the canonical specs/sad.md file.

How do I generate architecture diagrams for a software architecture document?▼

You can generate architecture diagrams for a software architecture document using Mermaid diagram syntax to visualize architecture styles, system boundaries, and runtime flows within the canonical specs/sad.md file.

What is the best way to maintain and update a software architecture document across a repo lifecycle?▼

Maintain a software architecture document by applying a repeatable workflow to bootstrap and update architecture decisions across repo lifecycles, ensuring governance through the canonical specs/sad.md file.

Does this software architecture documentation approach require any specific dependencies or frameworks?▼

No external dependencies are required; this software architecture documentation approach relies solely on a canonical specs/sad.md file and Mermaid diagrams to define architecture style, system boundaries, and ADRs.

What should be included in a software architecture document to support project governance?▼

To support project governance, a software architecture document should include architecture style, system boundaries, runtime flows, ADRs, and cross-cutting concerns to properly codify the project's technical context.

Related Skills

Explore More Software Engineering Skills→
telum-aitelum-ai
2

project-import

Create a Speck project structure with a skeleton project.md file.

Official
Basic
zzafergokzzafergok
1

c4-architecture

Generate C4 model diagrams and documentation in Mermaid syntax from codebase analysis.

Community
Intermediate
OKHP3OKHP3
2

architecture-decision-records

Automate creation and lifecycle management of Architecture Decision Records in Markdown.

Community
Intermediate
B4sanB4san

documentation

Generate project documentation including READMEs, API docs, and Mermaid/PlantUML architecture diagrams.

Community
Intermediate