doc-dd-dr

Generate and update DD-DR infrastructure design documents for disaster recovery.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation and updating of infrastructure detailed design (DD-DR) documents, ensuring they align with diopside's standards and maintain traceability with requirement and verification documents.

Core Features & Use Cases

  • Document Generation: Creates or revises DD-DR-*.md files for infrastructure detailed design.
  • Compliance: Organizes detailed specifications, constraints, and failure behaviors according to diopside conventions.
  • Traceability: Links detailed designs to upstream requirements and downstream tests via frontmatter.
  • Use Case: When updating the disaster recovery procedures for a new service, use this Skill to generate the DD-DR-XYZ.md document, detailing failover steps, RTO/RPO, and validation checks.

Quick Start

Use the doc-dd-dr skill to create a new infrastructure detailed design document for disaster recovery.

Frequently Asked Questions about doc-dd-dr

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

FAQPage Schema
How do I generate infrastructure detailed design documents for disaster recovery?▼

To generate disaster recovery infrastructure detailed design documents, use this Skill to create or revise DD-DR markdown files, ensuring they align with diopside conventions for specifications, constraints, and failure behaviors.

What should disaster recovery detailed design documentation include for failover procedures?▼

Disaster recovery detailed design documentation should include failover steps, RTO/RPO targets, validation checks, detailed specifications, constraints, failure behaviors, and recovery procedures organized according to project standards.

How do I maintain traceability between infrastructure detailed design and upstream requirements?▼

Maintain traceability by using frontmatter in your DD-DR documents to link detailed designs to upstream requirements and downstream tests, ensuring full compliance with document ID and content standards.

Can I use this to update existing disaster recovery design documents for new services?▼

Yes, you can update existing disaster recovery design documents for new services by revising DD-DR markdown files to detail new failover steps, RTO/RPO metrics, and validation checks while maintaining standards compliance.

What are the limitations of automating disaster recovery documentation generation?▼

The automation is limited to generating and organizing DD-DR files within the diopside project framework, relying on provided specifications and constraints rather than autonomously designing the underlying disaster recovery architecture.