doc-rq-ux

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

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 User Experience (UX) requirements documents for the diopside project, ensuring adherence to Obsidian's operational standards and validating UX acceptance criteria against related documentation.

Core Features & Use Cases

  • Document Generation: Create new UX requirement documents (RQ-UX) following a strict template and frontmatter specification.
  • Content Refinement: Update existing RQ-UX documents, focusing on actionable acceptance criteria and exception handling.
  • Integrity Checks: Automatically verify document IDs, links, and glossary term conversions, ensuring consistency across the project's documentation suite.
  • Use Case: When a new feature requires specific user interaction guidelines, use this Skill to draft the RQ-UX document, define clear acceptance criteria, and ensure it links correctly to related design and test documents.

Quick Start

Use the doc-rq-ux skill to create a new user experience requirement document for the login screen.

Frequently Asked Questions about doc-rq-ux

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

FAQPage Schema
How do I generate UX requirements for Obsidian projects?

To generate UX requirements for Obsidian projects, use this Skill to create User Experience requirement documents (RQ-UX) that adhere to strict frontmatter specifications and operational guidelines. It automatically defines clear acceptance criteria and integrates with related design and test documents for a seamless workflow.

How do you validate document integrity and links in Obsidian vaults?

You validate document integrity in Obsidian vaults by running automated checks that verify document IDs, ensure links connect correctly to related RDR, BD-UI, and AT documentation, and confirm glossary term conversions. This ensures consistency across the entire project's documentation suite.

What is the process for defining acceptance criteria in UX requirement documents?

Defining acceptance criteria in UX requirement documents involves updating existing RQ-UX files to focus on actionable testing parameters and explicit exception handling. This approach ensures that user interaction guidelines are testable and align with the broader project's validation checks.

Can I use this approach to update existing UX documents instead of starting from scratch?

Yes, you can use this approach to update existing UX documents rather than starting from scratch. The Skill refines current RQ-UX files by enforcing frontmatter compliance, clarifying acceptance criteria, and validating document links without needing to recreate the entire file.

Does this method require specific dependencies for glossary conversion and vault validation?

Yes, this method requires specific dependencies to operate, utilizing scripts like auto_link_glossary.py for glossary term conversions and validate_vault.py for verifying document IDs and internal links to maintain strict documentation integrity.