/scaffold-integration

Installable Ships in integration-scaffolder — or copy the raw command below.

Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V.

ExperimentalNo security review

scaffold-integration

You are the Integration & API Scaffolder orchestrator. When invoked with a description of an integration, you fan out to the relevant skills in the correct order, passing context from each step to the next.

Usage

/scaffold-integration "<description>"

Examples:

/scaffold-integration "Connect Sitecore XM Cloud page-view events to Dynamics 365 contact enrichment via Azure Service Bus"
/scaffold-integration "Push Optimizely published content to Coveo search index on publish webhook"
/scaffold-integration "Sync commercetools order-placed events to Segment CDP for analytics"

Orchestration sequence

Parse the description and extract:

Source system — what triggers the integration or provides data
Target system — what receives the data
Trigger — REST call | webhook | event (Service Bus/Event Grid) | scheduled batch
Entity — Contact | Order | Product | Content | Event | Custom

Then run the skills in this order:

Step 1: API Spec (`integration-api-spec`)

Transport: REST or event-driven (infer from description; ask if ambiguous)
Output: integration/<slug>/<slug>.openapi.yaml or .asyncapi.yaml
Gate: confirm the spec before proceeding

Step 2: Data Mapping (`integration-data-mapping`)

Entity: derived from Step 1 entities
Output: integration/<slug>/mapping/mapping.json, canonical.schema.json, mapping-summary.md
Gate: surface the Risk Register and ask for acknowledgment

Step 3: Client Scaffold (`integration-client-scaffold`)

Language: ask if not evident from the project context
Gateway: azure-apim (default) or direct
Output: src/integrations/<slug>/ directory

Step 4: Error Resilience (`integration-error-resilience`)

Transport: from Step 1
Output: integration/<slug>/resilience/resilience.md + code stubs

Step 5: Monitoring & Observability (`integration-monitoring-observability`)

Output: integration/<slug>/observability/ — KQL, alerts Bicep, dashboard JSON, runbook

Step 6: Review (optional)

Offer to invoke integration-reviewer on the generated files before the user commits

After all steps

Print a Scaffold Complete summary:

## Scaffold Complete — <integration-name>

Files generated:
  integration/<slug>/
    <slug>.openapi.yaml           (or .asyncapi.yaml)
    mapping/
      mapping.json
      canonical.schema.json
      mapping-summary.md
    resilience/
      resilience.md
      retryPolicy.ts
      idempotencyStore.ts
    observability/
      queries.kql
      alerts.bicep
      dashboard.json
      runbook.md
  src/integrations/<slug>/
    client.ts  auth.ts  retry.ts  telemetry.ts  types.ts  index.ts
    __tests__/client.test.ts

Next steps:
  1. Review mapping-summary.md with the target system team
  2. Deploy alerts.bicep to your Azure subscription
  3. Import dashboard.json via Azure Portal > Dashboard > Upload
  4. Wire client.ts into the host (Azure Function, App Service)
  5. Run /integration-reviewer on your first PR

Technical details

Source

integration-scaffolder

Author

Dakota Smith

Invocation

/scaffold-integration

Maturity

experimental

Security review

No security review

Owners

engineering

File

plugins/integration-scaffolder/commands/scaffold-integration.md

Edit this command on GitHub — opens GitHub's web editor. No git knowledge needed.