skills.rest
github
githubOFFICIAL
Explore all skills by this author →
WebsiteGitHub

coordinator-source-of-truth

Defines file ownership, write permissions, and precedence rules for Squad state files.

5.1k|530|Updated Aug 12, 2025
Search Tags:#coordinator#source of truth#Permissions#file ownership#Multi-Agent#Squad#Governance
One-click install
npx skills add https://github.com/github/gh-aw --skill coordinator-source-of-truth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coordinator-source-of-truth
Source: https://github.com/github/gh-aw/tree/main/.squad/templates/skills/coordinator-source-of-truth
Command: npx skills add https://github.com/github/gh-aw --skill coordinator-source-of-truth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When multiple agents collaborate in a Squad repository, it is often unclear which file is authoritative, who may write to it, and which file wins when two sources conflict. This Skill provides the complete file-by-file source-of-truth hierarchy so the coordinator can resolve write conflicts and ownership questions.

Core Features & Use Cases

  • File Authority Matrix: A full table classifying each Squad file as Authoritative, Derived/append-only, or Reference, with explicit read/write permissions per role.
  • Conflict Precedence Rules: Clear rules such as "squad.agent.md wins over any other file" and append-only files never being retroactively edited.
  • State Backend Awareness: Distinguishes static on-disk config from mutable runtime state accessed via squad_state_read/write/append tools.
  • Use Case: Before writing to .squad/decisions.md or reviewing whether an agent violated the append-only rule on .squad/orchestration-log/, load this Skill to adjudicate the correct behavior.

Quick Start

Ask the coordinator agent to load the coordinator-source-of-truth skill to determine who owns a specific Squad file and whether a planned write is permitted.

Frequently Asked Questions about coordinator-source-of-truth

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

FAQPage Schema
How do I decide which Squad file is authoritative when two files conflict?▼

When files conflict, .github/agents/squad.agent.md always wins because it is the only file with hard governance authority. All other files are either authoritative config or derived append-only state subordinate to it.

Who is allowed to write to .squad/decisions.md?▼

Only the Squad Coordinator may write to .squad/decisions.md, and only by appending new entries. Other agents may propose decisions in their responses, but the coordinator records accepted ones.

Can agents edit append-only Squad history or log files?▼

No, append-only files like agent history, orchestration logs, and audit trails must never be retroactively edited to change meaning. Corrections are added as new entries referencing the prior one.

What is the difference between authoritative and derived files in Squad?▼

Authoritative files are static config that always live on disk, such as team.md and routing.md. Derived files are mutable runtime state accessed via squad_state_read, squad_state_write, and squad_state_append tools regardless of backend.

When should the coordinator load the source-of-truth skill?▼

Load it when resolving where a piece of state belongs, checking whether an agent broke the append-only rule, answering file-layout questions, or adjudicating conflicts between two Squad files.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
209

init-mode

Propose cast roles and scaffold .squad structure after user confirmation.

Official
Advanced
B0yZ4kr14B0yZ4kr14

speckit-squad-route

Route open Speckit tasks to active Squad agents via capability matching or round-robin.

Community
Intermediate
bluejayAbluejayA
2

devflow-audit

Append interaction logs with ISO 8601 timestamps to an audit file.

Community
Basic
agent0aiagent0ai
1.4k

App Files And APIs

Read, discover, and modify app files via space.api helpers.

Official
Intermediate