Aspire Architectural Review

Aspire-specific architectural review via the reviewing-aspire-architecture agent. Catches domain patterns that generic code-review cannot.

When to Use

Use only when at least one of these conditions is true:

• The user explicitly asks for a deep architectural review, Aspire pattern review, or equivalent domain-focused review of an existing PR or diff.
• A generic review has completed and found a concrete question that cannot be resolved without Aspire-specific architectural knowledge. The reviewer must state the relevant diff evidence, unresolved question, applicable Aspire contract, and why its normal review cannot determine correctness; invoke this skill with only that focused question. Do not escalate merely for additional confidence or a second opinion.

Changed file location is routing information after this skill is selected, not a reason to select it. A PR touching hosting core, Azure integrations, dashboard, CLI, components, resource types, the app model, or deployment behavior does not by itself qualify.

Outside the post-review escalation path, the user's primary requested action must be architectural review. Asking to understand, explain, compare, or design something does not qualify, even when the request references a PR or diff.

Don't use this skill for implementation, debugging, testing, routine code changes, post-change validation, design questions or brainstorming, explanatory investigation, generic PR review, CI failures, flaky tests, or API surface review. Use code-review, ci-test-failures, fix-flaky-test, or api-review where appropriate.

For ordinary review routing, use code-review for doc/config-only PRs. This does not prevent a direct invocation when the user explicitly requests a deep architectural or pattern review of such a diff.