doc-rq-uc

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

Create and update RQ-UC documents with Obsidian frontmatter and traceability links.

1|Updated Feb 11, 2026

Search Tags:#documentation #requirements #validation #obsidian #use case #diopside

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that Use Case Requirements (RQ-UC) documents for diopside are created and updated according to established Obsidian operational standards, maintaining consistency and traceability.

Core Features & Use Cases

Standardized Document Creation: Guides users in creating new RQ-UC documents that adhere to specific frontmatter and content requirements.
Consistent Updates: Facilitates the revision of existing RQ-UC documents, ensuring changes are properly documented and linked.
Traceability Maintenance: Verifies and maintains traceability links (up/related) between related documents.
Use Case: When adding a new user interaction scenario to the diopside system, use this Skill to draft the RQ-UC document, ensuring all required fields are present and the flow is clearly described.

Quick Start

Use the doc-rq-uc skill to create a new Use Case Requirement document for the user login process.

Frequently Asked Questions about doc-rq-uc

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

FAQPage Schema

How do I create use case requirement documents in Obsidian that meet operational standards?▼

To create use case requirement documents in Obsidian, you must follow specific frontmatter and content requirements, detailing use-case-specific behaviors, acceptance criteria, and alternative/exception flows. This ensures standardization and traceability across the project vault.

What is the best way to maintain traceability links for requirements documentation in a vault?▼

Maintaining traceability links for requirements documentation involves verifying and updating the up and related links between documents. This ensures that changes to use case behaviors are properly connected to their parent requirements and glossary terms.

Does this approach to use case validation support frontmatter integrity checks?▼

Yes, use case validation supports frontmatter integrity by integrating with vault validation scripts. It ensures that required metadata fields are present and correctly formatted when adding or revising documents.

How do I document alternative and exception flows for user interaction scenarios?▼

Documenting alternative and exception flows for user interaction scenarios requires detailing the specific branching behaviors and acceptance criteria within the use case document. This captures deviations from the main flow to ensure comprehensive system validation.

Can I use vault validation scripts to verify glossary linking in use case requirements?▼

Yes, you can use vault validation scripts to verify glossary linking in use case requirements. The integration ensures that domain terms within the documents are properly connected to the project's established glossary.