# Enterprise Context Mapper

> enterprise-context-mapper

- Skill: `45ck/enterprise-context-mapper` (Agent Skill)
- Install (CLI): `npx skillmds@latest add 45ck/enterprise-context-mapper`
- Raw SKILL.md: https://api.skillmd.com/api/skills/45ck/enterprise-context-mapper/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: 45ck (https://skillmd.com/u/45ck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/45ck/enterprise-context-mapper

---

# enterprise-context-mapper

## Purpose
Map the enterprise context around a system including business units, upstream/downstream systems, actors, governance constraints, and external dependencies.

## Expected inputs
- system scope
- business capabilities
- stakeholders
- known upstream/downstream systems

## Deliverables
- enterprise context map
- dependency list
- assumptions and gaps
- recommended next artifact

## Trigger this skill when
- You need to make an enterprise or integration decision that spans more than a single codebase.
- Multiple systems, teams, environments, or governance constraints influence the design.
- A recommendation needs to be tied to enterprise reality rather than generic integration advice.

## Operating procedure
1. Clarify the system, estate, or cross-system workflow being assessed.
2. Separate facts, assumptions, constraints, and missing enterprise context.
3. Produce a context-specific analysis rather than a platform- or buzzword-driven recommendation.
4. Make tradeoffs explicit, especially around governance, ownership, runtime failure, and operational cost.
5. Recommend the next most useful architecture or delivery skill.

## Quality gates
- Recommendations acknowledge enterprise constraints, ownership, and operational consequences.
- Interfaces, dependencies, and environment implications are not hand-waved away.
- Assumptions and open questions are visible.
- Output is specific enough to inform architecture, integration, or release planning.

## Output style
- Be concrete and structured.
- Separate evidence, inference, and recommendation.
- Prefer explicit tradeoffs over single-answer absolutism.
- Use priority or severity where useful.

## Failure modes to avoid
- Do not recommend technology because it sounds enterprise-grade.
- Do not ignore team boundaries, operational maturity, or integration sprawl.
- Do not treat all workloads as equally suited to the same platform pattern.
- Do not hide uncertainty behind confident language.

## Minimum output skeleton
```md
## Summary
## Findings or proposal
## Evidence vs assumptions
## Risks or tradeoffs
## Recommended next skill
```

## Handoff targets
- application-landscape-mapper
- enterprise-domain-alignment-checker
- environment-topology-planner