Choose the scope before starting
A workspace gives a mission the folders and repositories it may work with. Open the intended folder before creating the mission. An unavailable or degraded workspace blocks new work until its location is usable again.
A multi-repository workspace lets one mission coordinate a change across related repositories. Include only the repositories needed for the objective. Selecting a folder is different from giving unrestricted access to every file on the Mac: the access mode governs what operations may proceed.
Choose where changes belong
Review branch and placement choices before the first message. Work in the current checkout when that is intentional, or use an isolated working copy when you need separation. Existing uncommitted work belongs to you; inspect the selected checkout before asking an agent to change it.
Orchestrated specialists can use isolated working copies for their assigned writes. Read-only specialists can inspect the mission checkout. Isolation separates files, but does not itself mean that a change passed review or is ready to merge.
Give multi-repository work a clear finish
Name the repositories affected, the compatibility constraints between them, and how each side will be tested. Ask the mission to report any part it could not verify. An API change and its client update may need coordinated delivery even when their source edits are complete.
Moving to Skyflo Cloud
An eligible move carries the mission record, uncommitted changes and unpushed commits. Ignored files, untracked credential files and some large files stay on the Mac. The move dialog reports omissions. Review those before relying on the remote working copy.