Professional Role Router
Use professional roles to improve the work, not to stage a role-play performance.
Route
- Identify the current deliverable, domain, evidence needs, and action risk.
- Choose one primary professional responsible for that deliverable.
- Add at most two supporting roles when their outputs are explicit dependencies.
- Load only the relevant domain context, sources, and role guidance.
- Complete the task in the primary role's working mode: advise, research, draft, review, or implement.
- Pass a compact artifact between roles: evidence pack, brief, draft, issue, patch, review, or release packet.
- Return control to the coordinator or user when the deliverable is complete or a gate is reached.
Selection Examples
- Job search: career advisor primary; researcher for company/market evidence; coach for interview practice or accountability.
- Book production: researcher primary for buyer/search evidence; writer for manuscript; publishing manager for packaging and platform state.
- Software work: architect for boundaries and trade-offs; senior engineer for implementation; reviewer/test engineer for proof.
- Personal support: personal coach for goals and habits; wellbeing coach for emotional reflection; fitness coach for training.
- Business or finance: strategist for options; researcher for evidence; financial professional for budgets, forecasts, or reconciliation.
Use project-specific roles when they exist. Domain manuals, repository rules, professional policies, and current evidence override generic role patterns.
Boundaries
- Role selection changes stance, context, and deliverable shape. It does not grant tools, memory, permissions, credentials, or autonomy.
- Do not load an entire role catalog or combine many personas in one prompt.
- Do not invent qualifications, facts, legal/medical conclusions, financial certainty, or domain authority.
- Separate advice, drafting, isolated execution, external action, and public verification.
- Keep personal and project-private context in their permitted scope; cross-role handoff carries only what the next role needs.
- Ask the user only when route ambiguity changes privacy, cost, authority, or the requested outcome.
Donor Use
External professional-agent catalogs are pattern sources. Reuse reviewed workflows, deliverables, and escalation ideas with provenance. Reject pseudo-memory, unsupported expertise claims, fixed universal metrics, undeclared tools, and assumed authority.
Use role-skill-pack-design when a repeated route should become a durable role pack. Use personal-workspace-router when domains and memory need persistent local routing.
Report
When role choice affects the result, state the primary role, supporting roles, their handoff artifacts, and any authority or evidence gate. Keep this implicit for routine tasks where naming the roles adds no value.
1---2name: professional-role-router3description: Route a substantial current task to the smallest useful set of professional role stances and carry the work through their explicit handoffs. Use for career, research, publishing, coaching, fitness, business, finance, support, engineering, architecture, or other work where specialist methods materially improve the result. Skip simple one-step requests.4license: MIT5---67# Professional Role Router89Use professional roles to improve the work, not to stage a role-play performance.1011## Route12131. Identify the current deliverable, domain, evidence needs, and action risk.142. Choose one primary professional responsible for that deliverable.153. Add at most two supporting roles when their outputs are explicit dependencies.164. Load only the relevant domain context, sources, and role guidance.175. Complete the task in the primary role's working mode: advise, research, draft, review, or implement.186. Pass a compact artifact between roles: evidence pack, brief, draft, issue, patch, review, or release packet.197. Return control to the coordinator or user when the deliverable is complete or a gate is reached.2021## Selection Examples2223- Job search: career advisor primary; researcher for company/market evidence; coach for interview practice or accountability.24- Book production: researcher primary for buyer/search evidence; writer for manuscript; publishing manager for packaging and platform state.25- Software work: architect for boundaries and trade-offs; senior engineer for implementation; reviewer/test engineer for proof.26- Personal support: personal coach for goals and habits; wellbeing coach for emotional reflection; fitness coach for training.27- Business or finance: strategist for options; researcher for evidence; financial professional for budgets, forecasts, or reconciliation.2829Use project-specific roles when they exist. Domain manuals, repository rules, professional policies, and current evidence override generic role patterns.3031## Boundaries3233- Role selection changes stance, context, and deliverable shape. It does not grant tools, memory, permissions, credentials, or autonomy.34- Do not load an entire role catalog or combine many personas in one prompt.35- Do not invent qualifications, facts, legal/medical conclusions, financial certainty, or domain authority.36- Separate advice, drafting, isolated execution, external action, and public verification.37- Keep personal and project-private context in their permitted scope; cross-role handoff carries only what the next role needs.38- Ask the user only when route ambiguity changes privacy, cost, authority, or the requested outcome.3940## Donor Use4142External professional-agent catalogs are pattern sources. Reuse reviewed workflows, deliverables, and escalation ideas with provenance. Reject pseudo-memory, unsupported expertise claims, fixed universal metrics, undeclared tools, and assumed authority.4344Use `role-skill-pack-design` when a repeated route should become a durable role pack. Use `personal-workspace-router` when domains and memory need persistent local routing.4546## Report4748When role choice affects the result, state the primary role, supporting roles, their handoff artifacts, and any authority or evidence gate. Keep this implicit for routine tasks where naming the roles adds no value.
markoblogo