multi_repo_plan

Multi-repo planning coordinates new features across separate repositories by facilitating contract-based communication, tracking dependencies, and managing incremental state updates to ensure consistent implementation.

Contract-based coordination passes API contracts and dependencies between multiple repositories, ensuring all parties are aligned on implementation details and project state updates throughout the planning process.

Implementation coordination for frontend and backend repositories starts by providing a structured Product Requirements Document path, which this Skill uses to manage planning and resolve dependencies.

Yes, managing incremental project state updates across multiple repositories is supported, allowing you to track progress and coordinate dependencies throughout the entire planning process.

Yes, structured input such as a Product Requirements Document is required for multi-repo dependency tracking to properly resolve dependencies and coordinate implementation across repositories.

The best way to align API contracts between separate repositories is using contract-based communication that passes dependencies between repos, ensuring all parties agree on implementation details.