aget-analyze-ontology

Analyze AGET ontology artifacts for completeness, consistency, coverage, and freshness issues.

1|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/aget-framework/template-spec-engineer-aget --skill aget-analyze-ontology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aget-analyze-ontology
Source: https://github.com/aget-framework/template-spec-engineer-aget/tree/main/.claude/skills/aget-analyze-ontology
Command: npx skills add https://github.com/aget-framework/template-spec-engineer-aget --skill aget-analyze-ontology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AGET ontology artifacts often drift, leaving undefined terms, inconsistent definitions, low coverage, and stale concepts that silently degrade specification quality and agent performance.

Core Features & Use Cases

  • Vocabulary Discovery: Scans controlled vocabulary sources to enumerate defined terms across the framework.
  • Completeness & Consistency Checks: Detects undefined term usage in specs and flags cross-vocabulary definition conflicts.
  • Coverage & Freshness Analysis: Quantifies how much vocabulary grounding exists in specs and identifies terms with no recent usage.
  • Tier Assessment & Ratio Diagnostics: Evaluates ONTOLOGY_TIER compliance and computes concept-to-requirement balance (OT-022) to identify under-specification or ontology overgrowth.
  • Use Case: When specification coverage drops or validation results look inconsistent across teams, use this skill to pinpoint exactly which terms, vocabularies, or freshness gaps are causing the problem.

Quick Start

Run the command to analyze ontology health and coverage by invoking the skill name aget-analyze-ontology.

Frequently Asked Questions about aget-analyze-ontology

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

FAQPage Schema
How do I check ontology consistency and vocabulary coverage in spec validation?

To check ontology consistency and vocabulary coverage, scan all configured vocabulary sources to map term definitions against observed spec usage, flagging cross-vocabulary conflicts and undefined terms in specification YAML and markdown files.

What causes undefined terms and inconsistent definitions in controlled vocabularies?

Undefined terms and inconsistent definitions occur when ontology artifacts drift over time, degrading specification quality. Scanning configured vocabulary sources identifies cross-vocabulary conflicts and completeness gaps causing these validation issues.

How do I detect stale concepts and unused terms in semantic analysis?

To detect stale concepts in semantic analysis, quantify vocabulary grounding in specification files and identify terms with no recent usage. This freshness analysis isolates ontology overgrowth and highlights unused vocabulary terms.

Does ontology tier assessment evaluate concept-to-requirement ratio diagnostics?

Ontology tier assessment evaluates ONTOLOGY_TIER compliance and computes the OT-022 concept-to-requirement ratio. This diagnostic identifies under-specification or ontology overgrowth by measuring balance between defined concepts and actual requirements.

What is the best way to audit ontology health for requirements engineering specs?

The best way to audit ontology health is to scan controlled vocabulary sources, map term definitions to specification usage, and assess ONTOLOGY_TIER compliance. This produces actionable recommendations resolving vocabulary completeness, consistency conflicts, and coverage gaps.

Why does specification validation accuracy decline across teams maintaining controlled vocabularies?

Validation accuracy declines when ontology artifacts drift, leaving stale concepts and inconsistent definitions. Running an ontology health audit pinpoints exactly which vocabulary terms or freshness gaps cause inconsistent validation results across teams.