What problem does it solve?
Teams using Spec Kitty need a consistent way to configure, bind, and diagnose tracker integrations without guessing which sync mode or routing path is active, especially when hosted sync and local CLI behavior diverge.
Core Features & Use Cases
- Tracker Status Inspection: Reviews tracker status and service discovery output to confirm the active project and tracker binding.
- Hosted Sync Routing: Enables hosted sync only when the workflow requires it, and routes auth failures to spk-team-auth and transport or offline replay failures to spk-team-sync.
- Local Dev Configuration: Guides opting into hosted mode with SPEC_KITTY_ENABLE_SAAS_SYNC=1 via .kittify/.kitty.env or ${SPEC_KITTY_HOME}/.kitty.env, verified with spec-kitty doctor env-file.
- Use Case: A developer testing tracker sync locally writes the env flag into the repo-scoped .kitty.env file, runs spec-kitty doctor env-file to confirm the active tier, and diagnoses a binding mismatch before pushing work.
Quick Start
Ask the assistant to check the current Spec Kitty tracker status and confirm which project and tracker binding are active.