We split this skill into the rules it gives an agent

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

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈4

  Distinctive · estimate

  This author's own choices. Worth a look.

• 3

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   After implementing and verifying a user-visible product change:

   line 10
2. Distinctive:

   Read and apply the canonical skill.

   line 12
3. Distinctive:

   Use this product repository’s code, tests, API schema, and docs as primary technical evidence.

   line 13
4. Very specific:

   Create or update the feature record in ../businessflow/features/.

   line 14
5. Very specific:

   Update affected business artifacts there and the landing implementation in ../synamcps-landing.

   line 15
6. Distinctive:

   Run the canonical validation steps and report all artifact dispositions.

   line 16
7. Very specific:

   If businessflow or synamcps-landing is unavailable, do not invent a substitute path.

   line 18

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