design-driven

Define, document, and audit system architecture with drift detection.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/lidessen/skills --skill design-driven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-driven
Source: https://github.com/lidessen/skills/tree/main/skills/design-driven
Command: npx skills add https://github.com/lidessen/skills --skill design-driven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams systematically define, document, and evolve the architectural shape of complex systems, ensuring clarity and consistency across development phases.

Core Features & Use Cases

  • Architectural Documentation: Create and update a formal design/ directory, including DESIGN.md and optional detailed mechanisms files.
  • Design Reconciliation: Run audits to identify drift between code and design, reconciling discrepancies through proposals.
  • Design Proposals: Draft, review, and record tradeoffs and system decisions impacting overall system shape.
  • Use Case: Use this Skill when onboarding a new project, ensuring consistent architecture is established and maintained across team members and iterations.

Quick Start

Invoke /design-driven init to set up design and blueprint folders, then write DESIGN.md manually or generate it from existing code with /design-driven bootstrap.

Frequently Asked Questions about design-driven

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

FAQPage Schema
How do I document system architecture to prevent documentation drift?

To prevent documentation drift, use design-driven to create a formal design directory and run reconciliation audits. It detects discrepancies between your evolving codebase and documented architecture, enabling updates through formal proposals.

What is the best way to maintain design decisions during system refactoring?

The best way to maintain design decisions during system refactoring is recording tradeoffs and proposals. This Skill traces architectural decisions, ensuring evolving codebases stay aligned with the documented system shape and facilitating onboarding safety.

How do I set up architectural documentation for a new software project?

Set up architectural documentation by initializing design and blueprint folders. You can then write the DESIGN.md file manually or generate it directly from existing code to ensure consistent architecture across team members.

Can I generate architecture documentation from an existing codebase?

Yes, you can generate architecture documentation from an existing codebase. The Skill provides a bootstrap command that analyzes your current code structure to create the initial DESIGN.md file and establish formal architectural baselines.

When do I need formal design proposals for system architecture?

You need formal design proposals when making changes impacting the overall system shape. This Skill helps draft, review, and record tradeoffs for architectural decisions, ensuring changes are traced and reconciled against the existing design.