pfc-oaa-v7

Route OAA v7 ontology requests to creation, migration, or validation workflows.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/ajrmooreuk/pfi-w4m-dev --skill pfc-oaa-v7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pfc-oaa-v7
Source: https://github.com/ajrmooreuk/pfi-w4m-dev/tree/main/pfc-core/skills/pfc-oaa-v7
Command: npx skills add https://github.com/ajrmooreuk/pfi-w4m-dev --skill pfc-oaa-v7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ontology development and governance are complex, error-prone, and time-consuming; this skill automates end-to-end creation, conversion, validation, and registry integration for OAA v7 ontologies.

Core Features & Use Cases

  • Automates creation, conversion, and validation of ontologies to OAA v7 with built-in quality gates.
  • Supports new ontology creation, v6→v7 migration, and interactive validation workflows.
  • Includes registry checks, namespace governance, and artifact generation for deployment.

Quick Start

Invoke the skill with a workflow letter (A, B, or C) and the target ontology code or domain name to begin the corresponding workflow.

Frequently Asked Questions about pfc-oaa-v7

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

FAQPage Schema
How do I automate OAA v7 ontology creation and validation?

You can automate OAA v7 ontology creation and validation by invoking the skill with workflow A for new creation or C for interactive validation, which plans competency, schema, and governance steps before executing quality gates and generating artifacts.

What is the best way to migrate an ontology from v6 to v7?

The best way to migrate an ontology from v6 to v7 is using workflow B, which handles conversion, enforces quality gates, generates new artifacts, and updates the ontology registry to reflect the migrated version.

Can I check the ontology registry for duplicates before creating a new OAA v7 ontology?

Yes, the skill automatically checks the ontology registry for duplicates during the planning phase, identifying the target series and preventing duplicate ontology creation before executing any workflow.

Do I need to specify a workflow type to start ontology governance automation?

Yes, you need to invoke the skill with a workflow letter (A, B, or C) and a target ontology code or domain name to begin the corresponding creation, migration, or validation workflow.

Does OAA v7 ontology automation handle namespace governance and artifact generation?

Yes, the automation includes namespace governance checks and handles artifact generation for deployment as part of its end-to-end execution, ensuring proper governance and delivery of the final ontology files.

Why does ontology migration require quality gates during v6 to v7 conversion?

Quality gates are required during v6 to v7 conversion to enforce validation rules, ensure schema competency, and prevent errors in the generated artifacts before the ontology registry is updated.