doc-at-ops

To create operational acceptance test documents in Obsidian, this Skill generates AT-OPS files using a strict template and frontmatter requirements. It ensures clarity by defining acceptance criteria for both normal and abnormal operational scenarios.

Operational acceptance criteria in testing documentation define the specific checks for normal and abnormal operational scenarios. This Skill helps establish these criteria within AT-OPS documents to ensure operational readiness and compliance.

You validate Obsidian vault integrity using Python scripts that automate glossary linking and vault validation. This ensures your AT-OPS documents maintain required frontmatter and link correctly to relevant design documents.

Yes, this Skill works with existing Obsidian vaults by providing update guidance for current AT-OPS documents. It validates frontmatter compliance and ensures operational acceptance criteria are properly maintained.

You need to update operational acceptance test documents when introducing new features that require specific operational checks. This Skill provides instructions for updating existing AT-OPS files to reflect new acceptance criteria and operational considerations.

The best way to maintain frontmatter standards in testing documentation is through automated vault validation scripts. This Skill enforces strict frontmatter requirements and automatically links glossary terms to preserve document integrity.