reconcile-plan

Reconcile structured planning state with code reality using diffs and artifacts.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/alexandersumer/config --skill reconcile-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reconcile-plan
Source: https://github.com/alexandersumer/config/tree/main/.agents/skills/reconcile-plan
Command: npx skills add https://github.com/alexandersumer/config --skill reconcile-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the reconciliation of structured planning state with code reality, ensuring that planning aligns with actual implementation.

Core Features & Use Cases

  • Code Reality Reconciliation: Updates planning state to match the current codebase.
  • Artifact Analysis: Reads and analyzes artifacts, branch/worktree diffs, and code.
  • Status Update: Preserves artifact structure and updates planning state in place.
  • Use Case: Ideal for software development teams to ensure that planning documents are up-to-date with the current codebase.

Quick Start

Reconcile the planning state with the current codebase using the 'reconcile-plan' skill.

Frequently Asked Questions about reconcile-plan

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

FAQPage Schema
How do I automate plan reconciliation with code reality in software development?

Plan reconciliation with code reality is automated by analyzing artifacts, branch diffs, and worktree states to update planning documents in place. This ensures your structured planning state aligns with the actual codebase without manual intervention.

What is code reality reconciliation and when do I need it?

Code reality reconciliation is the process of updating structured planning state to match the current codebase. You need it when planning documents drift from actual implementation, ensuring software development teams maintain accurate, up-to-date planning artifacts.

How do I update planning state based on branch and worktree diffs?

Updating planning state involves analyzing branch and worktree diffs alongside existing artifacts. The process reads code changes, preserves the original artifact structure, and updates planning state in place to reflect the current codebase accurately.

Does automated plan reconciliation preserve existing artifact structure?

Automated plan reconciliation preserves existing artifact structure while updating planning state in place. It reads and analyzes artifacts and code diffs, then modifies only the planning state to align with the current codebase without breaking document organization.

Can I use automated code reconciliation for software development team planning?

Automated code reconciliation is ideal for software development teams needing to ensure planning documents stay up-to-date with the current codebase. It requires no manual intervention, making it suitable for team workflows managing structured planning state.

What's the best way to keep planning documents aligned with the current codebase?

Keeping planning documents aligned with the current codebase is best achieved through automated reconciliation. This approach analyzes code artifacts and branch diffs to update planning state in place, eliminating manual synchronization effort and reducing documentation drift.