atm10-source-of-truth-check

Align authoritative docs in atm10-* repositories with local doc maps.

4|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/8Dionysus/aoa-skills --skill atm10-source-of-truth-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atm10-source-of-truth-check
Source: https://github.com/8Dionysus/aoa-skills/tree/main/.agents/skills/atm10-source-of-truth-check
Command: npx skills add https://github.com/8Dionysus/aoa-skills --skill atm10-source-of-truth-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a local overlay for atm10-* repositories to map authoritative sources to repo-relative docs and surface a clear local review posture, reducing ambiguities about document authority.

Core Features & Use Cases

  • Local source-of-truth mapping for atm10-* repos, aligning local docs with canonical sources
  • Repo-relative guidance for surfaces like README.md, docs/*, and governance materials
  • Explicit local authority rules that stay aligned with the base workflow
  • Example: adapt the base source-of-truth check to a particular atm10-* project while preserving upstream integrity

Quick Start

Apply the overlay to your atm10-* repo by mapping authoritative docs to repo-relative patterns and enforcing a local review posture.

Frequently Asked Questions about atm10-source-of-truth-check

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

FAQPage Schema
How do I align local documentation with canonical sources in atm10 repositories?

To align local documentation with canonical sources in atm10 repositories, apply a local source-of-truth overlay that maps authoritative docs to repo-relative patterns like README.md and docs/*, enforcing a clear local review posture to reduce ambiguity.

What is a local source-of-truth overlay for repo-relative governance artifacts?

A local source-of-truth overlay maps authoritative governance artifacts to repo-relative documentation surfaces within atm10-* projects, providing explicit local authority rules while preserving the integrity of the base source-of-truth workflow.

Does the source-of-truth check work with standard project documentation surfaces like docs and README files?

Yes, the source-of-truth check explicitly covers repo-relative documentation surfaces such as README.md, docs/* directories, and governance artifacts within atm10-* projects where local adaptation is required.

How do I adapt a base source-of-truth check to a specific project without breaking upstream integrity?

You adapt the base source-of-truth check by applying the overlay to your specific project, mapping authoritative docs to repo-relative patterns and enforcing a local review posture while explicitly preserving upstream integrity.

Can I enforce a local review posture for documentation governance in atm10 projects?

Yes, you can enforce a local review posture for documentation governance in atm10-* projects by satisfying the requirements for a local canonical-file pattern and surface-aligned authority rules within the base source-of-truth workflow.

When do I need a local canonical-file pattern for source-of-truth mapping?

You need a local canonical-file pattern for source-of-truth mapping when reducing ambiguities about document authority across repo-relative documentation surfaces in atm10-* projects that require local adaptation from the base workflow.