Generate and revise RQ-PC project constraint documents following Obsidian guidelines.
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-rq-pc
Please help me install this Agent Skill. Skill: doc-rq-pc Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-rq-pc Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-rq-pc
This Skill ensures that project constraints (RQ-PC) are clearly defined, documented according to Obsidian standards, and aligned with other project documentation.
RQ-PC-*) and related documents like requirements (RQ-SC-*), risks (RQ-RDR-*), and non-functional requirements (RQ-PRC-*, RQ-COST-*, RQ-DEV-*).RQ-PC-DATA-PRIVACY, ensuring it aligns with security policies and operational procedures.Use the doc-rq-pc skill to update the document RQ-PC-001, ensuring its constraints and operational prerequisites are clearly defined.
High-intent search queries and answers about installing and using this skill.
To document project constraints in Obsidian, generate and revise constraint documents using standardized frontmatter conventions. This ensures clarity on constraint applicability, operational prerequisites, and exception handling while maintaining compliance.
Aligning project constraint documents with related files requires validating consistency across requirements, risks, and non-functional documents. Auto-linking glossary terms and running vault validation ensures structural integrity and cross-document alignment.
Defining operational prerequisites and exception handling involves articulating project constraints related to regulations, operational capacity, costs, and release criteria. Clear documentation ensures all operational boundaries are explicitly stated and compliant.
Yes, you can validate consistency between constraint documents and non-functional requirements within an Obsidian vault. Quality checks verify and update links between constraint files and related requirements, risks, and cost documents.
You need to generate a dedicated project constraint document when introducing new compliance requirements, such as user data handling. This ensures the new constraint aligns with existing security policies and operational procedures.
tsuji-tomonoriGenerate and revise IT-ENV documents compliant with diopside Obsidian standards.
tsuji-tomonoriGenerate and update RQ-AV availability requirement documents for the diopside project.
tsuji-tomonoriCreate and revise data quality requirements for public archive data with Obsidian conventions.
BrandondaymdrEnforce predefined templates and structural guidelines for Obsidian vault notes.