We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈6

  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:

   Do not invent ticket IDs; verify against Linear when connected

   line 15
2. Very specific:

   Prefer linking the approved IMPLEMENTATION_PLAN.md / GitHub issue to the Linear parent.

   line 27
3. Distinctive:

   Create child workstream tasks only when parallel streams are cleanly separable.

   line 28
4. Distinctive:

   Update status to reflect plan gate: planned → in progress after approval → done after validation.

   line 29
5. Distinctive:

   If Linear is unavailable, fall back to GitHub issues / local placeholders and report the gap.

   line 31
6. Distinctive:

   Do not auto-close parent epics without Captain confirmation

   line 35
7. Distinctive:

   Do not store secrets in Linear descriptions

   line 36
8. Very specific:

   Do not treat Linear as the only source of truth for approval (repo IMPLEMENTATION_PLAN.md wins)

   line 37

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