agentleFS
igovetigovet/cortex-orch-acp/skills/documentation-sync/SKILL.md

documentation-sync

Skill1 starsChanged 59 days agoMITView on GitHub

Update affected project knowledge after verified changes while preserving manual documentation.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read applicable indexes and linked pages for the assigned scope.

    line 41
  2. Distinctive:

    Update durable knowledge, public guidance and examples only where affected.

    line 44
  3. Distinctive:

    Use an optional declared Markdown example only when it resolves a real content question.

    line 47
  4. Distinctive:

    Do not add a reviewer assignment to the plan.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

Documentation synchronization

Responsibility

RoleWork
CoordinatorAssess documentation impact and assign affected paths with the implementation or as independent work
Assigned implementing worker or technical writerApply this skill, confirm source-backed facts and update only affected documentation
Runtime's mandatory independent reviewCheck material documentation claims against source, commands and links

The coordinator may inspect bounded project source, report evidence and public artifacts read-only to reconcile cited revisions and decide scope. Workers own project edits and checks; the coordinator does not rerun project checks. A stale or absent index does not automatically require harvest. The coordinator source-read restriction in knowledge-harvest applies only to harvests, not ordinary work.

The worker assigned the affected documentation applies this skill. The coordinator does not read another role's SKILL.md.

For ordinary completion, include related documentation in the implementing worker's assignment when practical. Use a separate technical writer when the documentation is independent work or needs distinct ownership. Supported impact requires the affected updates and proportionate verification before acceptance; a supported no-impact conclusion needs no token edit or extra worker. If inspection is incomplete, gather bounded missing evidence or leave the impact unresolved.

Inputs for the assigned worker

  • Verified behavior, architecture, interface, command or ownership changes.
  • Exact affected index/page paths, requirements and preservation boundaries.
  • Relevant reports, source routes and known uncertainties.

Work sequence

  1. Read applicable indexes and linked pages for the assigned scope.
  2. Confirm consequential claims in source, tests or executable configuration.
  3. Preserve manual material outside generated blocks unless its change is authorized.
  4. Update durable knowledge, public guidance and examples only where affected.
  5. Validate changed links, anchors, commands, terminology and stated behavior.
  6. Publish an ordinary Markdown report using the live draft creator's guidance. Use an optional declared Markdown example only when it resolves a real content question. Standard skill/reference reads do not authorize reading manifests, databases or other runtime internals.

Verification and completion

  • The runtime's mandatory review checks material claims; list them in your report. Do not add a reviewer assignment to the plan; no special publication kind exists.
  • A supported no-impact conclusion can use existing evidence without a token edit or extra worker.
  • Missing inspection is not proof of no impact. State unverified facts and unrun checks.
  • Required updates and their verification must finish before task completion.
  • Record findings and follow-up in your report as unresolved; the pipeline is runtime-owned and the coordinator decides the next action from your report.
  • Harvest already owns its documentation work; do not duplicate it under another label.

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.