القائمة
Routes core skill requests to fullstack-typescript component standards and lifecycle skills.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Orchestrates SDD project initialization — version detection, environment verification, scaffolding, and git setup.
Manage project settings in sdd/sdd-settings.yaml including component settings that drive scaffolding.
Single gateway for all core↔tech-pack interactions. Reads manifests, resolves paths, loads skills/agents, routes commands.
Manage tasks and plans using the .tasks/ directory.
Standards for authoring SDD plugin agents — frontmatter, self-containment, skill references, and no-user-interaction rules.
Standards for authoring SDD plugin commands — frontmatter, user interaction, skill/agent invocation, CLI integration, and output formatting.
| name | skills-router |
| description | Routes core skill requests to fullstack-typescript component standards and lifecycle skills. |
| user-invocable | false |
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.
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.
Maps component_type to the standards skills that apply during implementation and verification phases.
| component_type | Standards Skills |
|---|---|
server | backend-standards, typescript-standards |
webapp | frontend-standards, typescript-standards |
database | database-standards |
contract | contract-standards, typescript-standards |
helm | helm-standards |
config | config-standards |
cicd | cicd-standards |
integration-testing | integration-testing-standards |
e2e-testing | e2e-testing-standards |
| Skill Name | Path (relative to tech pack root) |
|---|---|
backend-standards | skills/components/backend/backend-standards/SKILL.md |
frontend-standards | skills/components/frontend/frontend-standards/SKILL.md |
database-standards | skills/components/database/database-standards/SKILL.md |
contract-standards | skills/components/contract/contract-standards/SKILL.md |
helm-standards | skills/components/helm/helm-standards/SKILL.md |
config-standards | skills/components/config/config-standards/SKILL.md |
cicd-standards | skills/components/cicd/cicd-standards/SKILL.md |
integration-testing-standards | skills/components/integration-testing/integration-testing-standards/SKILL.md |
e2e-testing-standards | skills/components/e2e-testing/e2e-testing-standards/SKILL.md |
typescript-standards | skills/typescript-standards/SKILL.md |
unit-testing | skills/unit-testing/SKILL.md |
component-discovery | skills/component-discovery/SKILL.md |
scaffolding | skills/scaffolding/SKILL.md |
planning-standards | skills/planning-standards/SKILL.md |
Maps the lifecycle phase to the skill(s) to load.
| Phase | Skills | Notes |
|---|---|---|
component-discovery | component-discovery | Discovers component types and instances in the project |
project-scaffolding | scaffolding | Scaffolding conventions for this tech pack |
plan-generation | planning-standards | Planning conventions and output format |
implementation | (from Component Standards Table) | Requires component_type in context |
testing | integration-testing-standards, e2e-testing-standards | Both loaded regardless of component type |
verification | (from Component Standards Table) | All standards for each component type involved |
component-discovery — Always loads the component-discovery skill. No component_type required.
project-scaffolding — Always loads the scaffolding skill. No component_type required.
plan-generation — Always loads the planning-standards skill. No component_type required.
implementation — Requires component_type. Look up the Component Standards Table and return the listed skills. If component_type is missing, return an error.
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.
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.
Maps component_type to the agent declared in techpack.yaml that should be loaded via techpacks.loadAgent.
| component_type | Agent Name | Agent Path |
|---|---|---|
server | backend-dev | agents/backend-dev.md |
webapp | frontend-dev | agents/frontend-dev.md |
database | backend-dev | agents/backend-dev.md |
contract | api-designer | agents/api-designer.md |
helm | devops | agents/devops.md |
config | backend-dev | agents/backend-dev.md |
cicd | devops | agents/devops.md |
integration-testing | tester | agents/tester.md |
e2e-testing | tester | agents/tester.md |
When the techpacks gateway invokes this router:
Read the context block — extract phase, component_type, component_name, and agent.
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.
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.
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.
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