Skills Router

Routes techpacks.routeSkills(phase, component_type) requests to the appropriate fullstack-typescript skills. Core never loads tech pack skills directly — it invokes this router, which returns the skill paths to load.

Input

Invoked by the techpacks gateway with a structured context block:

phase: <phase>
component_type: <optional>
component_name: <optional>
agent: <optional>

Validated against skills-router-context.schema.json.

Component Standards Table

Maps component_type to the standards skills that apply during implementation and verification phases.

Skill Paths

Phase Skills Table

Maps the lifecycle phase to the skill(s) to load.

Phase Resolution Rules

1. component-discovery — Always loads the component-discovery skill. No component_type required.

2. project-scaffolding — Always loads the scaffolding skill. No component_type required.

3. plan-generation — Always loads the planning-standards skill. No component_type required.

4. implementation — Requires component_type. Look up the Component Standards Table and return the listed skills. If component_type is missing, return an error.

5. testing — Always loads integration-testing-standards and e2e-testing-standards. If a specific component_type is provided and it is integration-testing or e2e-testing, load only that one.

6. verification — Requires component_type. Look up the Component Standards Table and return all listed skills. The verifier uses these to check the implementation against standards.

Agent Context Table

Maps component_type to the agent declared in techpack.yaml that should be loaded via techpacks.loadAgent.

Loading Instructions

When the techpacks gateway invokes this router:

1. Read the context block — extract phase, component_type, component_name, and agent.

2. Resolve skill list — use the Phase Skills Table to determine which skills to load. For phases that reference the Component Standards Table (implementation, verification), look up the component_type entry.

3. Return skill paths — for each resolved skill name, map it to the relative path from the Skill Paths table above. The techpacks gateway will call techpacks.resolvePath to turn these into absolute paths and then techpacks.loadSkill to load each one.

4. Agent resolution — if the context includes a component_type and the phase is implementation or verification, also return the agent reference from the Agent Context Table. The techpacks gateway loads the agent via techpacks.loadAgent, which spawns a Task subagent with the resolved skills composed into its prompt.

Example

Request:

phase: implementation
component_type: server
component_name: main-server

Response:

skills:
  - skills/components/backend/backend-standards/SKILL.md
  - skills/typescript-standards/SKILL.md
agent:
  name: backend-dev
  path: agents/backend-dev.md