doc-dd-scale

Generates and revises DD-SCALE documents for the diopside project.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-dd-scale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-dd-scale
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-dd-scale
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-dd-scale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires auto_link_glossary.py, validate_vault.py, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation and revision of DD-SCALE (Scalability Detailed Design) documents, ensuring they adhere to diopside's standards for documenting load assumptions, scaling strategies, and degradation conditions.

Core Features & Use Cases

  • Standardized Documentation: Ensures new or updated DD-SCALE documents follow the Obsidian operational guidelines.
  • Scalability Design: Helps define thresholds, triggers, and control procedures for peak access, re-execution concentration, and intake bursts.
  • Dependency Management: Documents constraints with external dependencies (API limits, DB connections, queue backlogs) and defines recovery paths.
  • Use Case: When designing a new feature that anticipates high user traffic, use this Skill to draft the DD-SCALE document, outlining how the system will scale horizontally or vertically, what triggers these scaling events, and how it will recover from potential bottlenecks.

Quick Start

Use the doc-dd-scale skill to create a new DD-SCALE document for handling peak load scenarios.

Frequently Asked Questions about doc-dd-scale

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

FAQPage Schema
How do I document scalability strategies and load assumptions for technical design?

To document scalability strategies and load assumptions, you define thresholds, triggers, and control procedures for peak access. This process outlines horizontal or vertical scaling events and establishes recovery paths for potential system bottlenecks.

What is a DD-SCALE document and when do I need to create one?

A DD-SCALE document is a Scalability Detailed Design record needed when designing features anticipating high user traffic. It captures load assumptions, scaling strategies, and degradation conditions to handle peak access, re-execution concentration, and intake bursts.

How do I structure Obsidian technical writing to include required frontmatter and glossary links?

Obsidian technical writing requires frontmatter including id, title, doc_type, phase, version, status, owner, created, updated, up, related, and tags. Document integrity is validated and glossary terms are linked automatically to ensure compliance.

How do I document external dependency constraints and recovery paths for system scalability?

Documenting external dependency constraints involves defining limitations with API limits, database connections, and queue backlogs. You establish recovery paths and degradation conditions to manage these constraints during scaling events and intake bursts.

Does the diopside project require specific Obsidian operational guidelines for design documentation?

The diopside project requires Obsidian operational guidelines for design documentation to ensure standardization. New or updated DD-SCALE documents must follow these guidelines to define scaling triggers, load assumptions, and degradation conditions.