mao-discovery-framework

Functional analysis toolkit with 6 tools for requirements engineering. Use when the user asks to "run event storming", "create a story map", "extract business rules", "write acceptance criteria", "build traceability matrix", "detect anti-patterns", or mentions "Given/When/Then", "functional toolbelt", "requirements quality".

Generative AI architecture — RAG patterns, LLM orchestration, multi-model tiering, agent workflow design, vector database architecture, knowledge connectors, and GenAI quality assurance. This skill should be used when the user asks to "design RAG architecture", "architect LLM system", "select vector database", "design AI agents", "implement knowledge retrieval", "plan GenAI quality", or mentions RAG, embeddings, vector search, LLM orchestration, agent framework, context-aware generation, hallucination reduction, or multi-model routing.

Hypothesis-Driven Development (HDD) framework for structuring modernization proposals as testable hypotheses with Lean Startup cycles (Build-Measure-Learn). Transforms features into hypotheses with metrics, experiments, and kill/pivot/persevere thresholds. Use when formulating scenarios as hypotheses, designing validation experiments, applying Lean Startup to discovery, or when "HDD", "hypothesis", "hipótesis", "lean startup", "build-measure-learn", "experiment", "kill/pivot/persevere", or "validación de hipótesis" is mentioned.

Incident response framework — severity classification, escalation paths, postmortem templates. Use when the user asks to "design incident process", "define severity levels", "create escalation paths", "build postmortem template", or mentions incident response, on-call, war room, blameless postmortem.

Infrastructure and platform architecture — compute, network, storage, HA/DR, IAM, cloud landing zones, and cost optimization. Use when the user asks to "design cloud infrastructure", "plan network topology", "define HA/DR strategy", "set up cloud landing zones", "optimize cloud costs", or mentions VPC, Kubernetes, serverless, multi-AZ, IAM, reserved instances, or chaos testing.

System integration patterns — point-to-point, ESB, iPaaS, event mesh, API contract management, data mapping. Use when the user asks to "design integrations", "map system connections", "define API contracts", "plan event-driven integration", or mentions ESB, iPaaS, MuleSoft, API gateway, event mesh, data mapping.

Management and consulting discovery — PMO maturity assessment, methodology fitness evaluation, team capability analysis, governance model assessment, delivery performance baseline, Factor WOW assessment, and management transformation roadmap. Use when the user asks to "assess PMO maturity", "evaluate project management practices", "management discovery", "methodology assessment", "governance evaluation", "delivery performance analysis", "Factor WOW assessment", "management transformation", "agile maturity", "SAFe assessment", "PMO setup", or mentions "Disciplined Agile", "delivery excellence", "management consulting", "project governance", "ceremony health".

Mentoring and training discovery — capability assessment, learning path design, knowledge transfer planning, training delivery model, measurement framework, and training roadmap. Use when the user asks to "assess training needs", "design learning paths", "plan knowledge transfer", "evaluate mentoring program", "training gap analysis", "capability assessment", "upskilling plan", or mentions "training discovery", "mentoring readiness", "talent development", "MetodologIA University".

This skill should be used when the user asks to "create diagrams", "generate Mermaid", "visualize architecture", "diagram flows", "draw a sequence diagram", "create a C4 diagram", "add visual diagrams", or mentions diagramming, visualization, flowcharts, sequence diagrams, Mermaid syntax, architecture diagrams, or visual documentation. Use this skill to embed precise, syntactically valid Mermaid diagrams in any discovery deliverable.

Detailed migration execution guide — strangler fig, parallel run, big bang, rollback procedures, data migration. Use when the user asks to "plan migration", "design cutover", "build migration playbook", "define rollback strategy", or mentions strangler fig, parallel run, data migration, legacy modernization.

Mini Apps and Low-Code discovery — citizen developer readiness, platform assessment (Power Platform, OutSystems, Mendix, Retool), use case identification and prioritization, governance model, integration architecture, and low-code adoption roadmap. Use when the user asks to "evaluate low-code platforms", "assess citizen developer readiness", "mini apps strategy", "Power Platform assessment", "low-code governance", "no-code evaluation", "automation apps discovery", or mentions "citizen development", "low-code adoption", "mini apps".

Mobile app architecture -- native vs cross-platform, offline-first, state management, release management. Use when the user asks to "design mobile architecture", "choose between native and cross-platform", "implement offline-first", "plan mobile CI/CD", "optimize app performance", or mentions Flutter, React Native, KMP, MVVM, SwiftUI, Jetpack Compose, or app store deployment.

AS-IS assessment for mobile apps -- performance, compliance, dependency health, UX metrics. Use when the user asks to "assess the mobile app", "audit app health", "review app dependencies", "check app store compliance", "measure app performance", or mentions crash rate, ANR, app size, cold start time, or mobile tech debt.

Unified mobile platform assessment — merges former mobile-architecture and mobile-assessment into one skill. Covers cross-platform vs native strategy, store compliance, app vitals, architecture patterns, offline-first design, performance optimization, dependency health, and remediation roadmaps. Use when the user asks to "assess mobile architecture", "evaluate mobile platform", "audit app health", "choose between native and cross-platform", "check store compliance", "optimize mobile performance", "review app dependencies", or mentions Flutter, React Native, KMP, MVVM, crash rate, ANR, app size, cold start time, or mobile tech debt.

Deep feasibility validation across 7 dimensions by a Council of Seven Sages (Think Tank). Postdoctoral-level research rigor applied to scenario validation. Validates technical claims, quantitative assumptions, systemic risks, technology maturity, infrastructure limits, integration feasibility, and economic viability. Use when validating approved scenarios before roadmap commitment, when stakeholders need confidence in technical achievability, or when "Phase 3b" / "feasibility" / "think tank" / "7 sabios" is mentioned.

Observability architecture — logging, tracing, metrics, alerting, SLO/SLI, incident response. Use when the user asks to "design observability", "set up monitoring", "implement tracing", "configure alerting", "define SLOs", "design incident response", or mentions OpenTelemetry, Prometheus, Grafana, ELK, correlation IDs, burn rate, runbooks.

Performance assessment — load testing, capacity planning, bottleneck analysis, caching, CDN, SLAs. Use when the user asks to "analyze performance", "design load tests", "plan capacity", "optimize caching", "configure CDN", "define SLAs", "find bottlenecks", or mentions latency, throughput, p95, saturation, cache hit ratio, edge compute.

Discovery pipeline governance — phase gate management, resource orchestration, dependency control, and proposal QA validation across the entire discovery pipeline. Replaces former project-program-management (not generic PM, specific to discovery pipeline). Use when the user asks to "track the discovery", "govern the pipeline", "validate the proposal", "run governance check", "check phase dependencies", "coordinate resources", or mentions pipeline governance, phase gates, proposal readiness, milestone tracking, or cross-phase dependency management. Works as the structural glue that holds the entire discovery pipeline together — from Phase 0 through Handover.

Product roadmap prioritization, backlog strategy, value stream mapping, product-market fit validation. Use when the user asks to "define product roadmap", "prioritize backlog", "map value streams", "validate product-market fit", or mentions product vision, RICE scoring, opportunity trees, dual-track agile.

PMO governance backbone — portfolio tracking, phase gate management, resource orchestration, dependency control, and proposal QA validation across the entire discovery pipeline. Use when the user asks to "track the discovery", "manage the portfolio", "validate the proposal", "run governance check", "check phase dependencies", "coordinate resources", or mentions PMO, program management, portfolio governance, phase gates, proposal readiness, milestone tracking, or cross-phase dependency management. Works as the structural glue that holds the entire discovery pipeline together — from Phase 0 through Handover.