Priivacy-ai spk-team-sync
Use this skill when a command touches spec-kitty tracker sync pull /
sync push / sync run (local providers), tracker bind / status
(hosted SaaS binding), or otherwise SaaS-backed mission data. There is no
standalone sync daemon, offline queue, or sync diagnostics command — that
transport was removed (issue #5); sync is a tracker capability now.
Flow
- Determine whether the user needs local-provider sync (
sync pull/sync push/sync run) or hosted SaaS binding/status. - Run
spec-kitty tracker statusbefore repair commands. - Preserve machine-readable output when the user requested JSON.
- For tracker-bound sync, route to
spk-team-tracker. - For auth failures, route to
spk-team-auth.
Local Dev Note
When testing tracker-backed sync flows from the CLI on this computer, hosted
mode is already on — the launch default (#3980) is enabled unless explicitly
opted out; SPEC_KITTY_ENABLE_SAAS_SYNC=0 is the opt-out. The flag is the
tracker-hosted rollout gate; it does not restore the removed standalone sync
daemon, offline queue, or diagnostics transport. To keep hosted mode off on
this machine, prefer writing SPEC_KITTY_ENABLE_SAAS_SYNC=0 once into
.kittify/.kitty.env (repo-scoped) or ${SPEC_KITTY_HOME}/.kitty.env
(machine-wide) over a per-shell export — a shell export disarms every project
that shell subsequently touches, not just the one you're testing. Run
spec-kitty doctor env-file to confirm which tier is active.