A localization role that checks whether an output still works for people in different locales, meaning regions or language-and-culture settings. It applies when internationalization, or adapting a product for multiple locales, is involved.
A market-analysis role that checks whether a product specification can stand out among competing products. It examines decisions through the lens of the competitive landscape.
A marketing role focused on which message should reach which audience through which channel. It applies to campaign and positioning decisions and passes funnel-performance analysis to a growth-analytics role.
A machine-learning engineering role focused on whether a model can be served reliably as a service. It applies to model-serving work and passes training-data pipeline work to a data-engineering role.
A role for reviewing whether company-wide financial, operational, and strategic risks stay within an accepted range. It is part of a contract-based workflow and passes detailed legal compliance work to another role.
A sales role for designing how leads and opportunities move through a sales process. It covers process design and hands message positioning to marketing.
A secure-coding role focused on making implementation code withstand attacks. It covers authentication and input-processing code and can hand work back for threat-model review.
A role for identifying threats around trust boundaries, authentication, and sensitive data. A trust boundary is a point where data or control moves between systems or users with different levels of trust.
A technical-writing role for structuring information that readers need to understand. It is intended for externally published documentation and points developer onboarding work to a developer-relations role.
A user-experience engineering role that turns interface decisions into reusable design tokens and rules. Design tokens are shared values such as colors, spacing, and type sizes.
The orchestration loop for contract v3: draft issues from the user's words, spawn role sessions (core plugins + role rulebook, agent account, issue- / branch), explain the PRs that come back, and relay the user's decisions — comments, review Approve, merge — with the user's own account, per conversation.