evidence-ontology

Decompose prompts into canonical ontology elements and tag claims with the Evidence Ontology.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill evidence-ontology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evidence-ontology
Source: https://github.com/WesleyMFrederick/cc-workflows-plugin/tree/main/src-claude/skills/evidence-ontology
Command: npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill evidence-ontology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a canonical grounding for agent reasoning by loading and enforcing the Evidence Ontology, ensuring all claims, tags, and derivations are traceable to a single, canonical set of rules.

Core Features & Use Cases

  • Loads the complete Evidence Ontology and its 13 tag types into context to standardize reasoning and documentation.
  • Provides explicit tag formatting rules, validation guidance, and strengthening workflows to keep artifacts coherent across sessions.
  • Supports mid-session re-grounding and artifact verification via the verifying-evidence workflow to reduce context rot.

Quick Start

Run the kickoff prompt to load the full ontology into agent context.

Frequently Asked Questions about evidence-ontology

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

FAQPage Schema
How do I ground LLM reasoning with traceable evidence in prompt engineering?▼

To ground LLM reasoning with traceable evidence, you decompose prompts into canonical ontology elements and tag each claim using a 13-tag Evidence Ontology. This standardizes reasoning and ensures all derivations are traceable to a single set of rules.

What is an evidence ontology and how does it work for prompt decomposition?▼

An evidence ontology is a canonical set of 13 tag types used to decompose prompts into baseline, ideal, and delta buckets. It works by tagging each claim to surface gaps, prioritize questions and hypotheses, and guide design and documentation decisions.

How do I validate artifacts and prevent context rot during agent sessions?▼

You validate artifacts and prevent context rot by running mid-session re-grounding and using the verifying-evidence workflow. This checks loaded claims against the canonical ontology rules to reduce drift and maintain artifact coherence.

Does this evidence tagging approach support frontmatter metadata validation?▼

Yes, the evidence tagging approach supports frontmatter metadata validation. It provides explicit tag formatting rules and validation guidance to keep documentation artifacts coherent across multiple sessions.

How do I apply decision buckets to surface gaps in design documentation?▼

You apply decision buckets by separating context into baseline, ideal, and delta categories. This decomposition surfaces gaps between current and ideal states, allowing you to prioritize questions and hypotheses for design decisions.

What are the limitations of using a 13-tag ontology for prompt grounding?▼

The 13-tag ontology requires loading the complete rule set into context at kickoff, which consumes context window space. Mid-session re-grounding is necessary to prevent context rot and maintain artifact accuracy during long tasks.