review-plans

Audit layered planning documents against the codebase to resolve drift.

4|2|Updated Jan 29, 2026

Search Tags:#planning #codebase #drift #prd #tech-plan #prfaq

Ready to run

npx skills add https://github.com/blake-simpson/belmont --skill review-plans

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-plans
Source: https://github.com/blake-simpson/belmont/tree/main/plugin/skills/review-plans
Command: npx skills add https://github.com/blake-simpson/belmont --skill review-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and ensure planning documents stay aligned with the codebase, reducing drift and conflict between strategy and implementation.

Core Features & Use Cases

Interactive multi-layer planning audit across PR/FAQ, master PRD, master Tech Plan, feature PRDs, and PROGRESS.
Detect drift, resolve conflicts, and ensure plans reflect reality with guided edits to planning docs.
Create actionable follow-ups and track alignment through notes and progress updates.

Quick Start

Run belmont:review-plans to start an interactive audit of your planning documents and resolve drift with user-guided edits.

Frequently Asked Questions about review-plans

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

FAQPage Schema

How do I detect drift between planning documents and my codebase?▼

To resolve drift between PRDs and code, this Skill performs an interactive multi-layer audit across PR/FAQ, master Tech Plans, and feature PRDs, guiding user-driven fixes through non-destructive edits to planning documents. It ensures plans reflect reality while creating actionable follow-ups.

What is the best way to audit PR/FAQ and tech plan alignment interactively?▼

The best way to audit PR/FAQ and tech plan alignment is running an interactive multi-layer review that reads .belmont files and feature-level PROGRESS documents. This process flags conflicts and orphaned features, guiding non-destructive edits to keep strategy and implementation synchronized.

Can I use review-plans to fix orphaned features in my PRDs without breaking the code?▼

Yes, you can fix orphaned features safely because the review-plans process enforces non-destructive edits to planning documents through guided prompts. It identifies orphaned features during the audit and walks users through resolving the drift without altering the codebase directly.

Do I need .belmont planning files to audit planning drift?▼

Yes, .belmont planning files are required as the review-plans Skill reads these files alongside feature-level PRDs and PROGRESS documents to perform the drift audit. These artifacts provide the baseline planning context needed to identify gaps and conflicts with the codebase.

Why does my planning document conflict with the current codebase implementation?▼

Planning documents conflict with the codebase when implementation drifts from the original PRDs or Tech Plans over time. The review-plans Skill identifies these exact drifts and conflicts by interactively comparing your layered planning artifacts against the actual code, guiding you to resolve discrepancies.