Specialist Dispatch
Use this skill when a task benefits from a specialist lens but does not require
installing a large external agent marketplace.
This skill turns broad agent catalogs into a small Codex-native dispatch layer.
It can be used with subagents when available, or as a checklist for the main
agent when no subagent tool exists.
Specialist Profiles
Choose the smallest set:
- architect: boundaries, dependency direction, module shape, migration seams;
- backend: APIs, domain logic, persistence, concurrency, errors;
- frontend: UI behavior, state, accessibility, visual quality;
- security: auth, authz, secrets, parser risk, supply chain;
- data: schemas, migrations, analytics, integrity, retention;
- DevOps: CI, deploy, runtime config, observability;
- QA: test plan, regression coverage, edge cases;
- docs: user-facing and operator-facing documentation;
- performance: evidence-led bottleneck analysis;
- product: user workflow, scope, acceptance criteria.
Dispatch Rules
- Do not spawn a specialist without a concrete question.
- Give each specialist bounded files and expected output.
- Prefer read-only specialist review unless implementation ownership is clear.
- Use
agent-squad when multiple specialists will work in parallel.
- Use
subagent-result-merge to consolidate outputs.
Specialist Prompt Shape
Specialist:
Question:
Scope:
Allowed files:
Forbidden files:
Evidence required:
Expected output:
Validation:
Output
Report:
- selected specialists;
- why each was needed;
- scope boundaries;
- result or next routing skill.
1---2name: specialist-dispatch3description: Selects scoped architecture, backend, frontend, security, data, DevOps, QA, docs, performance, or product roles.4---56# Specialist Dispatch78Use this skill when a task benefits from a specialist lens but does not require9installing a large external agent marketplace.1011This skill turns broad agent catalogs into a small Codex-native dispatch layer.12It can be used with subagents when available, or as a checklist for the main13agent when no subagent tool exists.1415## Specialist Profiles1617Choose the smallest set:1819- architect: boundaries, dependency direction, module shape, migration seams;20- backend: APIs, domain logic, persistence, concurrency, errors;21- frontend: UI behavior, state, accessibility, visual quality;22- security: auth, authz, secrets, parser risk, supply chain;23- data: schemas, migrations, analytics, integrity, retention;24- DevOps: CI, deploy, runtime config, observability;25- QA: test plan, regression coverage, edge cases;26- docs: user-facing and operator-facing documentation;27- performance: evidence-led bottleneck analysis;28- product: user workflow, scope, acceptance criteria.2930## Dispatch Rules3132- Do not spawn a specialist without a concrete question.33- Give each specialist bounded files and expected output.34- Prefer read-only specialist review unless implementation ownership is clear.35- Use `agent-squad` when multiple specialists will work in parallel.36- Use `subagent-result-merge` to consolidate outputs.3738## Specialist Prompt Shape3940```markdown41Specialist:42Question:43Scope:44Allowed files:45Forbidden files:46Evidence required:47Expected output:48Validation:49```5051## Output5253Report:5455- selected specialists;56- why each was needed;57- scope boundaries;58- result or next routing skill.
Mesteriis