NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 6 · Isolate and integrateLesson 1 of 2
Video lesson

L11 · Split independent work in separate worktrees

IntermediateVideo lesson
5 min readIntermediate
Downloads & resources
Download this lesson's materials, ready to use.

Skill packs and prompts are provided in English so they work best with the AI tools. Use them as-is.

Split Independent Work in Separate Worktrees

Learning time: about 33.9–50.0 active minutes. Choose ONE presentation: the text (about 5 minutes, estimated) OR the lesson video (3:54, measured). Then 30–45 minutes of practice and checking (estimated). Do not count both presentations. Setup delays and optional extra study are separate; learner timing has not yet been piloted.

Example prompt

Where you are: Module 6, lesson 11. You can supervise sequential work. Now try two small parallel assignments without letting both assistants edit the same working files.

What you will do

Create two isolated working copies from the same checkpoint, assign one owned output to each assistant and return two reviewable changes. You will explain why isolation helps and what it does not solve.

Teaching

Two conversations can share a folder. That does not make two simultaneous edits safe. One assistant may read a file just before the other rewrites it. Each can then report a reasonable result based on a different starting point.

A Git worktree gives a branch a separate working directory while retaining the repository's history. This protects working files from direct collisions. It does not make incompatible decisions compatible. Two branches can still change the same requirement or produce contradictory instructions.

First create and verify a checkpoint in your private practice repository. Confirm that it has at least one commit, that its status is understood and that no unfinished agent owns the files. Do not discard changes to make the screen look clean. Save or finish them deliberately before starting this exercise.

For clarity, this lesson uses manual Git worktrees with named branches. Both assistants can open those folders. This avoids assuming that Codex's app-managed detached worktree behaves exactly like Claude Code's named-worktree recipe.

From your practice repository, inspect first:

sh
git status --short
git branch --show-current
git rev-parse HEAD
git worktree list

Record the full starting revision. If the names or sibling folders below already exist, choose new names and record them; do not delete existing work. With a clean, understood starting point, these commands create the two practice branches and folders:

sh
git worktree add -b practice-guide ../workshop-guide
git worktree add -b practice-limits ../workshop-limits

Open one assistant in each new folder. Verify the folder and revision again. Installation, credentials and dependencies may differ by environment; a worktree is not a promise that every application is ready. Keep the task small enough to run sequentially if your account cannot support simultaneous work.

Worked example

Salma gives Claude Code the usage guide and Codex the limitations note. Both start from the same workshop checkpoint. Neither may alter the budget assumptions or calculator. Their outputs have separate paths.

She discovers that the limitations note calls the interest CSV “confirmed bookings.” The branches have no file conflict, but that statement is wrong: the data is fictional interest, not bookings or evidence of demand. Isolation protected files; her review protects meaning.

Do it yourself

Use the branch and folder names you actually created. Send this complete assignment to the assistant in the guide worktree:

Example prompt

You own only docs/USAGE.md in this private Workshop Launch Kit practice branch. First report your current directory, branch and starting commit. Read the supplied project brief and inspect the actual local calculator. Write plain instructions for opening and using it, including where the output appears and its limitations. Do not alter the calculator, inputs, other documents or repository settings. Do not publish, push or merge. Report changed files, checks performed and unresolved questions. If the expected project is absent, stop without inventing it.

Send this to the assistant in the limits worktree:

Example prompt

You own only docs/INPUT-LIMITS.md in this private Workshop Launch Kit practice branch. First report your current directory, branch and starting commit. Read the supplied brief and synthetic input files. Explain units, source assumptions, capacity limits and what the fictional interest data cannot prove. Do not alter calculations, inputs, other documents or repository settings. Do not publish, push or merge. Report changed files, supporting inputs and unresolved questions. If inputs are missing, state that limitation.

These directories and filenames are exercise outputs you may create; they are not promised to exist in the starter pack. Compare each result with its allowed path. Use your review log to record accuracy and scope. Commit reviewed work separately in its own worktree using the earlier Git workflow. Do not merge it yet.

Feedback and retry

Pause here before reading.

Success means two distinct folders/branches, a known common starting commit, separate owned files and no unauthorized edits. A useful guide must describe the real calculator. A useful limits note must distinguish assumptions from facts and interest from bookings.

If one assistant edits outside its path, stop both from writing while you inspect the changes. Preserve the files and identify the smallest repair. Do not reset the whole repository or delete a worktree containing unfinished work.

Retry by making the two assignments sequential in their isolated folders. You should obtain the same evidence of ownership and review. Parallel speed is optional; controlled work is the skill.

Check your understanding

Choose an answer and write one sentence explaining why before you read the answers.

  1. Two branches change different files and merge without a conflict. Does that prove their instructions agree?
    • A. Yes: no conflict means no disagreement.
    • B. No: file compatibility and meaning are different; read both outputs together and test their claims.
    • C. Yes, if the tests ran before the merge.

Answers

  1. B. No. File compatibility and meaning are different. Read both outputs together and test their claims against the project.

Summary

Separate working copies reduce collisions. Shared requirements, explicit ownership and integration review make the outputs usable together. Next, you will combine the changes deliberately.

Sources