Backend Integrate
Pull downstream service files from a GitHub repo with gh CLI, plan the integration, and execute backend wiring with parallel agents.
Overview
backend-integrate is a plugin marketplace for the Build phase that fetches downstream GitHub service context and executes planned backend integrations with parallel agents.
What is this marketplace?
- backend-integrate v2.0.0 MIT plugin sourced from ./platforms/claude
- Uses GitHub gh CLI to fetch relevant files from a downstream repository
- Clarifying questions, integration plan, then execution with parallel agents
- Keywords include fleet, downstream-service, and service-integration
- Marketplace metadata describes fetch-then-integrate flow for current service
- 1 plugin listed; plugin version 2.0.0 MIT
- Repository URL https://github.com/sagar-rai/backend-integrate per catalog
- Documented flow: fetch via gh CLI → questions → plan → parallel agent execution
Community signal: 6 GitHub stars.
What problem does it solve?
Integrating against another team's service repo manually is slow, error-prone, and hard to keep consistent when gh and fleet boundaries are unclear.
Who is it for?
Solo backend devs wiring their API to an existing downstream GitHub service who already use gh locally.
Skip if: Frontend-only changes, greenfield apps with no external service contract, or teams without GitHub CLI access.
What do I get? / Deliverables
You get a reviewed integration plan and agent-driven changes in your service after downstream files are pulled and questions are resolved.
- Integration plan after clarifying questions on service boundaries
- Fetched downstream file context from the specified GitHub repository
- Agent-executed backend changes aligned to the approved plan
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Backend integration against external services is core Build work when your product must talk to another codebase or fleet API. integrations is the shelf because the plugin fetches remote service context and merges it into your current service—not greenfield UI or docs-only tasks.
How it compares
Repo-aware backend integration orchestrator, not a generic OpenAPI stub generator.
Common Questions / FAQ
Who is Backend Integrate for?
Indie and small-team backend developers integrating their current service with a downstream GitHub-hosted API or fleet component.
When should I use Backend Integrate?
Use it in Build when you need to ingest another repo's integration surface, plan the merge, and implement with agent assistance.
How do I add Backend Integrate to my agent?
Install the sagar-rai/Backend Integrate marketplace in Claude Code and enable the Backend Integrate plugin from ./platforms/claude.