Generate and update Requirement Definition Records for the diopside project.
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-rq-rdr
Please help me install this Agent Skill. Skill: doc-rq-rdr Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-rq-rdr Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-rq-rdr
This Skill streamlines the creation and updating of Requirement Definition Records (RDRs) for the diopside project, ensuring compliance with Obsidian operational standards and clear documentation of decision-making.
Use the doc-rq-rdr skill to create a new RDR document for the requirement ID RQ-123.
High-intent search queries and answers about installing and using this skill.
Requirement definition records are generated using a strict template to ensure compliance with Obsidian operational standards. The skill captures the background, rationale, and impact of requirement changes while maintaining traceability between requirements and their corresponding records.
Documenting requirement changes is best handled by capturing the decision rationale and impact in a standardized record. This approach maintains a clear audit trail by validating document integrity and ensuring traceability between the original requirement and the recorded decision.
Document integrity and traceability are validated using automated Python scripts. These scripts check filename consistency, verify valid links, and ensure that requirements are properly connected to their corresponding definition records within the vault.
Python scripts are used to automate linking and validate vault integrity for Obsidian documents. The skill utilizes these scripts to enforce frontmatter requirements, ensure valid links, and maintain overall document consistency across the project.
A new requirement definition record is needed whenever a new feature request is added or an existing one is modified. This ensures the justification, impact, and related decisions are documented immediately to maintain a clear audit trail.
The documentation approach enforces strict frontmatter requirements and filename consistency rules. Automated validation scripts verify that all generated records adhere to the required template structure before they are integrated into the vault.
jonnytacos8Automate Obsidian vault operations with obsidian-cli commands.
roderikGenerate Markdown audit reports from security-focused differential code review.
tsuji-tomonoriGenerate and update RQ-DM documentation with Obsidian frontmatter and internal links.
Agile-VAutomate decision logging and requirement traceability for audit-ready compliance.
