persona-reconciliation

Review Persona-specific effects of a changed source and return a scoped update set.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a source claim, Skill, workflow, activity, Tool requirement, or capability changes, Persona records can silently drift out of date. This Skill performs a scoped, read-only impact review of only the affected Persona fields and returns a bounded update set without rewriting unrelated data. ## Core Features & Use Cases - Scoped Impact Classification: Classifies each affected claim or field as confirms, extends, qualifies, contradicts, invalidates, or unrelated, with evidence and confidence. - Field-Impact Contract: Maps changed inputs to exact Persona record properties using an impact matrix and revision contract as reasoning aids, not edit permissions. - Bounded Output Report: Separates required updates, optional follow-ups, and checked-but-unchanged items, then hands off at most once to the universal change-impact-reconciliation pass. - Use Case: After a Tool requirement changes for a research workflow, activate this adapter to inspect only the affected Personas' workflows, Skill applications, and Tool requirements, then receive a compact reconciliation report before any authorized write. ## Quick Start Use $persona-reconciliation to review this Persona change and return a bounded update set.

Frequently Asked Questions about persona-reconciliation

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

FAQPage Schema
How do I review the impact of a changed claim on Persona records?▼

Activate the adapter after a material change to a Persona or a capability it applies. It loads only the affected Persona records, classifies each impacted field with evidence, and returns a bounded update set before any write occurs.

What does the persona-reconciliation skill actually change in the data?▼

Nothing by default. It is a scoped, read-only adapter that prepares and validates an update set; only an initiating workflow with explicit authorization and a named target may apply the identified changes.

When should I not use Persona impact reconciliation?▼

Do not activate it for repository-wide impact reviews, pure research briefs with no changed Persona scope, canonical Tool catalog maintenance, or unpromoted prototypes. Those belong to the initiating workflow or the universal reconciliation pass.

How are changed inputs classified during reconciliation?▼

Each affected claim, field, or relationship is classified as confirms, extends, qualifies, contradicts, invalidates, or unrelated, based on evidence. Uncertain classifications are preserved explicitly rather than resolved by compromise.

Does the adapter run the universal change-impact-reconciliation pass?▼

Yes, but at most once and only after the Persona-specific adapter completes, when the initiating contract requires downstream review. The universal pass must never call this adapter again for the same event.

What happens if required records or metadata are missing?▼

The adapter returns a blocked or partial read-only report describing the exact gap instead of broadening the review by guesswork. Missing contract metadata means safest read-only behavior, never implicit permission.