skills.rest
Nealsch
NealschCOMMUNITY
Explore all skills by this author →
GitHub

Forge-Integration-Design

Designs system integration boundaries, communication flows, and data exchange definitions before implementation.

Updated Jul 18, 2026
Search Tags:#api design#system architecture#data exchange#failure handling#system boundaries#integration design#communication flows
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-integration-design-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Integration-Design
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/02-Architecture/Forge-Integration-Design
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-integration-design-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Systems that exchange data without a documented integration design end up with unclear ownership, fragile coupling, and unhandled failure scenarios. This Skill structures the design of how components, systems, and external services communicate before any code is written. ## Core Features & Use Cases - Boundary Definition: Identifies system interaction points, ownership areas, and integration boundaries between internal components and external services. - Communication & Data Exchange Design: Documents communication patterns (request/response, event-based, asynchronous, scheduled), data ownership, transformation, and validation expectations. - Failure & Risk Analysis: Captures failure handling, retry behavior, dependency risks, and open questions using the Integration-Design template. - Use Case: When adding a third-party payment service to an application, use this Skill to map interaction points, define request/response contracts, document failure recovery, and produce an integration design document for the implementation team. ## Quick Start Use the Forge-Integration-Design skill to design how our ordering service integrates with the external payment gateway and produce an integration design document.

Frequently Asked Questions about Forge-Integration-Design

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

FAQPage Schema
How do I design integrations between systems before writing code?▼

Follow a six-step procedure: identify integration requirements, define system boundaries, design information exchange, define interaction behavior, evaluate integration risks, and document the approach. Capture results in an integration design template covering communication flows and failure handling.

What should an integration design document include?▼

An integration design document should include an integration overview, system interaction map, communication flows, data exchange definitions, integration boundaries, failure handling considerations, dependencies, and open questions.

When should I not create an integration design?▼

Skip integration design when no system interaction exists, when creating a simple internal function, when implementation details are already established, or during routine coding tasks. It is meant for cross-boundary communication, not single-component work.

Does integration design cover API implementation?▼

No. Integration design defines boundaries, communication patterns, and data exchange expectations, but it does not implement APIs, write integration code, or configure infrastructure. API contracts are handled separately through API specification work.

How does integration design relate to solution architecture?▼

Solution architecture defines the broader system structure first, and integration design builds on it by detailing how the identified components and external systems interact. Data modelling supplies the information structures exchanged between systems.

Related Skills

Explore More Software Engineering Skills→
ethan-rioethan-rio

html-architecture-diagrams

Generate self-contained HTML architecture diagrams with inline SVG visuals.

Community
Advanced
osovvosovv
11

vv-plan

Generate structured implementation plans from approved spec.xml files.

Community
Advanced
GeneralJerelGeneralJerel
6

create-threat-model

Perform STRIDE threat modeling on architecture documents and generate prioritized mitigation files.

Community
Advanced
ArtRivArtRiv

gsd-quick

Execute small ad-hoc tasks with atomic commits and STATE.md tracking.

Community
Intermediate