Vendor evaluation and selection framework — RFP/RFI design, scoring matrices, TCO analysis, contract risk. Use when the user asks to "evaluate vendors", "design RFP", "compare platforms", "assess TCO", or mentions vendor selection, build-vs-buy, technology evaluation, procurement strategy.

UX writing and document accessibility standards for technical deliverables. Use when the user asks to "improve readability", "fix information hierarchy", "reduce cognitive load", "write microcopy", "check readability score", or mentions "UX writing", "scanability", "Flesch-Kincaid", "escritura UX", "legibilidad", "cognitive load".

UX writing and document accessibility standards for technical deliverables. Use when the user asks to "improve readability", "fix information hierarchy", "reduce cognitive load", "write microcopy", "check readability score", or mentions "UX writing", "scanability", "Flesch-Kincaid", "escritura UX", "legibilidad", "cognitive load".

UX/UI design discovery — design maturity assessment, design system inventory, user research capability evaluation, usability baseline, information architecture assessment, design process governance, and design transformation roadmap. Use when the user asks to "evaluate design maturity", "assess UX capability", "audit design system", "usability assessment", "information architecture review", "design ops evaluation", "UX transformation plan", or mentions "design discovery", "UX readiness", "design governance".

UX/UI design discovery — design maturity assessment, design system inventory, user research capability evaluation, usability baseline, information architecture assessment, design process governance, and design transformation roadmap. Use when the user asks to "evaluate design maturity", "assess UX capability", "audit design system", "usability assessment", "information architecture review", "design ops evaluation", "UX transformation plan", or mentions "design discovery", "UX readiness", "design governance".

End-user advocate that evaluates deliverable clarity, cognitive load, accessibility, adoption risks, and biases. Use when the user asks to "review for clarity", "check readability", "evaluate from user perspective", "assess adoption risk", or mentions "user representative", "voice of the user", "representante del usuario", "clarity review", "cognitive load check".

End-user advocate that evaluates deliverable clarity, cognitive load, accessibility, adoption risks, and biases. Use when the user asks to "review for clarity", "check readability", "evaluate from user perspective", "assess adoption risk", or mentions "user representative", "voice of the user", "representante del usuario", "clarity review", "cognitive load check".

Test strategy design — pyramid, automation, E2E, contract testing, shift-left, test data management, QA-as-a-service strategy, test factory design, PITT methodology, QA CoE design. Use when the user asks to "design test strategy", "build test automation", "implement contract testing", "manage test data", "define quality gates", or mentions test pyramid, Pact, Playwright, Cypress, coverage targets, flaky tests, chaos engineering.

Test strategy design — pyramid, automation, E2E, contract testing, shift-left, test data management, QA-as-a-service strategy, test factory design, PITT methodology, QA CoE design. Use when the user asks to "design test strategy", "build test automation", "implement contract testing", "manage test data", "define quality gates", or mentions test pyramid, Pact, Playwright, Cypress, coverage targets, flaky tests, chaos engineering.

Structured technology monitoring across analyst firms (Gartner, Forrester, IDC), academic sources (Stanford HAI, IEEE, ACM), editorial platforms (O'Reilly Radar, ThoughtWorks Tech Radar), and individual thought leaders (Martin Fowler, Paulo Caroli, Gregor Hohpe, Jez Humble). Produces vigilance reports with signals classified by urgency and impact. Use when evaluating technology trends, preparing sector-specific tech intelligence, validating technology choices against current landscape, or when "vigilancia tecnológica", "tech watch", "Gartner", "Forrester", "tech radar", "Stanford HAI", "IEEE", or "tendencias tecnológicas" is mentioned.

Structured technology monitoring across analyst firms (Gartner, Forrester, IDC), academic sources (Stanford HAI, IEEE, ACM), editorial platforms (O'Reilly Radar, ThoughtWorks Tech Radar), and individual thought leaders (Martin Fowler, Paulo Caroli, Gregor Hohpe, Jez Humble). Produces vigilance reports with signals classified by urgency and impact. Use when evaluating technology trends, preparing sector-specific tech intelligence, validating technology choices against current landscape, or when "vigilancia tecnológica", "tech watch", "Gartner", "Forrester", "tech radar", "Stanford HAI", "IEEE", or "tendencias tecnológicas" is mentioned.

Technical documentation precision — progressive disclosure, terminology consistency, evidence attribution, and reproducible analysis. Use when writing AS-IS analyses, functional specs, architecture documents, handover guides, or any deliverable requiring technical rigor and documentation standards.

Technical documentation precision — progressive disclosure, terminology consistency, evidence attribution, and reproducible analysis. Use when writing AS-IS analyses, functional specs, architecture documents, handover guides, or any deliverable requiring technical rigor and documentation standards.

Technical fact-checking and multidimensional feasibility analysis — validates claims, assumptions, and technical decisions from scenario analysis against evidence. Use when the user asks to "validate feasibility", "fact-check the scenario", "verify technical claims", "run feasibility analysis", "stress-test the approach", or mentions technical due diligence, feasibility study, risk validation, or "Phase 3b" verification work.

Technical fact-checking and multidimensional feasibility analysis — validates claims, assumptions, and technical decisions from scenario analysis against evidence. Use when the user asks to "validate feasibility", "fact-check the scenario", "verify technical claims", "run feasibility analysis", "stress-test the approach", or mentions technical due diligence, feasibility study, risk validation, or "Phase 3b" verification work.

Technical debt quantification, debt quadrant classification (reckless/prudent x deliberate/inadvertent), remediation prioritization, and paydown roadmap generation. Use when the user asks to "assess technical debt", "quantify debt", "classify tech debt", "prioritize remediation", or mentions debt inventory, impact scoring, or paydown planning.

Technical debt quantification, debt quadrant classification (reckless/prudent x deliberate/inadvertent), remediation prioritization, and paydown roadmap generation. Use when the user asks to "assess technical debt", "quantify debt", "classify tech debt", "prioritize remediation", or mentions debt inventory, impact scoring, or paydown planning.

Conway's Law analysis, team interaction modes, cognitive load assessment, organizational design. Use when the user asks to "design team structure", "assess cognitive load", "map team interactions", "apply Conway's Law", or mentions stream-aligned teams, platform teams, enabling teams, team-first thinking.

Conway's Law analysis, team interaction modes, cognitive load assessment, organizational design. Use when the user asks to "design team structure", "assess cognitive load", "map team interactions", "apply Conway's Law", or mentions stream-aligned teams, platform teams, enabling teams, team-first thinking.

Use when the user asks to "design team structure", "apply Team Topologies", "optimize team boundaries", "reduce cognitive load", "map team interaction modes", or mentions Team Topologies, Conway's Law, stream-aligned teams, platform teams, enabling teams, cognitive load, team interaction patterns.