co-plan

Facilitate collaborative code change planning with Claude and Gemini CLI.

Updated May 10, 2026
One-click install
npx skills add https://github.com/PatientVibes/agent-skills --skill co-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: co-plan
Source: https://github.com/PatientVibes/agent-skills/tree/main/plugins/co-plan/skills/co-plan
Command: npx skills add https://github.com/PatientVibes/agent-skills --skill co-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gemini-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables collaborative planning with Gemini CLI, providing a second-opinion for complex changes, reducing the risk of missed dependencies and incorrect approaches.

Core Features & Use Cases

  • Collaborative Planning Loop: Claude drafts a plan, Gemini critiques it, and Claude revises, repeating until convergence.
  • Gemini's Review: Gemini reviews the plan, checking for missed dependencies, incorrect ordering, codebase constraints, risks, and verification.
  • Iterative Process: Use this skill for architectural decisions, multi-step migrations, and complex plans where a second opinion is valuable.

Quick Start

To start planning, type /co-plan.

Frequently Asked Questions about co-plan

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

FAQPage Schema
How do I get a second opinion on a codebase analysis for complex architectural changes?

You can use collaborative planning to get a second opinion by having Claude draft a plan and Gemini critique it. This iterative loop identifies missed dependencies, incorrect ordering, and codebase constraints to reduce risks in complex architectural changes.

Do I need Gemini CLI installed to review code change plans for missed dependencies?

Yes, you need the Gemini CLI installed, authenticated, and available on your system PATH. It is required to execute the collaborative planning loop and provide iterative reviews of your code change plans.

What is the best way to validate multi-step migration plans for codebase constraints and risks?

The best way is an iterative planning process where an initial draft is reviewed for missed dependencies, incorrect ordering, and risks. This loop repeats with feedback for improvement until the plan converges, ensuring complex migrations are thoroughly validated.

Can I use collaborative planning for multi-step migrations where verifying dependencies is critical?

Yes, collaborative planning is designed for multi-step migrations and complex plans. The review process specifically checks for missed dependencies, codebase constraints, and verification steps, providing iterative feedback until the plan is robust.

How does the iterative feedback loop work when developing complex code change plans?

The iterative feedback loop works by having Claude draft a plan and Gemini critique it. This cycle of drafting, reviewing for risks and constraints, and revising repeats until convergence, ensuring the final plan is solid.

What are the limitations of using an AI collaborative planning loop for codebase analysis?

The primary limitation is the dependency on Gemini CLI being installed and authenticated on your PATH. Additionally, the process requires multiple iterations to reach convergence, which may not be efficient for trivial or simple code modifications.