coordinator-source-of-truth

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

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill coordinator-source-of-truth-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinator-source-of-truth
Source: https://github.com/elbruno/ElBruno.MagenticUI/tree/main/.squad/templates/skills/coordinator-source-of-truth
Command: npx skills add https://github.com/elbruno/ElBruno.MagenticUI --skill coordinator-source-of-truth-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple agents collaborate in a Squad workspace, it is often unclear which file is authoritative, who is allowed to write a given file, 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, decide where state belongs, and answer ownership questions. ## Core Features & Use Cases - File Hierarchy Reference: A full table mapping every Squad file (decisions.md, team.md, routing.md, charters, audit trails, and more) to its status, allowed writers, and allowed readers. - Precedence and Append-Only Rules: Explicit rules stating that squad.agent.md overrides all other files and that append-only logs must never be 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 history.md, the coordinator loads this Skill to confirm the correct writer and enforcement rule. ## Quick Start Ask the coordinator to load the coordinator-source-of-truth skill to determine which agent may write a specific Squad file.

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 a piece of state belongs in?

Consult the file hierarchy table in this Skill, which lists every Squad file with its status and purpose. Authoritative files hold canonical config like decisions and roster, while derived append-only files hold logs and history.

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.

What happens when squad.agent.md conflicts with another Squad file?

squad.agent.md always wins. It is the only file with hard governance authority, so any conflicting rule in another file is overridden by the governance definitions in squad.agent.md.

Can agents edit append-only Squad history files after writing?

No. Append-only files such as history.md, orchestration logs, and audit trails must never be retroactively edited. Corrections are added as new entries that reference the prior one.

Does the Squad file hierarchy change with different state backends?

The hierarchy stays the same, but derived append-only files are accessed through runtime state tools like squad_state_read and squad_state_write. The backend decides whether they live on disk, in git-native state, or an external provider.