doc-rq-dg

Create and revise RQ-DG documents with Obsidian frontmatter and change history.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that documents related to the "Document Update Flow and Acceptance Criteria" (RQ-DG) are created and updated according to the diopside conventions, maintaining consistency and adherence to operational rules.

Core Features & Use Cases

  • Standardized Document Creation/Revision: Generates or modifies RQ-DG-* documents following specific Obsidian operational guidelines.
  • Metadata Management: Enforces the correct structure and content for frontmatter, including essential keys like id, title, doc_type, phase, version, status, owner, created, updated, up, related, and tags.
  • Change Tracking: Ensures proper updates to the ## 変更履歴 (Change History) section and adherence to versioning policies.
  • Use Case: When a new process for updating documentation is defined, this Skill helps create the corresponding RQ-DG document, ensuring all required fields are populated and the change history is correctly formatted.

Quick Start

Use the doc-rq-dg skill to create a new document for RQ-DG-005, detailing the updated document review process.

Frequently Asked Questions about doc-rq-dg

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

FAQPage Schema
How do I standardize Obsidian frontmatter fields for process documentation?

To standardize Obsidian frontmatter, this skill enforces mandatory metadata keys like id, title, doc_type, phase, version, status, and tags, ensuring document consistency and adherence to operational conventions.

How do I create an RQ-DG document with proper change history tracking?

Creating an RQ-DG document with change history tracking is handled by generating the file with a properly formatted change history section, enforcing versioning policies and synchronized updates across docs and skills directories.

What is the best way to manage version control for single-topic documentation in Obsidian?

Managing version control for single-topic documentation involves enforcing single-topic principles and updating version fields within frontmatter, keeping process management standardized across synchronized directory structures.

Can I use this skill to synchronize document updates across multiple project directories?

Yes, you can synchronize document updates across multiple directories, as the skill facilitates synchronized updates between docs and .opencode/skills directories, ensuring consistency with skill maintenance policies.

Does this documentation standardization tool require any external dependencies?

This documentation standardization tool does not require external dependencies, operating independently to enforce Obsidian operational conventions and impact assessments for process management documents.

When should I not use automated document standardization for RQ-DG files?

You should not use automated document standardization for RQ-DG files when your project does not follow diopside conventions or lacks the required Obsidian operational guidelines for frontmatter and single-topic principles.