change-impact-reconciliation

Review downstream effects of repository changes and classify impacts without applying updates.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/rickvang/Persona-Library --skill change-impact-reconciliation-rickvang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-impact-reconciliation
Source: https://github.com/rickvang/Persona-Library/tree/main/.agents/skills/change-impact-reconciliation
Command: npx skills add https://github.com/rickvang/Persona-Library --skill change-impact-reconciliation-rickvang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a source record, decision, prototype, or generated artifact changes in a content repository, it is hard to know which dependent records, pages, and outputs are affected, and silent or unrelated updates can corrupt the source of truth. ## Core Features & Use Cases - Bounded Dependency Review: Enumerates direct and indirect dependents from explicit typed relationships and declared provenance in authored content modules, with stated search limits. - Impact Classification: Labels each dependent as Confirms, Extends, Qualifies, Contradicts, Invalidates, or Unrelated, with evidence and confidence. - Structured Reconciliation Report: Returns status, scope checked, required updates, optional follow-ups, blockers, and the smallest next action, while remaining strictly read-only. - Use Case: After updating a Persona record, run this skill to check affected Operating Packs, generated pages, and decision records, then receive a report separating required fixes from unchanged items. ## Quick Start Use the change-impact-reconciliation skill to review the downstream effects of this record change without making any durable updates.

Frequently Asked Questions about change-impact-reconciliation

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

FAQPage Schema
How do I review the downstream impact of a content record change?▼

Activate this skill after a material change and provide the change event, source authority, and scope. It loads explicit relationships and provenance from the authored content modules, enumerates direct and indirect dependents, and returns a classified reconciliation report.

What impact classifications does a reconciliation review produce?▼

Each checked dependent is classified as Confirms, Extends, Qualifies, Contradicts, Invalidates, or Unrelated, with evidence and confidence recorded. If evidence cannot distinguish classes, the classification is marked uncertain rather than guessed.

Can this skill apply the required updates it finds?▼

No. The skill is read-only by default: it inspects files and runs read-only checks but never edits content, creates records, publishes, or runs build commands that write generated output. Required updates are reported for an authorized owner to execute.

When should I not use a change impact reconciliation pass?▼

Skip it for ordinary read-only questions and isolated prototype exploration where no impact review is requested. The initiating domain workflow owns research or mutation; this skill only checks consequences of an actual change event.

What happens if the initiating workflow contract is missing metadata?▼

The skill falls back to the safest read-only behavior and reports the contract gap. Missing change_mode, change_domain, or reconciliation metadata is treated as a blocker to report, never as permission to proceed.