Use when the user asks to "identify PM automation candidates", "automate PM reporting", "reduce manual PM processes", "find automation quick wins", or "design workflow automation". Activates when a stakeholder needs to scan PM processes for automation potential, calculate automation ROI, design automation specifications, prioritize automation backlog, or plan phased automation rollout across the PMO.

Use when the user asks to "track assumptions", "document constraints", "log assumptions", "manage project assumptions", or "validate planning hypotheses". Activates when a stakeholder needs to create an assumption register, document project constraints, link assumptions to risks, establish assumption validation cadence, or audit planning hypotheses across the project lifecycle.

Use when the user asks to "track assumptions", "document constraints", "log assumptions", "manage project assumptions", or "validate planning hypotheses". Activates when a stakeholder needs to create an assumption register, document project constraints, link assumptions to risks, establish assumption validation cadence, or audit planning hypotheses across the project lifecycle.

Universal current-state assessment producing 10-section analysis for ANY MetodologIA service type. Use when the user asks to "analyze the codebase", "assess current architecture", "run AS-IS analysis", "technical audit", "evaluate tech debt", "code quality assessment", "assess current state", "service assessment", "QA maturity", "PMO assessment", "RPA readiness", "data maturity", "cloud readiness", "design maturity", "talent gap analysis", or mentions "Phase 1", "current state", "legacy system review", "technical health check".

Universal current-state assessment producing 10-section analysis for ANY MetodologIA service type. Use when the user asks to "analyze the codebase", "assess current architecture", "run AS-IS analysis", "technical audit", "evaluate tech debt", "code quality assessment", "assess current state", "service assessment", "QA maturity", "PMO assessment", "RPA readiness", "data maturity", "cloud readiness", "design maturity", "talent gap analysis", or mentions "Phase 1", "current state", "legacy system review", "technical health check".

Target state (TO-BE) architecture design — C4 L2 containers, ADRs, nightmare scenario mitigations, MVP component, phased Strangler Fig migration. Use when the user asks to "design the target architecture", "create a TO-BE architecture", "plan a migration strategy", "define ADRs for a new system", "mitigate nightmare scenarios", or mentions Strangler Fig, C4 diagrams, saga pattern, anti-corruption layer, or legacy modernization.

Target state (TO-BE) architecture design — C4 L2 containers, ADRs, nightmare scenario mitigations, MVP component, phased Strangler Fig migration. Use when the user asks to "design the target architecture", "create a TO-BE architecture", "plan a migration strategy", "define ADRs for a new system", "mitigate nightmare scenarios", or mentions Strangler Fig, C4 diagrams, saga pattern, anti-corruption layer, or legacy modernization.

API design & governance — REST/GraphQL/gRPC, versioning, rate limiting, DX, contract-first. Use when the user asks to "design an API", "define API strategy", "implement contract-first", "set up API governance", "design API versioning", "improve developer experience", or mentions REST, GraphQL, gRPC, AsyncAPI, OpenAPI, API gateway, rate limiting, or API catalog.

API design & governance — REST/GraphQL/gRPC, versioning, rate limiting, DX, contract-first. Use when the user asks to "design an API", "define API strategy", "implement contract-first", "set up API governance", "design API versioning", "improve developer experience", or mentions REST, GraphQL, gRPC, AsyncAPI, OpenAPI, API gateway, rate limiting, or API catalog.

Analytics pipeline design — dbt-style transformations, data modeling, testing, documentation. Use when the user asks to "design analytics models", "set up dbt project", "plan data transformations", "define data contracts", "model star schema", or mentions staging models, marts, incremental strategies, or materializations.

Analytics pipeline design — dbt-style transformations, data modeling, testing, documentation. Use when the user asks to "design analytics models", "set up dbt project", "plan data transformations", "define data contracts", "model star schema", or mentions staging models, marts, incremental strategies, or materializations.

Análisis horizontal de estados financieros (P&L, Balance General, Flujo de Caja, notas/anexos) con comparación YoY de 2 períodos. Genera informes ejecutivos estandarizados para Junta Directiva y C-Level con variaciones absolutas, relativas, drivers de cambio, alertas y recomendaciones estratégicas. Usa esta skill SIEMPRE que el usuario mencione análisis horizontal, comparar estados financieros, variación año contra año, YoY, análisis de tendencias financieras, comparación de períodos, evolución financiera, cambios interanuales, delta financiero, o adjunte cualquier estado financiero y pida análisis comparativo. Trigger: análisis horizontal, comparar estados financieros, YoY, variación interanual, evolución financiera, delta financiero, comparar períodos.

Análisis horizontal de estados financieros (P&L, Balance General, Flujo de Caja, notas/anexos) con comparación YoY de 2 períodos. Genera informes ejecutivos estandarizados para Junta Directiva y C-Level con variaciones absolutas, relativas, drivers de cambio, alertas y recomendaciones estratégicas. Usa esta skill SIEMPRE que el usuario mencione análisis horizontal, comparar estados financieros, variación año contra año, YoY, análisis de tendencias financieras, comparación de períodos, evolución financiera, cambios interanuales, delta financiero, o adjunte cualquier estado financiero y pida análisis comparativo. Trigger: análisis horizontal, comparar estados financieros, YoY, variación interanual, evolución financiera, delta financiero, comparar períodos.

Comprehensive testing strategy for AI systems — testing scope matrix (6 types x 6 layers), model prediction testing, data quality testing, compliance and fairness testing, integration approaches, and CI/CD test automation. This skill should be used when the user asks to "define AI testing strategy", "test ML models", "design data quality tests", "plan fairness testing", "test AI pipelines", "design integration tests for ML", or mentions adversarial testing, drift simulation, model regression testing, bias testing, explainability testing, or AI test automation.

Comprehensive testing strategy for AI systems — testing scope matrix (6 types x 6 layers), model prediction testing, data quality testing, compliance and fairness testing, integration approaches, and CI/CD test automation. This skill should be used when the user asks to "define AI testing strategy", "test ML models", "design data quality tests", "plan fairness testing", "test AI pipelines", "design integration tests for ML", or mentions adversarial testing, drift simulation, model regression testing, bias testing, explainability testing, or AI test automation.

AI software architecture design — modules, layers, boundaries, design patterns, ADRs, quality attributes, and technical debt strategy for AI-enabled systems. This skill should be used when the user asks to "design AI system structure", "define AI module boundaries", "select AI architecture patterns", "document AI architecture decisions", "evaluate AI code architecture", or mentions AI pipelines, feature stores, model serving, drift detection, ML quality attributes, explainability architecture, or AI technical debt.

AI software architecture design — modules, layers, boundaries, design patterns, ADRs, quality attributes, and technical debt strategy for AI-enabled systems. This skill should be used when the user asks to "design AI system structure", "define AI module boundaries", "select AI architecture patterns", "document AI architecture decisions", "evaluate AI code architecture", or mentions AI pipelines, feature stores, model serving, drift detection, ML quality attributes, explainability architecture, or AI technical debt.

Use when the user asks to "use AI for project management", "augment PM with AI", "implement predictive scheduling", "parse status with NLP", or "design ML risk models". Activates when a stakeholder needs to identify AI augmentation opportunities for PM, build predictive scheduling models, automate status report parsing with NLP, design intelligent resource allocation, or create a human-AI collaboration model for project governance.

Use when the user asks to "use AI for project management", "augment PM with AI", "implement predictive scheduling", "parse status with NLP", or "design ML risk models". Activates when a stakeholder needs to identify AI augmentation opportunities for PM, build predictive scheduling models, automate status report parsing with NLP, design intelligent resource allocation, or create a human-AI collaboration model for project governance.

AI pipeline architecture design — development pipelines, production pipelines, data stores, model registry, CI/CD for AI, and non-functional requirements. This skill should be used when the user asks to "design AI pipelines", "architect ML pipelines", "select data stores for AI", "design model registry", "implement CI/CD for ML", "define AI pipeline requirements", or mentions MLOps, training pipeline, inference pipeline, feature pipeline, Blue and Gold deployment, or pipeline patterns.