We split this skill into the rules it gives an agent

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

• 3

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Create a new git branch: feature/<project-name>-v1 (or use phase number if building incrementally).

   line 10
2. Very specific:

   Create a git worktree in an isolated directory: ../<project-name>-worktree.

   line 11
3. Distinctive:

   Run project setup in the worktree: install dependencies, build.

   line 12
4. Distinctive:

   Verify clean test baseline: Run the full test suite. ALL existing tests must pass.

   line 13
5. Distinctive:

   If tests fail: STOP. Surface failures to the user.

   line 14
6. Distinctive:

   If no tests exist (new project): note this and proceed.

   line 15
7. Very specific:

   If use_worktrees is set to false in settings, skip worktree creation and work in the current directory.

   line 21
8. Distinctive:

   If a worktree already exists for this project, ask the user whether to reuse or create a new one.

   line 22

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