doc-rq-av

Generate and update RQ-AV availability requirement 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-rq-av
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-rq-av
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-rq-av
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-rq-av

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 updating of Availability Requirement (RQ-AV) documents for the diopside project, ensuring adherence to Obsidian operational standards and validating acceptance criteria.

Core Features & Use Cases

  • Document Generation: Creates new RQ-AV documents following a strict template and frontmatter convention.
  • Document Updating: Modifies existing RQ-AV documents, ensuring version control and updated metadata.
  • Quality Assurance: Validates document compliance, checks links, and ensures acceptance thresholds are met.
  • Use Case: When a new availability requirement needs to be documented or an existing one updated, this Skill guides the user through the process, ensuring all necessary fields are present and correct, and that the document integrates seamlessly with the project's knowledge base.

Quick Start

Use the doc-rq-av skill to create a new availability requirement document for the diopside project.

Frequently Asked Questions about doc-rq-av

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

FAQPage Schema
How do I create availability requirement documents in Obsidian?

To create availability requirement documents in Obsidian, use this Skill to generate RQ-AV files for the diopside project. It enforces strict frontmatter conventions, content guidelines, and link validation to ensure operational standard compliance.

What is the best way to validate Obsidian vault consistency for requirement docs?

The best way to validate Obsidian vault consistency for requirement docs is running validation scripts. This Skill executes checks for link integrity and glossary term conversion, ensuring acceptance thresholds are met and related documentation remains consistent.

How do I update existing availability requirements and maintain version control?

To update existing availability requirements and maintain version control, this Skill modifies RQ-AV documents while enforcing updated metadata. It ensures changes integrate seamlessly with the diopside project's knowledge base and pass quality assurance checks.

Do I need specific scripts to enforce glossary terms in Obsidian docs?

Yes, you need specific scripts to enforce glossary terms in Obsidian docs. This Skill relies on auto_link_glossary.py and validate_vault.py dependencies to automatically convert glossary terms and validate frontmatter requirements for RQ-AV documents.

What are the limitations when validating acceptance thresholds for availability requirements?

Limitations when validating acceptance thresholds for availability requirements include strict dependency on Obsidian operational standards and specific diopside project templates. Documents failing frontmatter checks or link validation will not pass quality assurance until manually corrected.