doc-rq-data

Name: doc-rq-data
Availability: InStock
Author: tsuji-tomonori

Create and revise data quality requirements for public archive data with Obsidian conventions.

1|Updated Feb 11, 2026

Search Tags:#documentation #requirements #data quality #obsidian #traceability #diopside

Ready to run

npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-rq-data

💬 Prompt for ChatGPT / Claude Chat▼

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

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 helps you create and revise data quality requirements (RQ-DATA) for public archive data, ensuring traceability to SnowCard and related designs according to diopside conventions.

Core Features & Use Cases

Document Compliance: Updates documents to align with Obsidian operational rules.
Requirement Definition: Defines non-functional requirements for data completeness, uniqueness, and accuracy.
Traceability Maintenance: Ensures dependencies with related documents (RQ-RDR, BD-DATA, BD-ERD) are clear.
Use Case: When defining new quality thresholds for missing data or reflection time in the public archive, use this skill to ensure the requirements are measurable and correctly linked to design documents.

Quick Start

Use the doc-rq-data skill to create a new data quality requirement document.

Frequently Asked Questions about doc-rq-data

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

FAQPage Schema

How do I define data quality requirements for public archive data?▼

To define data quality requirements for public archive data, you create an RQ-DATA document specifying non-functional thresholds for completeness, uniqueness, and accuracy. This ensures measurable quality criteria are established for your archive.

How do I maintain traceability between data quality requirements and SnowCard designs in Obsidian?▼

Maintain traceability between data quality requirements and SnowCard by linking the RQ-DATA document to related designs. This verifies dependencies with RQ-RDR, BD-DATA, and BD-ERD documents according to diopside conventions.

What are non-functional requirements for data completeness and accuracy?▼

Non-functional requirements for data completeness and accuracy define specific quality thresholds, such as acceptable missing data rates or reflection times. They ensure public archive data meets measurable operational standards.

Does the doc-rq-data skill check dependencies with BD-DATA and BD-ERD documents?▼

Yes, the doc-rq-data skill verifies dependencies with BD-DATA and BD-ERD documents. It ensures your data quality requirements maintain clear traceability and structural links to related design documents.

Can I update existing data quality requirements to comply with Obsidian operational rules?▼

Yes, you can revise existing data quality requirements to align with Obsidian operational rules. The skill facilitates document compliance by updating RQ-DATA files to meet diopside conventions.

When should I set quality thresholds for missing data in a public archive?▼

You should set quality thresholds for missing data when defining new requirements for the public archive. Use this process to ensure the specified quality thresholds are measurable and correctly linked to design documents.