
Backend Integrate
- 6 repo stars
- Updated April 22, 2026
- sagar-rai/backend-integrate
Fetch a downstream service's context from a GitHub repo and execute a backend integration into your current service, with a plan run by parallel agents.
About
backend-integrate fetches a downstream service's context from a GitHub repo and executes a backend integration into your current service. It pulls relevant files via the gh CLI, asks clarifying questions, builds a plan, and runs it with parallel agents to wire services together.
- Fetches downstream service context via gh CLI
- Asks clarifying questions
- Creates and runs an integration plan
- Parallel-agent execution
Backend Integrate by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add sagar-rai/backend-integrate/plugin install backend-integrate@backend-integrateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 6 |
|---|---|
| Last updated | April 22, 2026 |
| Repository | sagar-rai/backend-integrate ↗ |
What it does
Fetch a downstream service's context from a GitHub repo and execute a backend integration into your current service, with a plan run by parallel agents.
README.md
Claude Code Plugin — backend-integrate
This directory contains the Claude Code plugin for backend-integrate. It is a complete, self-contained plugin that can be installed directly from this repo.
Install
# Add this repo as a marketplace (one-time)
/plugin marketplace add sagar-rai/backend-integrate
# Install the plugin
/plugin install backend-integrate@backend-integrate
Local development
claude --plugin-dir ./platforms/claude
Then reload after changes:
/reload-plugins
Plugin structure
platforms/claude/
├── .claude-plugin/
│ └── plugin.json ← Plugin manifest (v2.0.0)
├── skills/
│ └── backend-integrate/
│ └── SKILL.md ← Skill: /backend-integrate:backend-integrate
├── agents/
│ └── backend-integrate.md ← Orchestrator with inline A→B→C execution
└── README.md ← This file
How to invoke
Invoke the skill explicitly or just describe what you want:
/backend-integrate:backend-integrate
Or naturally:
Integrate the payment service from github.com/acme/payment-svc — use INTEGRATION.md for context
Execution tracks
After you approve the integration plan, the orchestrator works through three sequential tracks:
| Track | Starts when | Builds |
|---|---|---|
| A | Immediately after approval | Downstream HTTP/gRPC client + config struct + .env.example |
| B | After Track A completes | Service layer + dependency injection wiring |
| C | After Track B completes | Unit tests + integration tests + doc updates |
Shared prompts
All behavioral prompts live in prompts/ at the repo root and are shared between the Copilot and Claude plugins:
| File | Controls |
|---|---|
prompts/context_discovery.md |
How to fetch files from downstream repos via gh CLI |
prompts/integration_analysis.md |
How to synthesize fetched context |
prompts/clarification_guide.md |
7 required questions before any plan is generated |
prompts/fleet_decomposition.md |
How to split integration into parallel tracks |
Session cleanup
Temporary files are stored in ~/.agents/session/<uuid>/ and deleted automatically after context is loaded into memory. Nothing is written to your repo until you approve the plan.
Requirements
- Claude Code installed and authenticated
ghCLI installed and authenticated (gh auth login) — or let the agent install it for you