forsvn

Classifies user asks and routes them to the appropriate FORSVN leaf.

14|Updated Apr 1, 2026

Search Tags:#context #routing #dispatch #workspace #resume #front-door #forsvn

Ready to run

npx skills add https://github.com/hungv47/meta-skills --skill forsvn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: forsvn
Source: https://github.com/hungv47/meta-skills/tree/main/skills/meta/forsvn
Command: npx skills add https://github.com/hungv47/meta-skills --skill forsvn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires shrinkage, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The Skill serves as the central dispatcher for the FORSVN agent stack, classifying user asks, loading canonical context, and routing to the appropriate leaf skill or resuming an in-flight initiative.

Core Features & Use Cases

Central front door that classifies vague requests and routes to the leaf skill.
Loads shared product context and prior session state to enable seamless resumptions.
Deterministic routing guided by routing.yaml, routing contracts, and domain chains.

Quick Start

Dispatch a vague ask or resume a session; the front door will classify, load context, and route to the correct leaf.

Frequently Asked Questions about forsvn

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

FAQPage Schema

How do I route vague user requests to the correct skill in a workspace?▼

Routing vague user requests requires a front-door dispatcher that classifies intent, loads shared project context, and applies deterministic routing rules to direct the ask to the correct leaf skill for execution.

What is intent classification and how does it work for agent dispatch?▼

Intent classification for agent dispatch analyzes vague user asks, ingests prior session state, and matches the request against routing contracts to deterministically select the single accountable downstream skill to execute.

How do I resume an in-flight session and load prior workspace context?▼

Resuming an in-flight session involves ingesting prior session state through a front-door orchestrator, which loads canonical project context and prepares the downstream leaf skill with the correct inputs to continue the initiative.

Can I use routing.yaml to enforce deterministic routing for multiple skills?▼

Yes, routing.yaml provides deterministic routing rules and domain chains that guide the front-door dispatcher, ensuring vague asks always resolve to the correct leaf skill rather than ambiguous outcomes.

Do I need the shrinkage dependency to use this front-door routing orchestrator?▼

Yes, the shrinkage dependency is required to support the front-door orchestrator's context loading and routing classification logic before dispatching to downstream leaf skills.

What are the limitations of using a central dispatcher for project routing?▼

A central dispatcher relies on predefined routing.yaml rules and prior session state, meaning routing fails if a user ask falls outside existing domain chains or if session context is missing or corrupted.