# Submodule Worktree

> Worktree strategy for a submodule-monorepo where the superproject is a thin shell (doc storage + submodule pointers) and the real code lives in submodules (illustratively fe/be). TRIGGER on ONE condition: a worktree / parallel-implementation request lands in a project whose profile (.claude/project-profile/, written by /team-init) records a Submodule Layout section with Submodule-monorepo: yes. A bare .gitmodules file is NOT a trigger — run /team-init first so the layout, worktree targets, and carry-list are recorded. Rules: worktree ONLY the code submodules, keep the superproject as the single original checkout (the docs/ anchor), CARRY gitignored runtime files (.env/secrets/local config) into each new worktree, and defer submodule-pointer bumps. The submodule-specialized companion to parallelization.

## Facts
- Page: https://tashan.sh/capability/skill-junjak-submodule-worktree
- tashan id: skill:JunjaK/submodule-worktree
- Source: https://github.com/JunjaK/ai-harness
- Type: skill
- Category: other
- tashan score: not scored (catalogued only — too little public evidence)
- Adoption: 9.0
- Upkeep: 81.0
- Freshness: 98.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- Official: no

## Install

```sh
cp -r submodule-worktree ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-08-14 by tashan (https://tashan.sh) from public evidence. Scorer s5.