living-design-documents

Create and maintain structured design documentation with Core Decisions, Taxonomy, and Parked sections.

9|1|Updated Jul 9, 2025
One-click install
npx skills add https://github.com/KemingHe/common-devx --skill living-design-documents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: living-design-documents
Source: https://github.com/KemingHe/common-devx/tree/main/.agents/skills/living-design-documents
Command: npx skills add https://github.com/KemingHe/common-devx --skill living-design-documents

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Create and maintain structured design documentation that guides development.

Core Features & Use Cases

  • Bootstrap and maintain core design documents (Core Decisions, Taxonomy, Parked) for new and existing projects
  • Support design audits and ongoing architecture alignment with templates found in assets
  • Facilitate cross-team collaboration through standardised notes, references, and Open Questions

Quick Start

Tell your AI agent to create or update living design documents for this project.

Frequently Asked Questions about living-design-documents

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

FAQPage Schema
How do I create structured design documentation for a new software project?

To create structured design documentation, bootstrap core documents by resolving templates from assets, establishing Core Decisions, Taxonomy, and Parked perspectives to guide development and align team architecture.

What is the best way to maintain and audit living design docs for ongoing projects?

Maintaining and auditing living design docs involves enforcing last updated metadata, tracking open questions, and verifying proper cross-reference navigation to ensure ongoing architecture alignment and accurate design audits.

How does cross-reference navigation work in design documentation?

Cross-reference navigation in design documentation works by enforcing proper links between Core Decisions, Taxonomy, and Parked perspectives, ensuring standardized notes and references facilitate cross-team collaboration without broken paths.

Can I use template resolution from assets to bootstrap design decisions?

Yes, you can use template resolution from assets to bootstrap design decisions. The system applies these templates to structure new projects and ongoing architecture alignment, enforcing consistent document formats.

Why does my design documentation need parked perspectives and open questions?

Design documentation needs parked perspectives and open questions to record alternative viewpoints and unresolved issues, facilitating cross-team collaboration and ensuring all design decisions are transparently tracked for future audits.

What are the limitations of managing living design documents without standardized templates?

Without standardized templates from assets, managing living design documents lacks enforced last updated metadata and proper cross-reference navigation, severely hindering design audits and cross-team collaboration for ongoing projects.