doc-dd-obs

Name: doc-dd-obs
Availability: InStock
Author: tsuji-tomonori

Generate and update infrastructure detailed design documents in Markdown format.

1|Updated Feb 11, 2026

Search Tags:#design #documentation #technical writing #obsidian #infrastructure #diopside

Ready to run

npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-dd-obs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-dd-obs
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-dd-obs
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-dd-obs

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 helps you create and update infrastructure detailed design documents (DD-OBS) that are consistent with diopside's conventions and traceable to upstream requirements and downstream tests.

Core Features & Use Cases

Structured Document Creation: Generates DD-OBS documents following a strict template and frontmatter requirements.
Traceability Maintenance: Ensures documents link back to requirements and forward to verification steps.
Quality Assurance: Integrates automated checks for filename consistency, link validity, and glossary term conversion.
Use Case: When designing the monitoring and observability aspects of a new microservice, use this Skill to author the DD-OBS- document, ensuring all technical specifications are clearly defined and linked.

Quick Start

Use the doc-dd-obs skill to create a new infrastructure detailed design document for the service monitoring.

Frequently Asked Questions about doc-dd-obs

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

FAQPage Schema

How do I write infrastructure detailed design documents in Markdown?▼

This Skill generates infrastructure detailed design documents in Markdown format, applying strict templates and frontmatter conventions to structure technical specifications for service monitoring and observability.

How do you maintain traceability between requirements and verification documents?▼

Traceability to requirements and verification documents is maintained by automatically validating links within the Markdown files, ensuring upstream requirements and downstream tests connect properly.

Can I use Obsidian to manage infrastructure design documentation?▼

Yes, Obsidian is supported as the documentation environment, utilizing automated scripts to validate vault naming conventions, check link validity, and convert glossary terms within the Markdown files.

What is the best way to automate quality checks for technical writing in Obsidian?▼

The best way to automate quality checks is by running validation scripts that enforce filename consistency, verify link validity, and convert glossary terms according to diopside's documentation conventions.

Does this documentation approach support microservice observability designs?▼

Yes, it supports microservice observability designs by providing a structured document template that clearly defines and links technical monitoring specifications within the detailed design phase.