agentleFS
aaronreneaaronrene/knowtation/.claude/skills/governance-sync/SKILL.md

governance-sync

Skill1 starsChanged 2 months agoMITView on GitHub

Use when a session is ending, handover/roadmap may be stale, or the operator runs /governance-sync. Keep {{docs.roadmap_path}} and {{docs.handover_path}} aligned with true VCS state and phase truth. This automates the SD-17 obligation — it does not invent new policy. Default: dry-run. Writes nothing except the local .overseer/last_governance_sync marker when D1/D2 are aligned (GFG carve-out). Governance-doc patches, commits, and realign apply only on explicit non-dry-run; never on {{vcs.git.main_branch}}. After apply/write of living docs, run ok next (or equivalent Read) and include…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 3 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use when a session is ending, handover/roadmap may be stale, or the operator runs /governance-sync.

    line 3
  2. Very specific:

    Keep {{docs.roadmap_path}} and {{docs.handover_path}} aligned with true VCS state and phase truth.

    line 7
  3. Very specific:

    Read VCS status via the kit adapter for {{vcs.regime}} (fail-closed on read errors).

    line 19
  4. Very specific:

    If NEXT is Thinking → Auto, emit {step}a or {step}b only — not both unless {step}a incomplete.

    line 24
  5. Very specific:

    After apply/write of living docs, run ok next (or equivalent Read) and include the ## CURRENT NEXT — paste this heading+fence in the …

    line 37
  6. Very specific:

    When the handover NEXT is land-phase=land-a and D1 is drifted (the merge landed on {{vcs.git.main_branch}}), the plan emits the land-b …

    line 42
  7. Very specific:

    No merge to {{vcs.git.main_branch}} without Tier 3

    line 52
  8. Distinctive:

    No staging push without Tier 3

    line 53
  9. Distinctive:

    No live posture flips

    line 54
  10. Distinctive:

    No peer-repo writes from this command — workspace relay check is read-only (§MR.8)

    line 55
  11. Very specific:

    After advancing product_order PRIMARY, refresh each relay: true tip (role=relay or ## PRODUCT RELAY —) and run:

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Governance sync skill

Use when a session is ending, handover/roadmap may be stale, or the operator runs /governance-sync.

Purpose

Keep {{docs.roadmap_path}} and {{docs.handover_path}} aligned with true VCS state and phase truth. This automates the SD-17 obligation — it does not invent new policy.

Read first

  • {{docs.handover_path}} — current NEXT block
  • {{docs.roadmap_path}} — build status table
  • policy/tiers.yaml, policy/model-labels.yaml
  • .overseer/config.yaml — regime and doc paths

Workflow (docs-first)

  1. Read VCS status via the kit adapter for {{vcs.regime}} (fail-closed on read errors).
  2. Compare docs to reality; list drift (phase status, branch/sha, NEXT prompt staleness).
  3. Update {{docs.roadmap_path}} first.
  4. Regenerate {{docs.handover_path}} from updated roadmap + VCS snapshot.
  5. Include Model: on every NEXT block per policy/model-labels.yaml.
  6. If NEXT is Thinking → Auto, emit {step}a or {step}b only — not both unless {step}a incomplete.

CLI (when K4/K5 land)

/path/to/overseer-kit/cli/ok governance-sync --dry-run
/path/to/overseer-kit/cli/ok governance-sync

Default: dry-run. Writes nothing except the local .overseer/last_governance_sync marker when D1/D2 are aligned (GFG carve-out). Governance-doc patches, commits, and realign apply only on explicit non-dry-run; never on {{vcs.git.main_branch}}.

After apply/write of living docs, run ok next (or equivalent Read) and include the ## CURRENT NEXT — paste this heading+fence in the user-visible close.

Post-merge land closeout (PMHF)

When the handover NEXT is land-phase=land-a and D1 is drifted (the merge landed on {{vcs.git.main_branch}}), the plan emits the land-b paste for the same slice. land-b required: ok governance-sync --dry-run then apply; paste land-b; do not re-paste land-a.

Closing commit

Feature branch only. Message pattern: governance: sync handover + roadmap (<date>). Bundle both docs.

Hard stops

  • No merge to {{vcs.git.main_branch}} without Tier 3
  • No staging push without Tier 3
  • No live posture flips
  • No peer-repo writes from this command — workspace relay check is read-only (§MR.8)

Multi-repo (when workspace: configured)

After advancing product_order PRIMARY, refresh each relay: true tip (role=relay or ## PRODUCT RELAY —) and run:

ok workspace check-next

governance-sync footer / JSON key workspace_relay reports not_configured|ok|stale_relay|ambiguous_primary|missing_member|error. Multi-repo SD-17 is incomplete until check-next exits 0. Single-repo docs↔VCS sync remains required.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.