We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 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.

• 2

  Very specific

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

• Common
• Distinctive
• Very specific

1. Distinctive:

   Run non-trivial implementation through an issue document so problem, scope, risks, validation, and next steps stay explicit.

   line 8
2. Very specific:

   If the request is still vague, hand off to spec-writing first.

   line 12
3. Distinctive:

   Create or update an issue doc before coding.

   line 13
4. Distinctive:

   Keep the issue state in sync with actual work.

   line 14
5. Distinctive:

   Use troubleshooting notes, decision records, and review notes when the work produces reusable evidence beyond the issue itself.

   line 19
6. Distinctive:

   Always remind what was just completed and what remains.

   line 20
7. Very specific:

   Keep the issue doc focused on execution state.

   line 38

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