common-design-docs-k

Document system design docs with frontmatter conventions and required sections.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill common-design-docs-k
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: common-design-docs-k
Source: https://github.com/JSai23/claude-tooling/tree/main/plugins/wf/skills/common-design-docs-k
Command: npx skills add https://github.com/JSai23/claude-tooling --skill common-design-docs-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design documentation for agent systems is often neglected or scattered, making it hard for new agents to understand decisions, architecture, and rationale.

Core Features & Use Cases

  • Living documentation: up-to-date system architecture, decisions, and principles.
  • Structured frontmatter conventions: standardized metadata for traceability.
  • Shared design language: consistent doc types, folder structure, and responsibilities across teams.
  • Use Case: New agent team onboarding — quickly surface the architecture and decisions behind living docs.

Quick Start

Create a living design-doc for a new service by outlining plans, architecture, and decisions in design-docs.

Frequently Asked Questions about common-design-docs-k

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

FAQPage Schema
What is a living design doc for agent workflows?▼

A living design doc for agent workflows is a consistently updated record of system architecture and decisions. It applies structured frontmatter conventions and required sections to ensure traceability and accessibility across teams.

How do I structure design documentation for system architecture and plans?▼

To structure design documentation, you outline plans, architecture, and decisions within design-docs. You must apply specified frontmatter conventions, required sections, and minimal structure to ensure consistent discovery and versioning.

Does my agent team need frontmatter conventions for living docs?▼

Yes, frontmatter conventions for living docs are required. They provide standardized metadata for traceability, ensuring new agents can quickly surface the architecture and decisions behind system-level and package-level documentation.

What's the best way to document design decisions across multiple agent packages?▼

The best way to document design decisions across packages is applying a shared design language. This specifies folder structure, doc types, and responsibilities, ensuring consistent discovery and versioning across teams.

When do I need to create living docs for agent systems?▼

You need to create living docs for agent systems when onboarding new team members or agents. It surfaces up-to-date architecture, principles, and rationale, solving the problem of scattered or neglected design documentation.