docops-orchestrator

Name: docops-orchestrator
Availability: InStock
Author: tsuji-tomonori

Orchestrate end-to-end diopside documentation updates with impact analysis and integrity checks.

1|Updated Feb 11, 2026

Search Tags:#documentation #workflow automation #validation #orchestration #impact analysis #diopside

Ready to run

npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill docops-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures that changes to diopside documentation are managed holistically, from initial impact analysis and related document updates to final integrity checks, preventing inconsistencies and ensuring a smooth documentation workflow.

Core Features & Use Cases

End-to-End Document Management: Orchestrates the entire process of updating documentation, including impact assessment, cross-referencing, and validation.
Consistency Enforcement: Ensures that changes across different document types (Requirements, Design, etc.) and skill definitions are synchronized and validated.
Use Case: When updating a functional requirement (FR) in the docs/ directory, this Skill will automatically identify related design documents (ADRs), update impact reports, link new terms, and verify the overall integrity of the documentation vault.

Quick Start

Initiate a comprehensive update for the document with ID 'RQ-FR-004', ensuring all related documents are updated and checks are performed.

Frequently Asked Questions about docops-orchestrator

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

FAQPage Schema

How do I ensure documentation consistency when updating requirements and design documents?▼

Documentation consistency is maintained by orchestrating end-to-end updates that link new terms and validate document IDs across the vault. This ensures requirements, design documents, and skill definitions remain synchronized during changes.

What is the best way to automate glossary linking and vault validation for markdown documentation?▼

Automated glossary linking and vault validation are performed using Python scripts to validate document IDs and verify terminology. This ensures structural integrity across `docs/**` and `.opencode/skills/**` directories.

Do I need Python to perform impact analysis on diopside documentation updates?▼

Yes, Python3 is required to execute the scripts that automate glossary linking and vault validation. These scripts perform the integrity checks and impact analysis needed for diopside documentation updates.

How do I update a functional requirement and automatically identify related design documents?▼

Updating a functional requirement automatically identifies related design documents by orchestrating an end-to-end update process. This manages changes across `docs/**` directories to keep cross-references synchronized.

Can I validate document IDs and links across multiple documentation directories simultaneously?▼

Yes, document IDs and links can be validated simultaneously across `docs/**` and `.opencode/skills/**` directories. The orchestration process verifies integrity for all requirements, design documents, and skill definitions.