Architecture Vision
PROWrite a target-state vision that guides without naming vendors.
Write, review, or de-solution an enterprise architecture VISION (target-state or pre-target directional). Use when asked to draft or critique an "architecture vision", "target state", "guard-rails", or "conceptual architecture", or when a document names products/vendors as the answer, reads as a solution rather than a direction, or asserts a target the organisation has not yet chosen. Enforces capability-first, system-agnostic framing with an honest named baseline. Not for Solution Architecture, detailed design, or implementation.
Ask for it in plain English, e.g.
Works in
You ask: Review this draft "architecture vision" excerpt and tell me what to fix. > ## Target State > The new student experience will be built on Vendor X DXP, with Vendor Y as the > identity provider and a React front end. All portals will be consolidated onto > Vendor X. The platform leverages RBAC for access control.

Example output shown for illustration. Your assistant produces this live from your own request once the skill is installed.