sddp-systemdesign

Create and maintain canonical project-level technical context in specs/sad.md.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill sddp-systemdesign
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sddp-systemdesign
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.claude/skills/sddp-systemdesign
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill sddp-systemdesign

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and maintains a canonical project-level technical context to align architecture decisions, reduce drift, and provide a single source of truth for large software initiatives.

Core Features & Use Cases

  • Canonical specs generation: Produce a reusable, referenceable set of system architecture specifications.
  • Architecture baselines: Define default patterns, constraints, and interfaces to guide downstream design.
  • Governance and onboarding: Accelerate project initiation with a centralized context that enforces consistency across teams.
  • Use Case: When starting a new program, generate the canonical specs and baselines to align stakeholders and reduce rework.

Quick Start

Create or refine the canonical project-level technical context in specs/sad.md.

Frequently Asked Questions about sddp-systemdesign

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

FAQPage Schema
How do I create a canonical project-level technical context for architecture alignment?

To create a canonical project-level technical context, generate actionable system architecture specifications at specs/sad.md. This establishes a single source of truth to align architecture decisions and reduce drift across teams.

What is the best way to define reusable architecture baselines for large software initiatives?

Defining reusable architecture baselines involves producing referenceable system design specifications that set default patterns, constraints, and interfaces. This guides downstream design and enforces consistency across project phases and team roles.

How does centralized architecture governance reduce rework when starting a new program?

Centralized architecture governance reduces rework by accelerating project initiation with a shared context that enforces consistency. Stakeholders align on canonical specs and baselines, preventing architectural drift and miscommunication across teams.

Can I use system design specifications for project onboarding across different team roles?

Yes, system design specifications apply across project phases and team roles. The canonical technical context provides governance and reference specs that accelerate onboarding and ensure consistent architecture baselines for everyone.

Do I need any specific dependencies to generate a system architecture document?

No specific dependencies are required to generate the system architecture document. The process produces actionable specs at specs/sad.md with built-in validations and safe defaults, working independently within your project environment.

When do I need to maintain a single source of truth for system architecture?

You need to maintain a single source of truth for system architecture during large software initiatives where architecture drift is likely. Regularly refine the canonical context in specs/sad.md to keep stakeholders aligned and reduce rework.