Use when the user asks to "implement LeSS", "set up Nexus", "scale Scrum for multiple teams", "coordinate multi-team delivery", "unify product backlog across teams", or mentions LeSS, Nexus, multi-team Scrum, cross-team coordination, integrated increment. Triggers on: designs multi-team Scrum scaling, configures shared product backlog, establishes cross-team coordination events, creates integration strategy for 2-8 teams, produces scaling metrics dashboard.

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".

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 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".

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.

Use when the user asks to "compare vendor costs", "analyze TCO", "evaluate vendor proposals", "calculate total cost of ownership", "normalize vendor pricing", or mentions vendor comparison, total cost of ownership, vendor TCO, proposal evaluation, vendor scoring matrix, hidden cost analysis.

Use when the user asks to "manage vendors", "track vendor performance", "monitor SLAs", "evaluate supplier compliance", "create vendor scorecards", or mentions vendor management, supplier performance, SLA monitoring, contract compliance, vendor governance, vendor scorecard.

Use when the user asks to "assess waterfall maturity", "evaluate traditional PM practices", "check PMBOK adherence", "review predictive methodology readiness", "audit phase-gate compliance", or mentions waterfall assessment, traditional PM maturity, PMBOK compliance, PRINCE2 maturity, predictive PM evaluation, earned value adoption.

Use when the user asks to "implement waterfall", "plan PMBOK phases", "set up PRINCE2", "define stage gates", "design predictive lifecycle", "configure change control", or mentions waterfall, traditional PM, predictive lifecycle, stage-gate, PMBOK, PRINCE2, earned value management.

Workshop design methodology — event storming, impact mapping, user story mapping, design sprints. Replaces former workshop-facilitator (facilitation is the agent's job, design is the skill). Use when the user asks to "design a workshop", "plan event storming", "design impact mapping session", "design a sprint", "create user story map", "design discovery session", or mentions workshop design, design sprint, event storming, story mapping, or collaborative design.

Workshop design — event storming, impact mapping, user story mapping, design sprints. Use when the user asks to "plan a workshop", "run event storming", "facilitate impact mapping", "design a sprint", "create user story map", "facilitate discovery session", or mentions workshop facilitation, design sprint, event storming, story mapping, or collaborative design.

Use when the user asks to "prepare kickoff", "create kickoff deck", "plan team alignment", "design project launch meeting", "build team charter", or mentions kickoff package, project kickoff, team alignment meeting, ground rules, team charter. Triggers on: creates kickoff presentation deck, designs team alignment agenda, facilitates ground rules agreement, produces communication quick-reference, compiles team charter from kickoff outcomes.

Use when the user asks to "design a Kanban board", "set WIP limits", "improve flow", "measure lead time", "optimize throughput", or mentions Kanban, flow metrics, cumulative flow diagram, pull system, WIP limits, cycle time. Triggers on: designs Kanban board layout, calculates initial WIP limits, defines pull policies, establishes flow measurement framework, produces Kanban system design document.

Use when the user asks to "assess Kanban maturity", "evaluate Kanban practices", "check flow efficiency", "measure WIP discipline", "diagnose Kanban health", or mentions Kanban assessment, Kanban maturity, flow metrics evaluation, WIP limit assessment, Kanban readiness. Triggers on: scores Kanban maturity against KMM levels, evaluates flow health metrics, assesses WIP limit enforcement, detects Kanban anti-patterns, produces evolutionary improvement roadmap.

Use when the user asks to "configure Jira", "set up Azure DevOps", "design PM tool workflows", "create board configuration", "map tool to methodology", or mentions Jira configuration, Azure DevOps setup, PM tool setup, workflow design, board configuration. Triggers on: designs PM tool project structure, creates workflow state machines, configures board columns and swimlanes, maps methodology ceremonies to tool features, produces tool user guides.

Use when the user asks to "track issues", "manage project issues", "resolve blockers", "create issue log", "remove impediments", or mentions issue tracking, issue resolution, blocker management, impediment removal, issue escalation. Triggers on: creates issue tracking workflow, assigns issue resolution owners, enforces resolution SLAs, captures root cause analysis, produces issue trend analysis.

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.

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.