跳到正文
cccskills
免费在 GitHub 公开

coordinator-source-of-truth

Consult Squad’s file ownership and authority rules to decide where state belongs, who may read or write it, and which source takes precedence. Distinguish authoritative configuration from append-only histories and reference material.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

The complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand when it needs to resolve a write conflict, decide where a piece of state belongs, or answer a 'who owns this file' question.

查看安装方法

适用场景

  • Decide where Squad state or decisions should be stored
  • Check who may read or write a particular file
  • Resolve conflicts between file contents
  • Review corrections to append-only history

包含的文件(1)

  • SKILL.md5.8 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Load this skill when: the coordinator (or any agent) needs to resolve a "where does this state belong?" or "who is allowed to write this file?" question — e.g., when about to write .squad/decisions.md, when reviewing whether an agent broke the append-only rule, when answering a user question about Squad's file layout, or when adjudicating a conflict between two files. The short summary in squad.agent.md is for routing; this skill is the full reference.

State backend note

Files below marked as "Derived / append-only" are mutable state — agents access them with runtime state tools (squad_state_read, squad_state_write, squad_state_append, squad_state_delete, squad_state_list). The runtime decides whether the configured backend stores them on disk, git-native state, or an external provider. Files marked as "Authoritative" are static config and always live on disk regardless of backend.

File hierarchy

FileStatusWho May WriteWho May Read
.github/agents/squad.agent.mdAuthoritative governance. All roles, handoffs, gates, and enforcement rules.Repo maintainer (human)Squad (Coordinator)
.squad/decisions.mdAuthoritative decision ledger. Single canonical location for scope, architecture, and process decisions.Squad (Coordinator) — append onlyAll agents
.squad/team.mdAuthoritative roster. Current team composition.Squad (Coordinator)All agents
.squad/routing.mdAuthoritative routing. Work assignment rules.Squad (Coordinator)Squad (Coordinator)
.squad/ceremonies.mdAuthoritative ceremony config. Definitions, triggers, and participants for team ceremonies.Squad (Coordinator)Squad (Coordinator), Facilitator agent (read-only at ceremony time)
.squad/casting/policy.jsonAuthoritative casting config. Universe allowlist and capacity.Squad (Coordinator)Squad (Coordinator)
.squad/casting/registry.jsonAuthoritative name registry. Persistent agent-to-name mappings.Squad (Coordinator)Squad (Coordinator)
.squad/casting/history.jsonDerived / append-only. Universe usage history and assignment snapshots.Squad (Coordinator) — append onlySquad (Coordinator)
.squad/agents/{name}/charter.mdAuthoritative agent identity. Per-agent role and boundaries.Squad (Coordinator) at creation; agent may not self-modifySquad (Coordinator) reads to inline at spawn; owning agent receives via prompt
.squad/agents/{name}/history.mdDerived / append-only. Personal learnings. Never authoritative for enforcement.Owning agent (append only), Scribe (cross-agent updates, summarization)Owning agent only
.squad/agents/{name}/history-archive.mdDerived / append-only. Archived history entries. Preserved for reference.ScribeOwning agent (read-only)
.squad/orchestration-log/Derived / append-only. Agent routing evidence. Never edited after write.ScribeAll agents (read-only)
.squad/log/Derived / append-only. Session logs. Diagnostic archive. Never edited after write.ScribeAll agents (read-only)
.squad/templates/Reference. Format guides for runtime files. Not authoritative for enforcement.Squad (Coordinator) at initSquad (Coordinator)
.squad/rai/policy.mdAuthoritative RAI policy. Check categories, terminology standards, and opt-out rules.Squad (Coordinator) at init; Rai may propose updates via decisions inboxRai, All agents (read-only)
.squad/rai/audit-trail.mdDerived / append-only. RAI review evidence log. Redacted — never contains raw secrets or harmful content.Rai (append only)Rai, Squad (Coordinator)
.squad/fact-checker/policy.mdAuthoritative verification + Devil's Advocate policy. Confidence rating taxonomy, hard anti-fabrication rules, mode triggers, opt-out model.Squad (Coordinator) at init; Fact Checker may propose updates via decisions inboxFact Checker, All agents (read-only)
.squad/fact-checker/audit-trail.mdDerived / append-only. Verification verdicts + DA brief evidence log. Succinct — verdict + citation, never raw source material.Fact Checker (append only)Fact Checker, Squad (Coordinator)
.squad/plugins/marketplaces.jsonAuthoritative plugin config. Registered marketplace sources.Squad CLI (squad plugin marketplace)Squad (Coordinator)

Rules

  1. If squad.agent.md and any other file conflict, squad.agent.md wins. It is the only file with hard governance authority.
  2. Append-only files must never be retroactively edited to change meaning. They are diagnostic and audit-trail material. Corrections go in a new entry that references the prior one.
  3. Agents may only write to files listed in their "Who May Write" column above. Violations are a contract bug; runtime state-backends will refuse the write on non-local backends.
  4. Non-coordinator agents may propose decisions in their responses, but only Squad (Coordinator) records accepted decisions in .squad/decisions.md.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

中文简介正在准备中。当前显示英语简介。

  • Locate team files across separate working directories
  • Record decisions that affect other agents
  • Request input from another specialist
github/gh-aw54212026年10月19日 更新

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

中文简介正在准备中。当前显示英语简介。

  • Share development rules across multiple agents
  • Keep team-specific agent names out of code and tests
  • Check affected tests before declaring work complete
github/gh-aw54212026年10月19日 更新

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

中文简介正在准备中。当前显示英语简介。

  • Designing a new workflow through questions
  • Investigating failed runs and recurring errors
  • Upgrading workflows and addressing deprecations
github/gh-aw54212026年10月19日 更新

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

中文简介正在准备中。当前显示英语简介。

  • Proposing a major architecture change
  • Replanning milestones after a foundation change
  • Comparing technical options before seeking approval
github/gh-aw54212026年10月19日 更新

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

中文简介正在准备中。当前显示英语简介。

  • Updating the firewall version used by gh-aw
  • Reviewing release notes for integration changes
  • Checking configuration schema differences
github/gh-aw54212026年10月19日 更新

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

中文简介正在准备中。当前显示英语简介。

  • Reviewing git operations after repository checkout
  • Checking tokens for private cross-repository access
  • Reviewing sparse and shallow checkout changes
github/gh-aw54212026年10月19日 更新

查看 github 的全部技能

报告此技能的问题