doc-rq-dm

Requirement documents in Obsidian comply with data model standards by using this Skill to generate RQ-DM files with mandatory frontmatter fields like id, title, phase, and owner properly populated. It enforces correct document structure and proper internal linking according to diopside operational standards.

Obsidian frontmatter fields are correctly populated for requirements by validating them against diopside conventions using the included Python scripts. The validate_vault.py script checks for mandatory fields and structural compliance, while auto_link_glossary.py automates internal glossary linking.

Glossary term linking in Obsidian documentation is automated by running the auto_link_glossary.py script, which scans requirement documents and formats internal links to glossary terms according to diopside standards. This ensures consistent cross-referencing across the vault.

Python scripts are required to validate Obsidian vault structure for compliance because the Skill relies on validate_vault.py to check document structure and frontmatter conventions. These scripts automate the validation process to ensure all RQ-DM documents meet operational standards.

An automated document generator for requirements data models should be used when you need to create new RQ-DM documents or update existing ones to meet diopside frontmatter and internal linking conventions. It ensures standardized compliance across all requirement entries in your Obsidian vault.

Requirement documents fail vault validation in Obsidian when they are missing mandatory frontmatter fields such as id, title, phase, or owner, or when internal links to glossary terms are improperly formatted. Running validate_vault.py identifies these specific compliance errors.