Operate Spec Kitty team sync, hosted SaaS sync, offline queue, diagnostics, and recovery flows.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add Priivacy-ai/spec-kitty --skill spk-team-sync --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Spk Team Sync?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/priivacy-ai-spk-team-sync)More formats (shields.io, HTML) on the badges page.
---
name: spk-team-sync
description: "Operate Spec Kitty team sync, hosted SaaS sync, offline queue, diagnostics, and recovery flows."
---
# spk-team-sync
Use this skill when a command touches hosted sync, team state, offline queue,
sync diagnostics, or SaaS-backed mission data.
## Flow
1. Determine whether the user needs local state, hosted sync, or recovery.
2. Run sync status/diagnostics before repair commands.
3. Preserve machine-readable output when the user requested JSON.
4. For tracker-bound sync, route to `spk-team-tracker`.
5. For auth failures, route to `spk-team-auth`.
## Local Dev Note
When testing sync flows from the CLI on this computer, opt into hosted mode
with `SPEC_KITTY_ENABLE_SAAS_SYNC=1`. Prefer writing it once into
`.kittify/.kitty.env` (repo-scoped) or `${SPEC_KITTY_HOME}/.kitty.env`
(machine-wide) over a per-shell `export` — a shell export arms 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
