Skip to content

suboss87/FDEOps / skills/integrate

integrate

Verified

Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.

FileKindSize
.fde-generated.jsonconfig1.1 KB
SKILL.mdskill md1.4 KB
agents/openai.yamlconfig207 B
references/build.mdmarkdown4.9 KB
references/debug.mdmarkdown3.6 KB
references/eval-pack.mdmarkdown6.2 KB
references/integrate.mdmarkdown4.7 KB
references/qa.mdmarkdown2.6 KB
references/review.mdmarkdown5.3 KB
references/ship.mdmarkdown10.6 KB
references/task-context.mdmarkdown6.6 KB
references/verification.mdmarkdown5.5 KB
---
name: integrate
description: Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.
---

# integrate

<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->

## Purpose

An integration with tested mapping and failure handling.

Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/integrate.md).

Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.

## Principles

- Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall