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.

Complete transformation roadmap with phased execution, investment horizon, team ramp-up, risk-adjusted timeline, and estimation pivot points. Use when the user asks to "create a roadmap", "plan the transformation", "build an investment case", "team sizing", "risk-adjusted timeline", or mentions "Phase 4", "solution roadmap", "transformation plan", "phased execution", "PoC validation criteria", "kill criteria", "go/no-go gates".

Software and technology viability validator — deep forensic analysis of whether proposed software solutions, AI/ML components, and technology choices are viable substance or speculative smoke. Covers service viability, platform viability, methodology viability, tool viability, and vendor assessment for any service type. Use when the user asks to "validate technology viability", "detect vaporware", "verify AI claims", "assess software maturity", "check if this tech actually works", or mentions technology due diligence, software validation, AI feasibility, vendor evaluation, or tech-stack viability. This is the devoted software-specific validator — separate and more critical than the multidimensional feasibility analysis.

Software architecture design — modules, layers, boundaries, design patterns, ADRs, quality attributes, and technical debt strategy. Use when the user asks to "design the internal structure", "define module boundaries", "select architecture patterns", "document architecture decisions", "evaluate code architecture", or mentions CQRS, Hexagonal, Event Sourcing, Clean Architecture, ADRs, or technical debt.

SAP S/4HANA implementation skill covering module selection (CO, SD, PS, FI, HCM), SAP Activate methodology, fit-to-standard workshops, multi-country localization, intercompany configuration, and professional services industry patterns. Use whenever the user mentions SAP, S/4HANA, SAP implementation, fit-to-standard, SAP modules, SAP localization, SAP migration, ERP implementation, or needs guidance on SAP configuration for IT services companies. Also trigger for SAP-specific gap analysis, SAP scope definition, SAP best practices, CATS integration, Strangler Fig migration, Activity Type configuration, or revenue recognition patterns for T&M, fixed price, retainer, or managed services contracts. Trigger: SAP implementation, S/4HANA configuration, fit-to-standard, SAP modules, SAP localization, CATS integration, Strangler Fig, Activity Types, revenue recognition.

Regional finance and accounting standards skill covering Colombia (NIIF/DIAN/CTC), Ecuador (SRI/USD dollarization), Mexico (SAT/CFDI), United States (GAAP/ASC 606), Spain (AEAT/SII), and pan-Americas considerations. Use whenever the user mentions financial regulations, tax compliance, electronic invoicing, transfer pricing, CTC calculation, intercompany billing, multi-currency management, localization requirements, withholding taxes, or labor cost structures for IT services companies operating across these regions. Essential for SAP localization configuration and fit-to-standard financial workshops. Also trigger when discussing cost-vs-sale segregation, Activity Type cost rates, margin visibility, arm's length pricing, or any cross-border billing. Trigger: CTC calculation, transfer pricing, intercompany billing, tax compliance, e-invoicing, SAP localization, withholding taxes, Activity Type rates, margin visibility.

BPMN 2.0 process modeling and analysis skill for AS-IS/TO-BE business process documentation, bottleneck identification, automation opportunity assessment, process maturity scoring, and process improvement design. Use whenever the user mentions process mapping, BPMN, business process, process flow, swimlane, AS-IS process, TO-BE process, process improvement, operational workflow, delivery monitoring, process maturity, or needs to model how work flows through an organization. Especially relevant for SAP fit-to-standard workshops, IT services company operations, and service variant analysis. Also trigger for RACI assignment, automation ROI, or compliance audit trail. Trigger: BPMN, process mapping, AS-IS TO-BE, process flow, swimlane, process maturity, automation ROI, RACI, fit-to-standard, process improvement, operational workflow.

SLO/SLA/SLI definition — error budget policies, reliability targets, customer-facing commitments. Use when the user asks to "define SLAs", "design SLOs", "set reliability targets", "create error budget policy", or mentions SLI, service level, uptime, nines, error budgets.

Use when the user asks to "analyze skills gaps", "assess team capabilities", "plan training", "evaluate competency readiness", "identify capability shortfalls", or mentions skills inventory, capability assessment, competency gap, training needs analysis, skill proficiency mapping.

Use when the user asks to "calculate cost of delay", "run WSJF analysis", "prioritize by economic value", "quantify delay impact", or "sequence work by value". Activates when a stakeholder needs to quantify the economic cost of delaying features, apply Weighted Shortest Job First prioritization, transform subjective prioritization into data-driven economic sequencing, or perform sensitivity analysis on priority rankings.

Use when the user asks to "convert skills to Cursor", "export to Codex", "convert to Gemini format", "port skills to another AI platform", or "create multi-platform skills". Activates when a stakeholder needs to convert MOAT skills from Claude Code format to Cursor rules, GitHub Codex AGENTS.md, Google Gemini system instructions, or other AI coding assistant formats while preserving skill logic and evidence protocols.

Security architecture design — threat modeling, zero trust, identity, encryption, compliance. Use when the user asks to "design security architecture", "model threats", "implement zero trust", "design IAM", "plan encryption strategy", "map compliance requirements", or mentions STRIDE, OWASP, OAuth, RBAC, SOC2, ISO27001, PCI-DSS.

Industry/sector intelligence analysis — context-adaptive expert that provides sector-specific insights, regulatory context, benchmarks, and risk overlays. Replaces former dynamic-sme. Use when the user asks to "add industry context", "analyze sector", "give me the banking/retail/health perspective", or mentions "sector intelligence", "industry analysis", "industry lens", "sector analysis", "regulatory context".

Use when the user asks to "scan for secrets", "detect credentials", "sanitize sensitive data", "check for exposed passwords", "run security gate G0", or mentions secret detection, credential scanning, security gate G0, sensitive data masking, API key exposure, token detection.

Use when the user asks to "configure dashboards", "set up data feeds", "design monitoring tools", "automate dashboard updates", or "integrate PM data sources". Activates when a stakeholder needs to configure PM dashboard tooling, set up automated data feeds from PM tools, design visualization components, configure alert thresholds, or establish dashboard refresh cadence and access control.

Use when the user asks to "implement Scrum", "plan sprints", "define ceremonies", "set up Scrum artifacts", "design sprint cadence", or mentions Scrum, sprint planning, daily standup, sprint review, retrospective, product backlog, sprint backlog, Definition of Done, velocity tracking.

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.

Use when the user asks to "create a WBS", "decompose scope", "define work breakdown structure", "document scope statement", "set project boundaries", "identify deliverables", or mentions scope definition, deliverable decomposition, work packages, scope baseline, exclusions, 100% rule.

Use when the user asks to "create a schedule", "build a Gantt chart", "define critical path", "plan milestones", "establish timeline", "estimate durations with PERT", or mentions scheduling, dependencies, float, lead/lag, fast-tracking, crashing, schedule baseline, 3-point estimation.