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.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
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.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
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.
About this listing
Category
Engineering
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.