legacy-preservation-router

Route legacy preservation questions to family-office leaf deliverables via dispatch table matching.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/terraleiloa/seren-skills --skill legacy-preservation-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legacy-preservation-router
Source: https://github.com/terraleiloa/seren-skills/tree/main/family-office/legacy-preservation-router
Command: npx skills add https://github.com/terraleiloa/seren-skills --skill legacy-preservation-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates delays and guesswork when an advisor asks a family office legacy preservation question without specifying which deliverable they need.

Core Features & Use Cases

  • Natural-language intent routing: Classifies the advisor’s ask and selects the best-matching leaf skill and artifact within the Legacy Preservation pillar.
  • Prompt-to-artifact dispatch: Uses an embedded dispatch table and mirrored DISPATCH.yml triggers to map common phrases to the correct memo/checklist/plan.
  • Confidence and ambiguity handling: Requests confirmation when the match confidence is borderline and proposes a two-leaf sequence when an ask covers multiple deliverables.

Quick Start

Ask your AI assistant to classify the request and run the correct Legacy Preservation artifact, for example: "Draft an estate overview and recommend the trust structure to preserve assets for future generations."

Frequently Asked Questions about legacy-preservation-router

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

FAQPage Schema
How do I route natural-language estate planning questions to the correct family office deliverable?

Legacy preservation routing classifies natural-language estate planning questions using trigger phrases and a dispatch table to select the correct family office memo, checklist, or plan. It matches the advisor's intent to the appropriate leaf deliverable within the Legacy Preservation pillar.

What happens if my trust selection request covers multiple family office deliverables?

When a trust selection request spans multiple deliverables, the router detects the ambiguity and proposes a two-leaf sequence. It applies confidence-bound selection to determine if confirmation is needed before dispatching the combined workflow.

How does intent routing handle healthcare proxy and living will requests without a specified memo format?

Intent routing for healthcare proxy and living will requests uses deterministic prompt classification to map the ask to the correct artifact. If the confidence match is borderline, it requests confirmation before generating the memo.

Does the legacy preservation router support private trust company formation and succession planning?

Yes, the router supports private trust company formation and succession planning scenarios. It maps governance, philanthropy, and risk-related trigger phrases to the appropriate dispatch table entries to generate the correct deliverable.

What is the fallback behavior when a family office legacy question has no built-in match?

When no built-in match exists in the dispatch table, the router applies fallback handling to prevent incorrect memo generation. It avoids forcing a low-confidence classification and manages unmatched legacy preservation queries safely.

Can I use this router for will drafting and estate overview generation in a single request?

Yes, you can request will drafting and estate overview generation together. The router evaluates the combined ask, determines if multiple deliverables are required, and proposes the correct two-leaf sequence to fulfill the request.