Skip to content

Enterprise IT Strategy Consultant

Assess, design, and communicate enterprise IT strategy — from current-state architecture analysis through target-state roadmap, technology selection, transformation planning, and governance frameworks.

Software Engineering|v1|Updated 7/16/2026|License: Proprietary
MCP get_skill({ skillId: "enterprise-it-strategy-consultant" })

Use this skill with your agent

Create a free account and connect via MCP

Get Started Free
---
title: "Enterprise IT Strategy Consultant"
description: "Assess, design, and communicate enterprise IT strategy — from current-state architecture analysis through target-state roadmap, technology selection, transformation planning, and governance frameworks."
author: AgentArmory
license: Proprietary
---

# Enterprise IT Strategy Consultant

Assess, design, and communicate enterprise IT strategy — from current-state architecture analysis through target-state roadmap, technology selection, transformation planning, and governance frameworks.

## Table of Contents

- [When to Use](#when-to-use)
- [Triggers](#triggers)
- [Methodology](#methodology)
- [Dos](#dos)
- [Don'ts](#don'ts)
- [Pitfalls](#pitfalls)
- [Validate Before Shipping](#validate-before-shipping)
- [Cross-Skill Hints](#cross-skill-hints)

## When to Use

Use when asked to assess current IT architecture, design a technology roadmap, evaluate build-vs-buy decisions, plan a digital transformation, create an IT strategy document, or provide technology advisory for a business. Do NOT use for hands-on coding, infrastructure provisioning, or deployment automation (use DevOps/Platform Engineering skills for those). Do NOT use for one-time technology recommendations (those belong in the specific technology's skill).

## Triggers

"IT strategy", "technology roadmap", "enterprise architecture", "digital transformation", "IT assessment", "technology audit", "architecture review", "IT modernization", "platform strategy", "technology stack evaluation", "build vs buy", "IT governance", "IT operating model", "cloud strategy", "infrastructure strategy", "IT cost optimization", "technology portfolio", "enterprise IT roadmap", "IT capability assessment"

## Methodology

### Phase 1: Current-State Assessment (As-Is)

Before recommending any changes, understand the existing landscape. Skip this phase and you will recommend solutions to problems that don't exist.

1. **IT capability inventory**: Document what systems, platforms, and tools exist. For each, capture:
   - System name, vendor, version
   - Business function served
   - Deployment model (on-prem, cloud, hybrid, SaaS)
   - Integration points (what talks to what)
   - Age and support status (current-gen, legacy, end-of-life)
   - Annual operating cost (licenses, hosting, support, staff)
   - Business criticality (mission-critical, important, nice-to-have)

2. **Architecture Layer Mapping**: Organize capabilities into layers:
   - **Business layer**: Processes, org structure, KPIs
   - **Application layer**: Systems, services, integrations
   - **Data layer**: Databases, data lakes, analytics, governance
   - **Infrastructure layer**: Compute, network, storage, identity

Continue reading

Sign up for a free account to view the full skill content

Login / Register
#IT strategy#enterprise architecture#technology roadmap#digital transformation#IT governance#technology assessment#build vs buy#IT operating model
License: Proprietary

Related Skills

More skills in Software Engineering

Accessibility Standards

Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.

#github-copilot#accessibilityMIT

Accord

Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.

#broad-capability#developmentMIT

Acquire Codebase Knowledge

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

#github-copilot#documentationMIT

Acreadiness Assess

Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.

#github-copilot#planningMIT

Acreadiness Generate Instructions

Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.

#github-copilot#skillMIT

Acreadiness Policy

Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.

#github-copilot#planningMIT
Enterprise IT Strategy Consultant - AgentArmory Skill — AgentArmory