Pending: address remaining Azure skill routing gaps

[kvenkatrajan]

Summary

There are remaining failure modes not resolved by the trigger/description updates:

• Prepare executed deployment directly (azure-prepare runs azd/terraform commands instead of handing off to azure-validate/azure-deploy). Needs enforcement or guardrails.
• Non-deployable app detected (e.g., Aspire samples with .ExcludeFromManifest()), currently handled as a failure; define expected behavior (skip/xfail or pick deployable sample).
• Routing misses that still bypass skills in some prompts need additional investigation beyond trigger text changes.

Evidence

Run: https://github.com/microsoft/GitHub-Copilot-for-Azure/actions/runs/22603076174

Diagnostics (Overall Result + Skills Missed)

Test	Overall	Skills missed	Issue type
Python function app with Service Bus trigger	Passed	azure-prepare, azure-validate, azure-deploy	Routing miss
URL shortener with Terraform	Passed	azure-prepare, azure-validate, azure-deploy	Routing miss
HTTP API with Terraform	Failed	azure-prepare, azure-validate, azure-deploy	Routing miss
Static portfolio (SWA)	Passed	azure-prepare, azure-validate, azure-deploy	Routing miss
Whiteboard (SWA)	Passed	azure-validate, azure-deploy	Handoff gap
Static portfolio (Terraform)	Passed	azure-prepare, azure-validate, azure-deploy	Routing miss
Whiteboard (Terraform)	Passed	azure-prepare, azure-validate, azure-deploy	Routing miss
brownfield-dotnet_deploys_MvcMovie_90	Failed	azure-validate, azure-deploy	Planning-only stop
brownfield-dotnet_deploys_aspire_azure_functions	Failed	azure-validate, azure-deploy	Prepare executed deployment directly
brownfield-dotnet_deploys_aspire_client_apps_integration	Failed	azure-validate, azure-deploy	Planning-only stop
brownfield-dotnet_deploys_aspire_container_build	Passed	azure-prepare, azure-validate, azure-deploy	Routing miss
brownfield-dotnet_deploys_aspire_database_containers	Failed	azure-validate, azure-deploy	Planning-only stop
brownfield-dotnet_deploys_aspire_health-checks-ui	Failed	azure-validate, azure-deploy	Prepare executed deployment directly
brownfield-dotnet_deploys_eShop	Failed	azure-validate, azure-deploy	Prepare executed deployment directly
brownfield-dotnet_does_not_deploy_aspire_custom_resources	Failed	azure-validate, azure-deploy	Non-deployable app detected

Examples from diagnostics table

• brownfield-dotnet_deploys_aspire_azure_functions (prepare executed deployment directly)
• brownfield-dotnet_deploys_aspire_health-checks-ui (prepare executed deployment directly)
• brownfield-dotnet_deploys_eShop (prepare executed deployment directly)
• brownfield-dotnet_does_not_deploy_aspire_custom_resources (non-deployable app detected)

Suggested next steps

• Add a guardrail to azure-prepare that blocks deployment commands and forces validate/deploy handoff.
• Define a test expectation for non-deployable samples (skip/xfail) or switch to a deployable sample.
• Add deeper routing instrumentation to understand why some prompts still bypass skills.

[github-actions]

Thanks for filing this, @kvenkatrajan! 🙏

This has been labeled as a bug since azure-prepare is executing deployment commands directly rather than handing off to azure-validate/azure-deploy as intended. The skills, intent-detection, and deploy labels have been applied to reflect that this touches skill routing logic and intent/prompt dispatch. The existing integration-test label has been retained since the failures were surfaced by integration test runs.

The suggested next steps in the issue body (guardrail in azure-prepare, xfail/skip for non-deployable samples, deeper routing instrumentation) look like solid concrete code changes — a coding agent will be taking a look at this to help drive it forward.

Generated by Issue Triage for issue #1108

[kvenkatrajan]

@tmeschter - we should revisit this after the support for hooks.