--- title: "Enterprise architecture change planner" type: "skill" url: "https://useaiblocks.com/skills/enterprise-transition-architect" updated: "2026-10-28" first_published: "2026-10-25" job: "Plan your strategy" tested: true licence: "MIT" source: "https://github.com/magnus919/agent-skills/tree/92c327e525da69c9ad3812fd223a1770e977c2e3/enterprise-architecture" instructions: "https://useaiblocks.com/skills/enterprise-transition-architect/SKILL.md" --- # Enterprise architecture change planner > Bring business goals and system facts. Get a staged change plan with owners, links and proof needed at each step. Share business goals, capabilities, systems and limits. It maps current and target states, then plans change steps with owners, dependencies and proof needed to move ahead. Free skill for the job "Plan your strategy" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28 ## Links - Page: https://useaiblocks.com/skills/enterprise-transition-architect - Instructions (SKILL.md): https://useaiblocks.com/skills/enterprise-transition-architect/SKILL.md - All files (zip): https://useaiblocks.com/skills/enterprise-transition-architect.zip - JSON version: https://useaiblocks.com/skills/enterprise-transition-architect.json - In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get enterprise-transition-architect" ## What it does Bring goals and a system list. Map what each one serves, then plan changes with owners and exit checks. ## What you give it - Your business goals, scope and time horizon. - The people who own decisions and sign off. - Your list of capabilities, applications and data, with costs and limits. - Known gaps in your evidence (optional). ## What you get - A portfolio view that links capabilities to applications, owners and risks. - A current, target and transition plan with each claim marked as fact, assumption, decision or open question. - A record of who decides what, with a path for conflicts. - A phased roadmap with dependencies, owners and the proof each step needs. ## Example: what goes in and what comes out ### What goes in - Your business goals, scope and time horizon - The people who own decisions and sign off - Your list of capabilities, applications and data, with costs and known limits (optional) - Known gaps in your evidence (optional) ### Before you start - The full skill folder, with its reference and template files, added to your AI tool ### What comes out - **Enterprise context brief**: The goal, scope, time horizon, stakeholders, limits and evidence gaps, each marked as fact, assumption, decision or open question. - **Capability and application portfolio view**: Capabilities and value streams linked to applications, information, owners, costs, risks, duplication and lifecycle status. - **Current, target and transition assessment**: The current state from evidence, a target state from stated principles, and what makes a direct jump unsafe. - **Operating model and decision rights record**: Central, federated or hybrid options compared, with named roles for decisions, exceptions and conflict escalation. - **Transition architecture roadmap**: Phased steps with dependencies, investment assumptions, accountable owners and the evidence that shows each step is done. ## Use it when - You must plan enterprise architecture changes across many systems and teams. - You need to see which systems serve which capabilities, and where they overlap. - A leader asks how you get from today's setup to the target, step by step. - You need to say who decides what, and who settles conflicts. ## Skip it when - You need the design of one system or its parts: ask a software architect, or use a solution design step instead of this plan. - You need an org chart, team structure or pay design: work with your HR lead or an organization design specialist. - You need to coordinate delivery across many projects: use a program manager and a delivery plan once this roadmap is approved. ## How to use it 1. Add the whole skill folder to your AI tool, including the references and templates. The steps rely on those files. 2. If your tool cannot take a folder, paste the main instructions and each reference and template file into the chat. 3. Paste your goals, scope, time horizon and system list. Name who decides. 4. Ask your AI to follow the skill and plan your enterprise architecture changes. 5. Check the claims marked as assumptions or open questions. Fill the gaps with real facts. 6. Hand the approved roadmap to your delivery team for a detailed plan. ## What to do next - [Enterprise customer onboarding planner](https://useaiblocks.com/skills/copilot-gtm-enterprise-onboarding): Plan your strategy - [Enterprise account deal planner](https://useaiblocks.com/skills/copilot-gtm-enterprise-account-planning): Plan your strategy ## Sources and credits - From magnus919: https://github.com/magnus919/agent-skills/tree/92c327e525da69c9ad3812fd223a1770e977c2e3/enterprise-architecture, shared under the MIT licence (original name: enterprise-architecture). - [enterprise-architecture skill](https://github.com/magnus919/agent-skills/tree/92c327e525da69c9ad3812fd223a1770e977c2e3/enterprise-architecture), magnus919: Original instructions and supporting files, with attribution and the MIT licence. Display copy describes the task. ## Instructions (SKILL.md) ## Enterprise Architecture Use this skill to make enterprise-wide structure and change legible without turning architecture into a shelf of diagrams. Connect outcomes to capabilities, value streams, applications, information, technology, ownership, and a feasible sequence of change. ### Before you start Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait. **What you need** (use your own material or the linked skill): - **Your question** (yours): the decision or problem, and what a good outcome looks like. **Makes it better (optional):** - **Source text** (yours): a long source in full: an article, a video or talk transcript, or notes from a book, with its title, author and link. How to start: 1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name. 2. **Check what's missing.** Look for your question, source text. They can attach files, paste the details, or share a file path your assistant can read. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps. 3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it. ### Workflow 1. **Frame the enterprise question.** State the outcome, scope, time horizon, stakeholders, constraints, authority, and evidence gaps. Separate strategy, product commitments, operational facts, and architectural hypotheses. 2. **Map the landscape.** Identify capabilities and value streams, then relate applications, information objects, technology dependencies, owners, costs, risks, duplication, and lifecycle status. Use `references/capability-value-stream-and-portfolio-mapping.md`. 3. **Describe states.** Record the current state from evidence, define a target state from explicit principles and outcomes, and identify constraints that make a direct jump unsafe or unrealistic. Use `references/current-target-and-transition-architecture.md`. 4. **Choose the operating model.** Compare centralized, federated, and hybrid arrangements against decision locality, coordination cost, required coherence, skills, and risk. Do not prescribe reporting lines or compensation. Use `references/enterprise-operating-model-and-roles.md`. 5. **Make authority executable.** Assign decision rights, consultation, standards, exceptions, escalation, and feedback to named roles. Use `references/federated-governance-and-decision-rights.md`. 6. **Engage and publish for use.** Adapt views to stakeholder jobs, make uncertainty and provenance visible, and maintain accessible, findable information with a review owner. Use `references/stakeholder-engagement-and-architecture-information.md`. 7. **Sequence change.** Connect transition increments to capabilities, outcomes, dependencies, investment assumptions, and exit evidence. Use `templates/transition-architecture-roadmap.md`; hand approved delivery plans to `implementation-planning` or `migration-engineering` as appropriate. ### Output Contract Produce an enterprise context brief, capability/application portfolio view, current-target-transition assessment, operating-model and decision-rights record, or transition roadmap. Every material claim must be labeled as evidence, assumption, decision, or open question and have a source or named owner. ### Ownership Boundaries - System boundaries, runtime behavior, architecture characteristics, and solution tradeoffs belong to `software-architecture`. - API contracts and API portfolio mechanics belong to `api-design-and-evolution`. - Data platforms, data products, data models, and data governance belong to `data-architect`. - Reporting structures, team topology, talent, compensation, and culture belong to `org-design`; this skill records organizational dependencies without designing HR systems. - Product bets, product outcomes, and product sequencing belong to `product-roadmapping-and-portfolio`. - Technology adoption posture, build-versus-buy, standards, and technology governance mechanics belong to `technology-radar`. - Corporate direction, competitive choices, capital allocation, and M&A belong to `strategy-frameworks`. - Process optimization and operational execution belong to `operational-design`; enterprise architecture may use its findings as evidence. - Approved cross-system execution belongs to `implementation-planning` and `migration-engineering`, not this skill. - Cross-project program coordination, shared capacity, integrated benefits, and transformation delivery belong to `technical-program-management`; this skill provides the architecture evidence and decision-rights inputs. ### When Not To Use Use the narrow owner when the request has no enterprise portfolio, cross-domain alignment, operating-model, or transition-architecture question. Do not use this skill to produce a solution design, organization chart, product roadmap, technology radar entry, data architecture, API contract, or corporate strategy verdict. ### After this When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own: - The [Enterprise customer onboarding planner](https://useaiblocks.com/skills/copilot-gtm-enterprise-onboarding). It takes the plan. - The [Enterprise account deal planner](https://useaiblocks.com/skills/copilot-gtm-enterprise-account-planning). It takes the document. If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring. ### Reference Guide | Decision point | Load | |---|---| | Mapping capabilities, value streams, applications, information, or duplication | `references/capability-value-stream-and-portfolio-mapping.md` | | Comparing current, target, and transition states | `references/current-target-and-transition-architecture.md` | | Selecting an enterprise operating model and defining architecture roles | `references/enterprise-operating-model-and-roles.md` | | Assigning decision rights, standards, exceptions, or escalation | `references/federated-governance-and-decision-rights.md` | | Interviewing stakeholders or publishing usable architecture information | `references/stakeholder-engagement-and-architecture-information.md` | | Establishing scope and evidence | `templates/enterprise-context-brief.md` | | Creating a portfolio view | `templates/capability-portfolio-view.md` | | Sequencing target-state change | `templates/transition-architecture-roadmap.md` | | Checking provenance and transformation constraints | `references/source-index.md` | ### Completion Stop when the enterprise scope and decision owner are explicit, the portfolio and state claims have evidence or named gaps, transition increments have dependencies and exit evidence, decision rights include conflict handling, and specialist handoffs are recorded. Escalate unresolved authority or strategy conflicts rather than resolving them by assumption.