What problem does it solve? Running two FSI Docker stacks at once fails out of the box because of pinned container names, fixed host ports, and a shared untagged image. This Skill generates a throwaway Compose override that shifts one stack onto its own ports, container names, image tag, and log directory, so a git worktree branch runs beside the standard stack. ## Core Features & Use Cases - Port-offset override generation: A PowerShell script writes a docker-compose.ports-<tag>.yml file that offsets every host port by slot x 100, renames the seven pinned containers, and tags the image per branch. - Collision and trap handling: The script probes shifted ports for conflicts, applies the Compose !override tag to avoid the ports-append trap, and points Compose at the main repo's .env so FHIR token acquisition works in a worktree. - Use Case: You have the main FSI stack running on standard ports and need to test branch FACS-824 from a worktree. Run the script with -Slot 1, then start the stack with the printed command and verify both projects in docker compose ls. ## Quick Start Ask the agent to run the FSI stack from this worktree on a parallel slot alongside the existing standard-port stack.