Using git worktrees
Skill truong170201/work-unit-roadmap/skills/using-git-worktrees
Use when a WUR contract has executable project work that requires editing project files in a sparse worktree excluding agents/ and contracts/.From its SKILL.md
npx -y skills add truong170201/work-unit-roadmap --skill using-git-worktreesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, as published. Nobody here has run it
Sparse Worktrees For Contract Execution
WUR does not create a worktree just because /wur:start created a contract. The executor first reads the contract.
Use this skill only when the active contract contains executable project work and implementing it requires editing project files.
Principle
A worktree used by an external executor should not carry WUR state. agents/ is the source-of-truth wiki and contracts/ is the contract/report boundary. The executor works from the contract brief and must not edit those folders.
Recommended Sparse Worktree
git worktree add .worktrees/P{n}_contract -b work/P{n}_contract main
cd .worktrees/P{n}_contract
git sparse-checkout init --no-cone
git sparse-checkout set "/*" "!/agents/" "!/contracts/"
Verify:
git status --short
Test-Path agents
Test-Path contracts
agents/ and contracts/ should not be present in the execution worktree. If the Git version does not support the exclude patterns reliably, do not force automation; copy the contract instructions manually and keep execution out of agents/.
Rules
- Do not create a worktree when the contract has no executable project work.
- If there is no implementation task, report blocked/no-op/clarification-needed in the contract ledger.
- If implementation requires editing project files, create or reuse a sparse worktree before editing those files.
- Do not copy
agents/into the execution worktree. - Do not copy
contracts/into the execution worktree. - Do not use sparse worktree setup as a substitute for WUR receive.
- The executor returns evidence; WUR updates
agents/.
When To Use
| Situation | Use sparse worktree? |
|---|---|
| Contract has no executable project work | No; report blocked/no-op/clarification-needed |
| Report-only or clarification-only round | No |
| Implementation edits project files | Yes |
| User explicitly asks for isolated execution | Yes, if there is executable work |
| Git sparse checkout errors or permission problems | Prefer manual execution from contract |