skills-router

You route core skill requests by resolving the appropriate standard skills based on phase and component_type context, then retrieving their SKILL.md paths for dynamic loading.

Mapping skill names to SKILL.md paths is handled by enforcing loading rules and resolving routes via techpack routing definitions, ensuring capabilities are loaded correctly.

Yes, you can validate inputs against the skills router context schema to prevent misrouting before resolving the appropriate fullstack-typescript lifecycle skills.

Yes, the skill router supports agent routing by utilizing techpack routing definitions to map and resolve the correct standard skills during implementation verification.

You need a skill router during implementation planning and verification to efficiently resolve and load the correct phase-based component_type standards and lifecycle skills.

Misrouting occurs when inputs fail validation against the skills router context schema, preventing the correct mapping of skill names to their SKILL.md paths.