plot-reconcile

Name: plot-reconcile
Availability: InStock
Author: plot

Identify and report Plot workflow drift and branch inconsistencies.

2|3|Updated Mar 13, 2026

Search Tags:#git #plot #workflow management #reconciliation #branch hygiene

Ready to run

npx skills add https://github.com/plot-pm/plot --skill plot-reconcile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plot-reconcile
Source: https://github.com/plot-pm/plot/tree/main/skills/plot-reconcile
Command: npx skills add https://github.com/plot-pm/plot --skill plot-reconcile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, gh, bb, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and reports on drift and inconsistencies in the Plot workflow, ensuring the integrity of the Git-based planning process.

Core Features & Use Cases

Branch Hygiene: Identifies and reports on plan phase drift, merged-but-not-delivered plans, and stale branches.
Read-Only Scanning: Performs a read-only scan without making any changes, allowing for manual decision-making.
Forge Integration: Integrates with GitHub and Bitbucket for precise PR state enumeration.
Configurable: Allows configuration of plan directories, branch prefixes, and main branch names.

Quick Start

Run the plot-reconcile skill to scan for branch hygiene issues in your Plot workflow.

Frequently Asked Questions about plot-reconcile

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

FAQPage Schema

How do I identify stale branches and workflow drift in my Git planning process?▼

Branch hygiene and workflow drift are identified by scanning Git repositories to detect plan phase mismatches, merged-but-not-delivered plans, and stale branches. This read-only process highlights inconsistencies for manual reconciliation without making changes.

How do I check for merged-but-not-delivered plans in my Git workflow?▼

Checking for merged-but-not-delivered plans involves scanning your workflow to compare merged branches against the active plan directory. This read-only reconciliation identifies plans that were merged but remain marked as incomplete or undelivered in your tracking system.

Does this branch reconciliation tool work with both GitHub and Bitbucket?▼

Yes, branch reconciliation works with both GitHub and Bitbucket. It uses the gh and bb CLI tools to fetch precise PR state enumeration, ensuring accurate detection of branch hygiene issues across both forge platforms during the scan.

Do I need jq and gh installed to scan for Plot workflow inconsistencies?▼

You need git and jq installed to perform the scan for Plot workflow inconsistencies. The gh or bb CLI tools are optional but required for enhanced PR precision and accurate state enumeration when integrating with GitHub or Bitbucket.

What is the best way to find plan phase mismatches without modifying my branches?▼

The best way to find plan phase mismatches without modifying branches is to perform a read-only scan of your workflow. This identifies drift and inconsistencies in your planning process and generates a report for manual decision-making.

Can I configure branch prefixes and main branch names for my workflow reconciliation scan?▼

Yes, you can configure plan directories, branch prefixes, and main branch names for your workflow reconciliation scan. This allows the tool to accurately match your specific Git workflow structure when identifying drift and stale branches.