orchestrator: Skill for Claude Code

Integration Authoring

Create, update, or extend integration manifest packages in the companion orchestrator-integrations repository.

Repository Layout

<org-root>/
├── orchestrator/                  # Main project (this repo)
│   ├── crates/                    # Core engine code
│   ├── docs/showcases/            # Execution plans
│   └── .claude/skills/            # Skills (including this one)
└── orchestrator-integrations/     # Integration packages (companion repo)
    ├── slack/
    ├── github/
    ├── line/
    └── <new-integration>/

When to Use This Skill

• User asks to "add a Jira integration", "create a Discord webhook trigger", etc.
• User asks to update an existing integration (e.g., "add a new GitHub trigger for releases")
• User asks to create a CRD-based integration extension

Workflow

1. Determine Scope

• New integration: Create a new directory in orchestrator-integrations/
• Update existing: Modify files in the existing integration directory
• CRD extension: Create CRD manifest + associated triggers (FR-083 pattern)

2. Create/Update Integration Package

Work in the companion repo at ../orchestrator-integrations/ (relative to this project root).

Each integration package MUST follow this structure:

<platform>/
├── secrets-template.yaml     # SecretStore with placeholder values
├── trigger-<event>.yaml      # One Trigger per event type
├── step-template-<action>.yaml  # Optional StepTemplate for payload handling
└── README.md                 # Platform setup guide

3. Manifest Standards

SecretStore template:

apiVersion: orchestrator.dev/v2
kind: SecretStore
metadata:
  name: <platform>-secret
spec:
  data:
    signing_secret: "<your-<platform>-secret>"

Webhook Trigger:

apiVersion: orchestrator.dev/v2
kind: Trigger
metadata:
  name: <platform>-<event>
spec:
  event:
    source: webhook
    webhook:
      secret:
        fromRef: <platform>-secret
      signatureHeader: <platform-specific-header>
    filter:
      condition: "<CEL expression for event filtering>"
  action:
    workflow: handle-<platform>-<event>
    workspace: default