spk-integrate-orchestrator-api

Integrates external systems with the Spec Kitty orchestrator-api using documented contracts and state-machine rules.

1.6k|156|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-integrate-orchestrator-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spk-integrate-orchestrator-api
Source: https://github.com/Priivacy-ai/spec-kitty/tree/main/src/charter/offering/skills/spk-integrate-orchestrator-api
Command: npx skills add https://github.com/Priivacy-ai/spec-kitty --skill spk-integrate-orchestrator-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External agents, scripts, CI jobs, and services often need to drive Spec Kitty workflows, but scraping local artifacts or bypassing gates breaks state-machine invariants and host boundaries. This Skill defines the correct integration path through the orchestrator-api.

Core Features & Use Cases

  • Host Boundary Enforcement: Identifies the external caller and restricts operations to the allowed host boundary.
  • Contract-Based Integration: Uses documented API contracts instead of scraping local repository artifacts.
  • State-Machine Safety: Preserves workflow invariants with no implicit success and no skipped review or acceptance gates.
  • Use Case: A CI pipeline needs to advance a Spec Kitty mission after tests pass; the Skill routes that advancement through orchestrator-api runtime decisions rather than mutating local state directly.

Quick Start

Ask the agent to integrate your CI job with the Spec Kitty orchestrator-api so mission advancement follows the documented API contracts and state-machine gates.

Frequently Asked Questions about spk-integrate-orchestrator-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate an external service with Spec Kitty?

Integrate through the Spec Kitty orchestrator-api using its documented API contracts rather than reading or modifying local artifacts directly. Identify the caller, respect the allowed host boundary, and route mission advancement through runtime decisions.

How to trigger Spec Kitty workflow advancement from a CI job?

A CI job should call the orchestrator-api and let runtime decisions advance the mission. The integration must not declare implicit success or skip review and acceptance gates defined by the workflow state machine.

Can I read Spec Kitty state by scraping local repository artifacts?

No, the Skill explicitly directs integrators to use documented API contracts instead of scraping local artifacts. Direct artifact access bypasses host boundaries and can violate state-machine invariants.

What are the limitations of the orchestrator-api integration approach?

The integration cannot bypass workflow gates, assume implicit success, or operate outside the identified host boundary. Detailed API contracts and host-boundary rules are delegated to the legacy spec-kitty-orchestrator-api-operator alias when available.