pm-reconcile

Legacy documentation reconciliation compares outdated product specifications against the existing codebase to create a consistent product knowledge base. It applies structured comparison workflows to track divergences across business rules, domain models, and features during product migrations or rebuilds.

Rebuilding an inherited product requires inspecting source documents and code structure to define reconciliation scope, then executing a layer-by-layer rebuild of domains, decision models, and features into clean live registers while tracking all divergences and decisions.

Yes, this reconciliation process applies directly to product migrations, team handovers, and rebuild initiatives where business rules, features, and domain models have diverged. It captures both implementation reality and business intent without losing source knowledge.

Source disposal verification performs final coverage checks to confirm that legacy knowledge has been fully captured into the new reconciled registers before documents are archived. This ensures no business intent or implementation reality is lost during the transition.

When business rules and domain models diverge, the Skill applies structured comparison workflows to track divergences and decisions layer by layer. It reconciles domains, decision models, and features into clean live registers to resolve inconsistencies between specifications and the running system.