Enterprise Knowledge Intelligence
Mission
Build a digital CIO twin of the provided context: a semantic map of enterprise entities, relationships, dependencies and knowledge gaps.
Inputs
Accept org charts, application inventories, project lists, process descriptions, document excerpts, meeting notes, risk logs, service data, architecture diagrams in text form and stakeholder notes.
Workflow
- Extract enterprise entities: people, teams, roles, applications, processes, projects, documents, risks, controls, data objects and KPIs.
- Map relationships: ownership, dependency, information flow, approval path, operational coupling, risk linkage and decision authority.
- Detect hidden dependencies, duplicate responsibilities, orphaned systems, knowledge islands and brittle single-person dependencies.
- Rank relationships by criticality, business impact, operational risk and confidence.
- Surface context gaps that block reliable decisions.
- Propose a reusable enterprise memory structure for later MCP or connector-backed persistence.
Output Format
- Executive Summary
- Entity Map
- Relationship Map
- Critical Dependencies
- Knowledge Islands
- Context Gaps
- Risk Implications
- Recommended Actions
- Evidence & Assumptions
- Missing Data
Guardrails
Separate confirmed relationships from inferred relationships. Do not invent organizational facts that are not present in the provided context.
1---2name: enterprise-knowledge-intelligence3description: Analyze enterprise knowledge relationships across people, teams, processes, applications, projects, documents and risks. Use for semantic discovery, dependency mapping, knowledge islands and context synthesis. Use when the user needs enterprise knowledge intelligence for CIO decision support.4---56# Enterprise Knowledge Intelligence78## Mission910Build a digital CIO twin of the provided context: a semantic map of enterprise entities, relationships, dependencies and knowledge gaps.1112## Inputs1314Accept org charts, application inventories, project lists, process descriptions, document excerpts, meeting notes, risk logs, service data, architecture diagrams in text form and stakeholder notes.1516## Workflow17181. Extract enterprise entities: people, teams, roles, applications, processes, projects, documents, risks, controls, data objects and KPIs.192. Map relationships: ownership, dependency, information flow, approval path, operational coupling, risk linkage and decision authority.203. Detect hidden dependencies, duplicate responsibilities, orphaned systems, knowledge islands and brittle single-person dependencies.214. Rank relationships by criticality, business impact, operational risk and confidence.225. Surface context gaps that block reliable decisions.236. Propose a reusable enterprise memory structure for later MCP or connector-backed persistence.2425## Output Format2627- Executive Summary28- Entity Map29- Relationship Map30- Critical Dependencies31- Knowledge Islands32- Context Gaps33- Risk Implications34- Recommended Actions35- Evidence & Assumptions36- Missing Data3738## Guardrails3940Separate confirmed relationships from inferred relationships. Do not invent organizational facts that are not present in the provided context.
rweisssieker-xp