project-plan-reconciler

Reconciles project plans and roadmaps against actual repository implementation evidence.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/vmitsaras/Agent-Skills --skill project-plan-reconciler-vmitsaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-plan-reconciler
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/project-planning/project-plan-reconciler
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill project-plan-reconciler-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning documents like roadmaps, TODO files, and milestone trackers drift out of sync with the actual codebase as work progresses, leaving teams unsure what is truly finished, blocked, or obsolete. ## Core Features & Use Cases - Evidence-Based Status Verification: Assigns each planned item a status (complete, partial, blocked, stale, obsolete, unverified, undocumented) based on tests, source code, and integration evidence rather than checkboxes. - Plan Drift Detection: Identifies incorrect completion claims, stale items, conflicting planning documents, and undocumented implementation work. - Corrected Execution Sequence: Produces a prioritized list of three to seven next tasks with dependencies, acceptance criteria, and validation methods. - Use Case: After several weeks of incremental development, ask the agent to check your ROADMAP.md against the repository to learn which milestones are genuinely complete and what should be implemented next. ## Quick Start Ask the agent to reconcile the project roadmap with the current repository state and report what is actually finished and what to work on next.

Frequently Asked Questions about project-plan-reconciler

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

FAQPage Schema
How do I check if my project roadmap matches the actual code?▼

Run a plan reconciliation that compares each roadmap item against repository evidence such as tests, source code, exports, and configuration. Each item receives a verified status like complete, partial, blocked, or stale rather than relying on checkboxes.

How to find stale or outdated TODO items in a repository?▼

Extract planned items from TODO, ROADMAP, and milestone files, then verify each against implementation evidence. Items no longer matching the project direction are classified as stale or obsolete, while finished work missing from the plan is marked undocumented.

Can this skill update my planning documents automatically?▼

By default it returns review-only recommendations without editing files. When you explicitly request updates, it modifies the smallest authoritative set of planning documents, preserves formatting, and reports every file changed.

What happens when a project has no planning documents?▼

The skill reports that no authoritative plan was found and produces a concise implementation-state inventory instead. It recommends using a roadmap-generation skill to create the initial plan rather than inventing historical project intent.

When should I not use plan reconciliation?▼

Avoid it when no plan exists and you need a roadmap from scratch, when you only want a brief repository summary, or when the task is a code-quality, security, or release-readiness review better handled by specialized skills.