template-reconciliation

Review downstream impacts after Template lifecycle changes in the Persona Library.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Template in the Persona Library is created, changed, promoted, deprecated, relocated, or restructured, dependent records such as Personas, Skills, Operating Packs, Playbooks, catalog entries, and generated Site output can silently drift out of sync. This Skill performs a read-only reconciliation pass that detects those downstream effects before they become stale links or broken publication chains. ## Core Features & Use Cases - Dependency Impact Review: Loads explicit relationships and provenance from a changed Template to Personas, Skills, workflows, Operating Packs, Playbooks, Tools, Docs, and dependent Templates. - Publication Chain Verification: Confirms the full reusable-publication chain, including canonical source resolution, catalog record match, illustrative viewer representation, generated data freshness, and Templates-tab visibility. - Classified Impact Report: Classifies each dependent as confirms, extends, qualifies, contradicts, invalidates, or unrelated, with evidence and confidence, then separates required updates from optional follow-ups. - Use Case: After promoting a Template to reusable status, run this Skill to verify the catalog record, viewer representation, and generated Site output all reflect the intended identity and lifecycle state. ## Quick Start Review the downstream effects of the recent Template promotion and report any impacted Personas, Skills, catalog records, and generated Site output.

Frequently Asked Questions about template-reconciliation

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

FAQPage Schema
How do I check what breaks after changing a Template?▼

Run a reconciliation pass that loads the Template's explicit relationships and provenance to Personas, Skills, workflows, Operating Packs, Playbooks, and Docs. Each dependent is classified as confirms, extends, qualifies, contradicts, invalidates, or unrelated, with evidence and confidence.

How to verify a Template publication is complete?▼

Verify the full publication chain: the canonical source resolves, the catalog record exists and matches, a local illustrative viewer representation exists with synthetic content, generated Site data is fresh, and the Template appears in the Templates tab and focused viewer with the intended lifecycle state.

Does template reconciliation modify dependent records?▼

No, the reconciliation pass is strictly read-only. It does not mutate Personas, Skills, workflows, Operating Packs, Playbooks, Tools, Docs, catalog records, or generated files; it only reports required updates and optional follow-ups.

What does a missing catalog record mean during Template review?▼

A missing catalog record, missing viewer representation, stale generated data, or absent Templates-tab state is treated as an incomplete publication rather than a successful lifecycle completion. Planned Templates may legitimately lack a viewer until publication.

When should template reconciliation not be used?▼

It is not a substitute for applying updates, since it never performs downstream mutations. It also does not prove runtime access, cloning, or execution of an external Template source; it only verifies catalog and Site integration evidence.