feature

Assign each agent its own git worktree and feature branch so filesystem-level isolation prevents silent overwrites. Define shared contracts and ownership boundaries first, then merge one branch at a time with a build verification after each merge.

Run git worktree add with a new branch, for example git worktree add ../skyboard-name -b feature/name. Copy gitignored files like .env manually since they do not transfer automatically.

Writing failing tests first confirms they actually test the intended behavior and creates a checkpoint commit as a safety net. If later code fixes a test instead of implementing the feature, the diff exposes the shortcut.

No. Two agents writing to the same working tree silently overwrite each other because git does not warn about concurrent edits, and the last write wins. Each agent must get its own worktree before writing any code.

Change the PORT value in each worktree's .env file and update the dev server proxy configuration to match. If you only write code and run type checks or tests without launching the app, no port changes are needed.

A shared database means concurrent migrations can conflict, so schema changes must be coordinated and ALTER statements should not run simultaneously. Practical concurrency caps around four to eight worktrees before review throughput becomes the bottleneck.