doc-ut-plan

Name: doc-ut-plan
Availability: InStock
Author: tsuji-tomonori

Generate and revise UT-PLAN documents for the diopside Obsidian project.

1|Updated Feb 11, 2026

Search Tags:#testing #documentation #standardization #obsidian #diopside #unit test plan

Ready to run

npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-ut-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-ut-plan
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-ut-plan
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-ut-plan

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 ensures that Unit Test Plan (UT-PLAN) documents are created or revised according to the diopside Obsidian operational rules, standardizing test strategy, scope, and completion criteria.

Core Features & Use Cases

Standardized Document Creation: Generates new UT-PLAN documents or updates existing ones, ensuring compliance with Obsidian operational rules.
Consistent Planning: Helps define clear test objectives, perspectives, scope, and completion conditions.
Use Case: When starting the unit testing phase for a new module, use this Skill to generate the initial UT-PLAN document, ensuring all required sections and frontmatter are correctly populated based on design specifications.

Quick Start

Create a new UT-PLAN document for the 'Authentication Module' with the ID 'UT-PLAN-AUTH-001'.

Frequently Asked Questions about doc-ut-plan

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

FAQPage Schema

How do I standardize unit test plan creation in Obsidian?▼

To standardize unit test plan creation in Obsidian, generate UT-PLAN documents with enforced frontmatter, test strategy, scope, and completion criteria, ensuring strict consistency with design specifications like BD-TST and DD-API.

What is a UT-PLAN document and what sections does it require?▼

A UT-PLAN document defines unit testing strategy, scope, and completion criteria. It requires specific frontmatter and standardized sections for test objectives and perspectives, ensuring alignment with broader design documents in the Obsidian vault.

How do I generate a unit test plan based on existing design specifications?▼

Generate a unit test plan by referencing existing design documents like [[BD-TST-*]] and [[DD-API-*]]. The process populates required frontmatter and test sections automatically, ensuring the new UT-PLAN aligns with established architectural rules.

Does this unit test plan generation work with Obsidian vault validation?▼

Yes, unit test plan generation works with Obsidian vault validation by running scripts like validate_vault.py and auto_link_glossary.py. These enforce quality checks, ensuring proper linking and structural compliance within the diopside project.

Can I update an existing unit test plan instead of creating a new one?▼

Yes, you can revise existing UT-PLAN documents. The process updates test strategies, scopes, and completion criteria while re-validating frontmatter requirements and Obsidian operational rules to maintain standardized documentation.

Why are auto-linking and vault validation needed for unit test documentation?▼

Auto-linking and vault validation are needed to enforce output contracts and quality checks. They ensure standardized UT-PLAN documents maintain proper internal links and structural integrity within the diopside Obsidian vault.