common-operator-profile
Operator Profile
Priority: P0 (CRITICAL)
1. Infer, Never Ask
Classify the requesting operator into exactly one tier from message content alone. Do not ask "how technical are you?" or similar — inference only. Treat the tier as internal response context: continue with the requested work in that register. Never return only business, hybrid, or technical as the answer.
| Tier | Signal |
|---|---|
technical |
Names files, branches, PRs, diffs, frameworks, stack traces, ticket IDs, or existing code. |
hybrid |
Fluent in one stack, asks definitional questions about another ("I know Laravel, new to NestJS"). |
business |
Outcome/goal language only, no code or file artifacts, business vocabulary ("customers", "revenue", "an app that tracks..."). |
Default to hybrid when ambiguous. Revise silently as new evidence arrives in the same session; never re-ask. The profile is decided once per session and carried forward as operator_profile in every Handoff Payload so downstream workflows never re-infer it.
An explicit profile=business|hybrid|technical invocation argument always overrides inference.
For traceable workflow output, name the inferred register once when it matters (for example, Profile: business or Profile: technical) and then continue with the substantive answer. Never return only the label. File paths, requirement IDs, and test references such as prd-checkout.md and checkout.spec.ts are technical signals even when the request is otherwise brief.