What kind of documentation does it generate?

It creates a MULTIREPO-FLOW.md diagram for the overall architecture and specific implementation plans (PLAN-repo.md) for each repository involved.

Can it help with deployment ordering?

Yes, part of the planning phase includes determining the implementation and deployment order, ensuring producer endpoints are ready before consumer services attempt to use them.

How does this skill handle different programming languages?

It utilizes Language Server Protocol (LSP) chains to analyze codebases regardless of the language, identifying symbols, definitions, and references to map out cross-repo integrations.

Do I need to manually specify which repo is the backend?

No, the skill analyzes the codebase roles automatically based on which repository produces or consumes specific endpoints and services during the indexing phase.

Multi-Repository Planner

Name: Multi-Repository Planner
Author: DieGopherLT

byDieGopherLT

•

API Development

Coordinates feature implementation across multiple codebases by analyzing API contracts and generating synchronized development plans.

About

The multirepo-plan skill streamlines the complex process of planning features that span multiple repositories, such as backend and frontend pairs. It uses an LSP-driven approach to identify integration points, maps out data flow and API contracts, and generates parallel implementation plans for each codebase. By automating the discovery of dependencies and creating a central documentation file, it ensures that developers maintain architectural consistency and proper implementation ordering across their entire tech stack, reducing integration friction and deployment risks.

Key Features

Generation of synchronized implementation plans for parallel development
1 GitHub stars
Deep-dive analysis of request/response schemas and internal dependencies
Automated integration mapping and role determination for different services
Automated multi-repo LSP indexing to identify producers and consumers
Visual flow documentation using Mermaid-based architecture templates

Use Cases

Coordinating a new API endpoint rollout between a backend service and a frontend client
Planning features for projects requiring synchronized mobile and web updates
Refactoring shared data structures or protocols used across microservices

About

Key Features

Generation of synchronized implementation plans for parallel development
1 GitHub stars
Deep-dive analysis of request/response schemas and internal dependencies
Automated integration mapping and role determination for different services
Automated multi-repo LSP indexing to identify producers and consumers
Visual flow documentation using Mermaid-based architecture templates

Use Cases

Coordinating a new API endpoint rollout between a backend service and a frontend client
Planning features for projects requiring synchronized mobile and web updates
Refactoring shared data structures or protocols used across microservices