developer-skills-reflection-router

name	developer-skills-reflection-router
description	Router that maps developer-skills capabilities to equivalent Godot-aligned workflows/contracts in this skill library.
tier	operational
godot_version	4.6+
doc_anchors	["godot-docs/tutorials/best_practices/introduction_best_practices.rst","godot-docs/tutorials/editor/command_line_tutorial.rst"]
tags	["routing","interoperability","governance"]
depends_on	["godot-skills/godot-operational/documentation-version-governance-workflow/SKILL.md","godot-skills/godot-operational/dependency-impact-analysis-workflow/SKILL.md","godot-skills/godot-operational/security-review-workflow/SKILL.md","godot-skills/godot-operational/release-pipeline-validation-workflow/SKILL.md"]

Developer Skills Reflection Router

Use When

• Aligning generic developer workflow skills to Godot-specific execution.
• Verifying developer-skills coverage is represented in godot-skills.

Outcomes

• Cross-library capability mapping is explicit and reusable.
• Teams can route from generic workflows to Godot execution contracts quickly.
• Coverage gaps become visible for future skill additions.

Required Rules

• Map by capability domain, not by filename similarity.
• Prefer existing Godot skills before creating new mirrors.
• Keep mapping table updated when either library changes materially.
• Mark unresolved mappings as TODO with proposed destination.

Workflow

1. Classify developer skill by function (docs, security, delivery, architecture, coordination, etc.).
2. Select nearest Godot counterpart skill(s).
3. Record one-to-one or one-to-many mapping entry.
4. Create new Godot skill only when no suitable counterpart exists.
5. Re-run mapping review after major library updates.

Validation

• Every active developer skill category has at least one mapped Godot counterpart.
• Mapping file references valid godot-skills/**/SKILL.md paths.
• New developer capabilities trigger mapping review before release.

Failure Modes

• Mapping is stale and routes users to deprecated/nonexistent skills.
• New developer capabilities remain unmapped and unaccounted.
• Mapping relies on name matching rather than functional equivalence.

Local Doc Anchors

• godot-docs/tutorials/best_practices/introduction_best_practices.rst
• godot-docs/tutorials/editor/command_line_tutorial.rst

Related Skills

• godot-skills/godot-operational/documentation-version-governance-workflow/SKILL.md
• godot-skills/godot-operational/dependency-impact-analysis-workflow/SKILL.md
• godot-skills/godot-operational/security-review-workflow/SKILL.md
• godot-skills/godot-operational/release-pipeline-validation-workflow/SKILL.md

Variations

• Docs/reporting developer skills -> documentation-version-governance-workflow, qa-validation-loop, test-execution-contract
• Delivery/devops developer skills -> release-pipeline-validation-workflow, foundation-platform-export-compatibility, qa-validation-loop
• Security developer skills -> security-review-workflow, live-content-update-safety-contract, networking-reliability-reconciliation-contract
• Architecture/coordination developer skills -> dependency-impact-analysis-workflow, project-structure-audit, manager-signal-architecture-workflow
• App/frontend and interaction developer skills -> theme-asset-pack-integration-workflow, ui-localization-accessibility-workflow, input-action-routing-workflow