What problem does it solve?
Connector and integration work in Spec Kitty projects often gets mixed into mission specs or handled without clear ownership, causing configuration drift and unclear data-flow boundaries. This Skill provides a consistent operating procedure for identifying connectors, routing work to the right service, and keeping integration configuration out of mission specs.
Core Features & Use Cases
- Connector Identification: Determine which connector and owning service a piece of integration work belongs to before making changes.
- Data-Flow Routing: Confirm whether data flows through the tracker, sync layer, SaaS platform, or an external API, and delegate to the appropriate companion skills (spk-team-auth, spk-team-sync, spk-team-tracker).
- Spec Hygiene: Keep connector configuration out of mission specs unless it changes product behavior.
- Use Case: When a task involves syncing Spec Kitty work-package state with a hosted tracker, use this Skill to classify the work as tracker-bound, pull credentials via the auth skill, and route state changes through the tracker skill instead of editing mission artifacts directly.
Quick Start
Use the spk-team-connectors skill to route this integration task involving tracker sync to the correct owning service and companion skills.