Adobe Dispatcher Workflow Orchestrator (AMS)
Use this skill when users need end-to-end Dispatcher support instead of a single specialist workflow.
Scope
- Full lifecycle orchestration for AMS Dispatcher work:
- requirements and design
- config implementation and hardening
- static/runtime validation
- release readiness and rollback planning
- production incident triage
Routing Model
- Start in
config-authoringfor file design and edits. - Pull in
technical-advisoryfor policy, documentation, and evidence planning. - Pull in
security-hardeningandperformance-tuningfor non-functional risk checks. - Switch to
incident-responsefor live failures or regressions. - Return a single consolidated output: changes, evidence, risk, rollback, and follow-ups.
Operational Packaging
Use these shared references to keep broad requests deterministic:
- Start with quick-start-execution-path.md when the user is new, the repo root is ambiguous, or the request spans multiple concerns.
- Normalize the repo to a dispatcher
srcroot with repo-layout-workflows.md. - Convert the chosen specialist playbook into exact MCP commands with playbook-command-linkage.md.
- Use the specialist skill references only after the path above is fixed.
Entry Criteria
Use when user intent is any of:
- end-to-end implementation
- pre-release readiness review
- troubleshooting + fix + re-validation in one flow
- broad audit across config, security, and performance
Exit Criteria
Always return:
- touched files and why
- executed checks (static + runtime) and evidence
- unresolved risks/gaps
- rollback trigger + rollback action
- next-step plan if prerequisites blocked verification