Use when the user asks to "plan integration", "map cross-project dependencies", "define interface agreements", "coordinate between projects", "manage cross-team dependencies", or mentions integration management, cross-project coordination, interface contracts. Triggers on: maps integration points between components, defines interface data contracts, creates dependency matrices, designs cross-project coordination protocols, produces integration verification checklists.

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.

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.

Use when the user asks to "analyze project inputs", "process documents", "extract requirements", "review project brief", "parse RFP content", or mentions input processing, document analysis, requirement extraction, project brief analysis. Triggers on: analyzes project input documents, extracts structured requirements from briefs, detects contradictions in source documents, normalizes project inputs for planning, produces input completeness scorecard.

Use when the user asks to "analyze project inputs", "process documents", "extract requirements", "review project brief", "parse RFP content", or mentions input processing, document analysis, requirement extraction, project brief analysis. Triggers on: analyzes project input documents, extracts structured requirements from briefs, detects contradictions in source documents, normalizes project inputs for planning, produces input completeness scorecard.

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.

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.

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.

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.

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.

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.

Use when the user asks to "test a hypothesis", "validate assumptions through delivery", "run experiment-driven project", "design build-measure-learn cycles", "validate project assumptions", or mentions hypothesis-driven delivery, HDD, validated learning, experiment design, build-measure-learn. Triggers on: converts assumptions into testable hypotheses, designs minimum viable experiments, facilitates pivot-or-persevere decisions, documents validated learning, ranks hypotheses by risk and impact.

Use when the user asks to "test a hypothesis", "validate assumptions through delivery", "run experiment-driven project", "design build-measure-learn cycles", "validate project assumptions", or mentions hypothesis-driven delivery, HDD, validated learning, experiment design, build-measure-learn. Triggers on: converts assumptions into testable hypotheses, designs minimum viable experiments, facilitates pivot-or-persevere decisions, documents validated learning, ranks hypotheses by risk and impact.

Use when the user asks to "design a hybrid approach", "combine agile and waterfall", "create hybrid methodology", "integrate iterative and sequential delivery", "build adaptive lifecycle", or mentions hybrid PM, water-scrum-fall, bimodal, agile-traditional blend, adaptive lifecycle. Triggers on: designs a hybrid methodology, maps components to delivery approaches, creates interface agreements between agile and waterfall, unifies governance across methodologies, blends iterative and predictive planning.

Use when the user asks to "design a hybrid approach", "combine agile and waterfall", "create hybrid methodology", "integrate iterative and sequential delivery", "build adaptive lifecycle", or mentions hybrid PM, water-scrum-fall, bimodal, agile-traditional blend, adaptive lifecycle. Triggers on: designs a hybrid methodology, maps components to delivery approaches, creates interface agreements between agile and waterfall, unifies governance across methodologies, blends iterative and predictive planning.

Use when the user asks to "assess hybrid methodology readiness", "evaluate hybrid approach", "check hybrid methodology maturity", "measure integration capability", "diagnose water-scrum-fall", or mentions hybrid assessment, hybrid readiness, mixed methodology evaluation, iterative-sequential integration maturity. Triggers on: evaluates hybrid methodology maturity, detects hybrid anti-patterns, scores integration capability, assesses dual-governance readiness, produces hybrid adoption roadmap.

Use when the user asks to "assess hybrid methodology readiness", "evaluate hybrid approach", "check hybrid methodology maturity", "measure integration capability", "diagnose water-scrum-fall", or mentions hybrid assessment, hybrid readiness, mixed methodology evaluation, iterative-sequential integration maturity. Triggers on: evaluates hybrid methodology maturity, detects hybrid anti-patterns, scores integration capability, assesses dual-governance readiness, produces hybrid adoption roadmap.

This skill should be used when the user asks to "create a Sofka HTML document", "generate a branded report", "build an executive deliverable", "upgrade HTML to brand standards", "fix broken Sofka styles", "convert markdown to HTML", "batch convert deliverables to HTML", or mentions Sofka HTML, entregable, brand deliverable, Design System v5, Dark Authority, or any combination of Sofka + document/report/summary/analysis/roadmap. Also use when batch-upgrading existing HTML files to Sofka brand compliance, even if the user does not explicitly say "brand". Triggers on: convert to HTML, branded HTML, DS v5, markdown to HTML pipeline, Mermaid diagrams in HTML.

This skill should be used when the user asks to "create a Sofka HTML document", "generate a branded report", "build an executive deliverable", "upgrade HTML to brand standards", "fix broken Sofka styles", "convert markdown to HTML", "batch convert deliverables to HTML", or mentions Sofka HTML, entregable, brand deliverable, Design System v5, Dark Authority, or any combination of Sofka + document/report/summary/analysis/roadmap. Also use when batch-upgrading existing HTML files to Sofka brand compliance, even if the user does not explicitly say "brand". Triggers on: convert to HTML, branded HTML, DS v5, markdown to HTML pipeline, Mermaid diagrams in HTML.

Use when the user asks to "define governance", "create governance model", "set up escalation paths", "design authority matrix", "establish decision framework", or mentions project governance, steering committee, decision framework, authority levels, escalation matrix. Triggers on: builds a governance charter, designs escalation paths, defines decision-making authority, creates steering committee structure, maps authority levels.