mao-pm-apex

BI and analytics service discovery — data maturity assessment (DCAM/DMM), dashboard landscape inventory, semantic layer evaluation, self-service analytics readiness, data literacy assessment, analytics use case portfolio, and BI transformation roadmap. Distinct from bi-architecture (design skill); this is the discovery/assessment for BI-as-a-service engagements. Use when the user asks to "assess BI maturity", "evaluate analytics capabilities", "dashboard inventory", "data literacy assessment", "semantic layer review", "self-service analytics readiness", "analytics use case prioritization", "BI transformation roadmap", or mentions BI-as-a-service, analytics maturity, dashboard consolidation, data democratization, DCAM, DMM, or data literacy.

BI solution design — semantic layers, dashboard patterns, self-service analytics, KPI frameworks. Use when the user asks to "design BI architecture", "build a KPI framework", "set up self-service analytics", "design dashboard hierarchy", "create a semantic layer", or mentions metric trees, drill-down patterns, or reporting strategy.

Generates branded DOCX (Word) documents using the MetodologIA Neo-Swiss Design System v6. Uses python-docx to create professional documents with navy headers, gold accents, Poppins headings, and Trebuchet MS body text. Use when the user requests a Word document, DOCX output, or when the ghost menu routes to DOCX.

Generates branded PPTX (PowerPoint) presentations using the MetodologIA Neo-Swiss Design System v6. Uses python-pptx to create slide decks with navy backgrounds, gold accents, Poppins titles, and Trebuchet MS body text. Use when the user requests a presentation, slide deck, PPTX output, or when the ghost menu routes to PPTX format.

Generates branded XLSX (Excel) spreadsheets using the MetodologIA Neo-Swiss Design System v6. Uses openpyxl to create professional spreadsheets with navy headers, gold accent rows, and semantic conditional formatting. Use when the user requests a spreadsheet, XLSX output, or when the ghost menu routes to XLSX.

Organizational change readiness assessment producing readiness scorecard, resistance map, and intervention plan. Use when the user asks to "assess change readiness", "evaluate organizational readiness", "change impact analysis", "resistance mapping", "ADKAR assessment", "readiness scorecard", or mentions "Phase 5b", "adoption risk", "organizational capacity for change".

Cloud migration planning -- 7R assessment, workload classification, wave planning, cutover. Use when the user asks to "plan cloud migration", "assess workloads for migration", "design landing zone", "create migration waves", "plan cutover strategy", or mentions 7R, rehost, replatform, refactor, lift-and-shift, or migration factory.

Cloud-native design -- containers, service mesh, serverless, multi-cloud, FinOps. Use when the user asks to "design cloud-native architecture", "containerize the application", "evaluate service mesh", "plan serverless migration", "implement multi-cloud strategy", "optimize cloud costs", or mentions Kubernetes, Istio, Docker, Helm, Terraform, FinOps, or 12-factor.

Cloud-as-a-Service discovery — cloud readiness assessment, DevOps maturity (DORA), cloud operations model, FinOps assessment, cloud security posture, and cloud services roadmap. Distinct from cloud-migration (which covers migration strategy); this covers Cloud as an ongoing service offering. Use when the user asks to "assess cloud operations", "evaluate DevOps maturity", "DORA assessment", "FinOps evaluation", "cloud security posture", "SRE maturity", "cloud operations model", "cloud service roadmap", or mentions cloud-as-a-service, platform engineering, toil reduction, FinOps, cloud cost optimization, or cloud operations.

Business model and value capture strategy — identifies optimal commercial structures for technology engagements beyond T&M. Use when the user asks to "define business model", "structure the deal", "identify value capture", "design pricing strategy", "explore commercial models", or mentions earned value, joint venture, revenue share, outcome-based, licensing model, or commercial structure.

Competitive technical landscape analysis, technology differentiation assessment, build-vs-buy analysis, and market positioning evaluation. Use when the user asks to "analyze competition", "compare technology options", "build vs buy analysis", or mentions competitive matrix, differentiation map, or market positioning.

Regulatory and standards compliance assessment — GDPR, SOX, PCI-DSS, HIPAA, ISO 27001, NIST CSF. Use when the user asks to "evaluate compliance", "audit regulatory gaps", "assess GDPR readiness", "review PCI-DSS compliance", or mentions regulatory frameworks, data protection, compliance matrix.

Persuasive writing for executive audiences — value propositions, calls to action, cost-of-inaction narratives, and compelling summaries. Use when generating executive summaries, pitch narratives, scenario value propositions, recommendation justifications, or any prose that must drive a decision.

Cost driver identification — effort inductors, scope drivers, magnitude estimation, team composition modeling, risk-adjusted timeline ranges, service engagement sizing, consulting effort, automation ROI, and staffing model. Use when the user asks to "estimate effort", "identify cost drivers", "size the project", "plan team composition", "identify effort inductors", or mentions WBS, sizing, contingency, burn rate, PERT, Monte Carlo, or "Phase 4" cost work. NEVER produces final prices — produces drivers, ranges, and magnitude indicators with costing disclaimers.

Database design — schema patterns, indexing, partitioning, replication, migration, performance tuning. Use when the user asks to "design the database schema", "plan indexing strategy", "set up replication", "partition large tables", "migrate database schema", "tune query performance", or mentions normalization, sharding, B-tree indexes, zero-downtime migration, or connection pooling.

Data pipeline architecture — ingestion, orchestration, quality, lineage, SLAs. Use when the user asks to "design data pipelines", "architect ingestion", "set up orchestration", "plan data lake", "design lakehouse", or mentions Airflow, Dagster, CDC, data lineage, or pipeline SLAs.

Data governance framework — catalog, ownership, classification, retention, privacy compliance, data mesh. Use when the user asks to "build a data catalog", "define data ownership", "classify sensitive data", "design retention policies", "ensure privacy compliance", "implement data mesh governance", or mentions GDPR, CCPA, LGPD, data stewardship, PII, data lineage, or federated governance.

Data mesh readiness assessment and strategy using Zhamak Dehghani's 4 principles. Use when the user asks to "assess data mesh readiness", "design data mesh strategy", "domain data ownership", "data as a product", "self-serve data platform", "federated data governance", "data mesh migration", or mentions "data decentralization", "data domain ownership", "data product thinking".

Data quality framework — profiling, validation, anomaly detection, data contracts, SLA monitoring. Use when the user asks to "design data quality framework", "set up data contracts", "plan data validation", "detect data anomalies", "define data SLAs", or mentions data profiling, quarantine patterns, or remediation workflows.

ML/AI system design — model lifecycle, feature stores, experiment tracking, model serving, MLOps pipelines. Use when the user asks to "design an ML system", "architect model serving", "set up experiment tracking", "design feature store", "plan MLOps pipeline", or mentions model registry, A/B testing, drift detection, or retraining triggers.