doc-dd-arch

Generate and update DD-ARCH-*.md architecture documents with diopside conventions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires obsidian-doc-new, obsidian-doc-check, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining clear, traceable, and diopside-compliant documentation for detailed architectural decisions, ensuring consistency between design and implementation.

Core Features & Use Cases

  • Architectural Documentation: Create and update detailed architecture documents (DD-ARCH-*.md) following specific conventions.
  • Boundary Definition: Clearly define framework boundaries, dependency directions, and responsibility separation.
  • Use Case: When designing a new microservice, use this Skill to document its core architectural principles, including its interaction with other services and its internal component responsibilities, ensuring it aligns with the overall system design.

Quick Start

Use the doc-dd-arch skill to create a new detailed architecture document for the user authentication module.

Frequently Asked Questions about doc-dd-arch

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

FAQPage Schema
How do I document detailed architecture principles for a new microservice?

To document detailed architecture principles, generate a DD-ARCH markdown file defining framework boundaries, dependency directions, and responsibility separation at a pre-implementation level to align component design with system structure.

What is the best way to maintain traceability between architectural design and requirements?

Maintain traceability between architectural design and requirements by ensuring your DD-ARCH document explicitly links to related requirements and tests while preserving frontmatter versioning and update timestamps for compliance.

Does this architectural documentation approach support diopside conventions?

Yes, this architectural documentation approach supports diopside conventions by generating and updating DD-ARCH files that adhere to specific structural rules for component design, boundary definition, and frontmatter integrity.

How do I define architectural boundaries and dependency directions before implementation?

Define architectural boundaries and dependency directions before implementation by creating a detailed architecture document that separates component responsibilities and establishes clear framework interaction rules for your module.

Why does my architecture documentation lose traceability during updates?

Your architecture documentation loses traceability during updates if frontmatter integrity is not maintained. Ensure versioning and update timestamps are preserved alongside explicit links to related requirements and tests.