mao-discovery-framework

Transforms metrics and findings into meaningful narratives — insight extraction, metrics-to-meaning conversion, comparison framing, and magnitude communication. Use when presenting scoring matrices, coverage metrics, performance data, cost estimates, or any quantitative finding that needs interpretation and context.

Visual data narrative design — chart selection, Mermaid diagram metodologia-storytelling, visual hierarchy, dashboard narratives, and annotation strategy. Use when selecting chart types, designing diagram narratives, building visual sequences for presentations, or annotating data visualizations for maximum comprehension.

System and library dependency mapping, vulnerability scanning, upgrade risk assessment, and license compliance analysis. Use when the user asks to "map dependencies", "analyze dependency risk", "check license compliance", "assess upgrade risk", or mentions dependency graph, vulnerability scanning, or supply chain security.

Configurable design system for HTML deliverables with tokens, page structure, and component library. Use when the user asks to "apply design system", "generate styled HTML", "set up brand tokens", "configure brand colors", or mentions "design system", "design tokens", "component library", "brand config", "page template".

MetodologIA branded design system — full-fidelity output templates for HTML, DOCX, XLSX, PPTX, and MD formats. Produces self-contained, accessible, production-ready deliverables in any format using the canonical MetodologIA Neo-Swiss Design System v6 tokens, components, and page templates. Use when generating branded outputs, converting between formats, creating HTML deliverables, building DOCX/PPTX/XLSX from markdown, or establishing brand compliance for any output.

Developer experience (DX) platform assessment, inner loop optimization, toolchain evaluation, and onboarding friction analysis. Use when the user asks to "assess developer experience", "optimize inner loop", "evaluate toolchain", or mentions DX scorecard, developer productivity, or cognitive load reduction.

DevSecOps pipeline architecture — CI/CD design, shift-left security, supply chain integrity, release management, and compliance automation. Use when the user asks to "design the CI/CD pipeline", "integrate security into delivery", "set up SBOM and artifact signing", "automate compliance", "measure DORA metrics", or mentions SAST, SCA, DAST, secrets scanning, IaC scanning, canary deployment, or policy-as-code.

Program-level digital transformation discovery — digital maturity assessment, service portfolio mapping, program architecture, change readiness, multi-service integration, program governance, and transformation roadmap. Use when the user asks to "assess digital maturity", "plan digital transformation", "design transformation program", "evaluate change readiness", "map service portfolio", "program governance", "transformation roadmap", or mentions digital transformation, maturity assessment, multi-workstream, program architecture, change management, or transformation program.

DR/BCP planning — RPO/RTO definition, failover design, backup strategies, tabletop exercises. Use when the user asks to "plan disaster recovery", "define RPO/RTO", "design failover", "create BCP", or mentions business continuity, backup strategy, recovery runbook, tabletop exercise.

Discovery-to-execution handover — operational transition package, commercial activation, governance transfer, and Phase 1 kickoff plan. Use when the user asks to "create handover", "transition to operations", "prepare delivery handoff", "activate commercial proposal", "hand off discovery", "prepare operations package", "close discovery engagement", or mentions handover, transition, delivery kickoff, proposal preparation, or discovery close-out.

This skill should be used when the user asks to "run a discovery", "orchestrate the pipeline", "start a consulting engagement", "coordinate the dream team", "plan a discovery session", "manage discovery inputs", or mentions discovery orchestration, phase sequencing, quality gates, data contracts, expert committee, dream team, or consulting pipeline. Always use this skill as the entry point for any discovery engagement — it coordinates all other skills.

Doc-as-code strategy design, documentation taxonomy, content governance, and knowledge base architecture. Use when the user asks to "design documentation strategy", "build knowledge base", "create doc-as-code pipeline", or mentions documentation governance, content taxonomy, or technical writing standards.

Context-adaptive industry expert that dynamically adopts the right SME lens based on client sector. Use when the user asks to "add industry context", "act as domain expert", "give me the banking/retail/health perspective", or mentions "SME", "subject matter expert", "industry lens", "sector analysis", "regulatory context".

Enterprise architecture alignment — capability mapping, domain decomposition, governance, technology radar, and strategic initiative roadmap. Use when the user asks to "map business capabilities", "build a technology radar", "define architecture governance", "prioritize strategic initiatives", "design team topologies", or mentions DDD domains, ARB, DORA metrics, maturity models, or target operating model.

Event-driven architecture — event catalog, schema registry, eventual consistency, saga, CQRS, event sourcing. Use when the user asks to "design event-driven system", "build event catalog", "implement CQRS", "design saga patterns", "set up schema registry", "implement event sourcing", or mentions Kafka, RabbitMQ, Pulsar, event bus, dead-letter queue, consumer groups, or event replay.

Execution tracking with 1-day sprints per developer, burndown charts (Atlassian-style), velocity tracking using the MetodologIA productivity model (1 FTE = 1 shippable feature/day from Sprint 2). Sprint 1 = onboarding. Produces burndown dashboards, velocity reports, and completion projections. Use when dimensioning execution effort, tracking delivery velocity, creating burndown projections, or when "burndown", "velocity", "sprints diarios", "1 feature por día", or "tracking de ejecución" is mentioned.

C-level executive pitch with financial modeling and persuasion architecture. Use when the user asks to "create a pitch", "build a business case", "justify the investment", "present to executives", "ROI analysis", "executive summary", or mentions "C-level presentation", "budget approval", "NPV", "IRR", "payback period", "business case", "Phase 5b".

Cloud financial operations assessment and strategy using FinOps Foundation framework. Use when the user asks to "assess cloud costs", "optimize cloud spending", "FinOps assessment", "cloud cost analysis", "rightsizing", "reservation strategy", "showback/chargeback model", "cloud unit economics", "cost allocation", or mentions "cloud financial management", "cost optimization", "FinOps maturity".

DDD domain taxonomy + 8-12 end-to-end business flows with trama specifications, process mapping, service flow documentation, and operational flow tracing. Use when the user asks to "map flows", "document business processes", "trace integrations", "identify failure points", "domain mapping", "DDD analysis", or mentions "Phase 2", "flow mapping", "integration matrix", "dependency graph", "swimlane diagrams", "business process documentation".

Comprehensive functional specification with use cases, business rules, and complexity/risk matrix, service specification, deliverable specification, and engagement spec. Use when the user asks to "write functional specs", "document use cases", "define business rules", "create requirements", "specification document", or mentions "Phase 5a", "functional specification", "MVP scope", "acceptance criteria", "casos de uso", "reglas de negocio".