We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈5

  Distinctive · estimate

  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:

   Keep implementation-coupled documentation accurate without creating an approval gate.

   line 9
2. Distinctive:

   Update automatically when required by the approved implementation:

   line 11
3. Distinctive:

   Stop and ask before materially changing durable governance or project-policy documents unless the user explicitly requested that document:

   line 17
4. Distinctive:

   Before asking, state what should change, why, what implementation/validation already occurred, and whether the update is required or …

   line 24
5. Distinctive:

   After approval, update only the canonical owner of each fact/rule.

   line 28

≈ “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.