frmoretto

Source Of Truth Creator — Development skill for Claude Code

Development community

Claude skill & templates for creating epistemically honest Source of Truth documents.

How to install Source Of Truth Creator

This entry records only its repository, not the path inside it, so there is no exact command to give. Open frmoretto/source-of-truth-creator and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Source Of Truth Creator does

Claude skill & templates for creating epistemically honest Source of Truth documents. Prevents 6 failure modes: unqualified headers, unmarked estimates, self-assessment bias, absence-as-proof claims, illustrative-as-data, staleness. Companion to Clarity Gate.

Alternatives in Development

  • Career-Ops For Codex — Read CLAUDE.md for all project instructions, routing, and behavioral rules 32.5k ★
  • Claude Code iOS Dev Guide — A comprehensive guide for setting up Claude Code CLI with PRD-driven workflows, extended thinking (ultrathink) 492 ★
  • Obsidian Reconcile — Find and resolve contradictions in the vault — the vault maintains its own truth 277 ★

README

Source of Truth Creator v1.1

**Create epistemically honest Source of Truth documents that pass verification.**

[![License: CC BY 4.0](https://img.shields.io/badge/License-CC_BY_4.0-lightgrey.svg)](https://creativecommons.org/licenses/by/4.0/)

*"A Source of Truth that overstates certainty is worse than no Source of Truth — it creates false confidence."*


The Problem

You write a document labeled "Source of Truth" but it contains:

  • Estimates formatted like verified data
  • Self-assessments that look like external validation
  • "No prior art found" stated as verified fact
  • URLs verified yesterday that may 404 today

**The document looks authoritative. Readers trust it. But it overstates certainty.**


What Is Source of Truth Creator?

A **practitioner-accessible** methodology and Claude skill for creating documents with **calibrated confidence** — where readers have accurate trust in each claim.

**Novelty disclosure:** The eight failure modes below synthesize established frameworks (GRADE, ICD 203, PRISMA, etc.). Our contribution is accessibility and documentation-specific implementation—not inventing new epistemic concepts. See [Prior Art & Transparency](#prior-art--transparency).

The Eight Failure Modes It Prevents

Failure Mode Problem Solution
Verified Header Trap Header says "VERIFIED" but body has estimates Qualify: "VERIFIED (with noted exceptions)"
Internal Measurement Trap Informal timing marked same as benchmarks Add: [single run, informal]
Self-Assessment Trap Self-scores look like external validation Label: "Author judgment, not audited"
Absence-as-Proof Trap "Not found" stated as verified Add: "to author's knowledge, [date] search"
Illustrative-as-Data Trap Examples appear in data tables Separate: Examples section vs. Verified Data
Staleness Trap No freshness warnings on volatile claims Mark: [STABLE] / `[VOL