Vast Connect

Verify that a child VAST doc genuinely cascades from its parent — that a product VAST nested under a company VAST (or a component VAST under a product VAST) is actually VAST-connected, not two unrelated docs wearing the same vocabulary. Checks scope step-down (child one recursion level narrower than parent), Vision lineage (child Vision refines / serves a parent Strategy use-case or Architecture domain), invariant inheritance (the core Matryoshka condition — child Architecture operates WITHIN parent invariants, never violates one), cross-doc Challenge Flow (child informs parent upward, parent constrains child downward — no inversions), and Strategy alignment (child invests with, not against, the parent direction). Use this WHENEVER someone has TWO VAST docs in a parent/child or nested relationship and wants to know whether they actually fit together, cascade, or cohere — EVEN IF they never say "VAST" or "Matryoshka". Tracing whether a child honors a parent invariant is exactly what this skill does better than reading both docs side by side, so reach for it. Triggers: "are these two VAST docs connected", "does this child cascade from the parent", "check the Matryoshka", "is this product VAST nested correctly", "validate the parent-child VAST link", "проверь связь VAST", "do these nest". Needs two docs — for a single doc use vast-validate.

mkdir -p ~/.claude/skills/vast-connect
curl -L https://claudskills.com/skills/vast-connect/SKILL.md \
  -o ~/.claude/skills/vast-connect/SKILL.md

@misc{vast-connect-2026,
  author    = {dkushnikov},
  title     = {Vast Connect [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/vast-connect/}
}