doc-at-plan

Generate and revise AT-PLAN documents following diopside documentation conventions.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-at-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-at-plan
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-at-plan
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-at-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 streamlines the creation and revision of Acceptance Test Plans (AT-PLANs), ensuring they adhere to the diopside documentation standards for clarity and consistency.

Core Features & Use Cases

  • Standardized Document Creation: Generates AT-PLAN documents (docs/6.受入テスト(AT)/11.受入テスト計画(PLAN)/AT-PLAN-*.md) that meet all frontmatter and content requirements.
  • Consistency Enforcement: Ensures AT-PLANs align with FR/NFR, operational procedures, and other test artifacts (AT-SCN, AT-RPT, AT-GO).
  • Use Case: When initiating acceptance testing for a new feature, use this Skill to draft the initial AT-PLAN, defining the scope, criteria, and team structure according to project guidelines.

Quick Start

Use the doc-at-plan skill to create a new acceptance test plan for the user authentication module.

Frequently Asked Questions about doc-at-plan

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

FAQPage Schema
How do I generate an acceptance test plan that aligns with FR and NFR requirements?▼

To generate an acceptance test plan, use this Skill to draft AT-PLAN documents that ensure adherence to scope, judgment criteria, and execution structure while aligning with FR/NFR requirements. It automatically enforces diopside documentation conventions for consistency.

What is the best way to standardize acceptance test plan documents in Obsidian?▼

Standardizing acceptance test plan documents in Obsidian requires enforcing consistent frontmatter and content structure. This Skill generates AT-PLAN files that comply with diopside documentation standards, ensuring clarity and consistency across all test artifacts.

Can I use this to create an AT-PLAN that links to AT-SCN, AT-RPT, and AT-GO artifacts?▼

Yes, you can create an AT-PLAN that links to AT-SCN, AT-RPT, and AT-GO artifacts. The Skill ensures consistency enforcement across these test artifacts, aligning the acceptance test plan with operational procedures and related documentation.

Does the acceptance test plan generator support automated vault validation?▼

Yes, automated vault validation is supported through the validate_vault.py dependency. This ensures that generated AT-PLAN documents maintain structural integrity and comply with the required documentation conventions within your Obsidian vault.

How do I revise an existing acceptance test plan to meet documentation standards?▼

You revise an existing acceptance test plan by applying this Skill to update the document's scope, judgment criteria, and execution structure. It ensures the revised AT-PLAN adheres to diopside documentation conventions and aligns with current operational procedures.

When do I need to define acceptance test scope and team structure for a new feature?▼

You need to define acceptance test scope and team structure when initiating acceptance testing for a new feature. This Skill drafts the initial AT-PLAN, establishing the required scope, criteria, and team structure according to project guidelines.