doc-it-tdat

Generate and revise IT-TDAT Markdown documents for diopside integration testing.

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

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 helps you create and revise IT-TDAT (Integration Test - Test Data Design) documents according to diopside conventions, ensuring necessary datasets and prerequisite states are properly prepared for integration testing.

Core Features & Use Cases

  • Document Generation: Creates new IT-TDAT-*.md documents following a strict template.
  • Document Revision: Updates existing test data, prerequisite states, and recovery data for integration tests.
  • Synchronization: Ensures test data aligns with changes in [[IT-PLAN-*]] and [[IT-CASE-*]] documents.
  • Use Case: When a new feature requires specific data configurations for integration testing, use this Skill to generate the IT-TDAT document detailing the data setup, including initial states and any necessary recovery data.

Quick Start

Use the doc-it-tdat skill to create a new integration test data design document for the user authentication module.

Frequently Asked Questions about doc-it-tdat

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

FAQPage Schema
How do I create integration test data design documents in Markdown for Obsidian?

Integration test data design documents are generated as IT-TDAT Markdown files following Obsidian conventions, ensuring datasets and prerequisite states are structured for the diopside framework. New documents are created using a strict template.

What is the best way to synchronize existing test data with integration test plans and cases?

Existing test data synchronization aligns IT-TDAT documents with updated IT-PLAN and IT-CASE files. Revisions update test data, prerequisite states, and recovery data to maintain consistency across integration testing artifacts.

Does this test data generation approach support prerequisite states and recovery data setup?

Prerequisite states and recovery data setup are fully supported during integration test data generation. The process details initial data configurations and necessary cleanup states required for valid test execution.

How do I update test data configurations when integration test cases change?

Updating test data configurations involves revising the IT-TDAT document to reflect changes in linked IT-CASE files. The skill ensures datasets and prerequisite states remain synchronized with the latest test case requirements.

Do I need Obsidian to manage integration test data design documents?

Obsidian is required to manage IT-TDAT documents effectively, as the generated Markdown files adhere to Obsidian operational conventions and utilize its linking features for test plan synchronization.

Why does my integration test data design need to align with diopside conventions?

Aligning with diopside conventions ensures structured preparation of datasets and prerequisite states required for integration testing. This standardization guarantees necessary recovery data is properly documented for test execution.