doc-at-rpt

Generate and update AT-RPT documents compliant with diopside's Obsidian standards.

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

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 automates the creation and updating of Acceptance Test Report (AT-RPT) documents, ensuring they comply with diopside's Obsidian operational standards.

Core Features & Use Cases

  • AT-RPT Generation: Create or update AT-RPT documents for specific test scenarios.
  • Result Aggregation: Consolidate scenario execution results and Go/No-Go judgments.
  • API Cross-Referencing: Track and report on API-level test outcomes against design specifications.
  • Use Case: After running a suite of acceptance tests, use this Skill to compile the results, identify any API-level failures, and generate a compliant AT-RPT document for review.

Quick Start

Use the doc-at-rpt skill to update the AT-RPT document for scenario AT-SCN-001.

Frequently Asked Questions about doc-at-rpt

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

FAQPage Schema
How do I generate an Acceptance Test Report in Obsidian?

To generate an Acceptance Test Report in Obsidian, use this Skill to consolidate scenario execution results and API-level judgments into a compliant document with required frontmatter and change history logging.

What is API reverse-mapping in acceptance test documentation?

API reverse-mapping in acceptance test documentation tracks and reports API-level test outcomes by cross-referencing them against design specifications to ensure comprehensive coverage and compliance.

Can I update existing AT-RPT documents without breaking Obsidian vault standards?

Yes, you can update existing AT-RPT documents while maintaining Obsidian vault standards by automatically validating frontmatter requirements, scenario summarization, and change history logging.

How do I consolidate Go/No-Go judgments across multiple test scenarios?

You can consolidate Go/No-Go judgments across multiple test scenarios by aggregating scenario execution results and API cross-references into a single AT-RPT document for review.

Do I need validate_vault.py to ensure AT-RPT frontmatter compliance?

Yes, validate_vault.py is required to ensure AT-RPT frontmatter compliance and adherence to diopside's Obsidian operational standards before finalizing the acceptance test documentation.