workflow-orchestrator

Orchestrate end-to-end AEMaaCS Dispatcher lifecycle workflows across design, validation, and incident response.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/adobe/aem-auth-demo --skill workflow-orchestrator-adobe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-orchestrator
Source: https://github.com/adobe/aem-auth-demo/tree/main/.agents/skills/workflow-orchestrator
Command: npx skills add https://github.com/adobe/aem-auth-demo --skill workflow-orchestrator-adobe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates end-to-end Dispatcher lifecycle work for AEMaaCS cloud deployments, coordinating design, implementation, validation, release readiness, and incident troubleshooting.

Core Features & Use Cases

  • End-to-end Dispatcher lifecycle orchestration across design, config, validation, and rollout.
  • Playbook-driven workflows that coordinate config-authoring, technical-advisory, security-hardening, performance-tuning, and incident-response tasks.
  • Consolidated outputs including touched files, evidence, risk, rollback triggers, and next steps.

Quick Start

Choose a matching playbook and run the MCP command chain to begin end-to-end Dispatcher orchestration.

Frequently Asked Questions about workflow-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate end-to-end Dispatcher lifecycle work for AEMaaCS cloud deployments?

Orchestrating end-to-end Dispatcher lifecycle work for AEMaaCS involves coordinating design, config-authoring, validation, and rollout using playbook-driven workflows that consolidate touched files, evidence, and rollback triggers.

What static checks and runtime traces are available for AEM Dispatcher validation?

AEM Dispatcher validation supports static checks like validate and lint, plus runtime traces including trace_request, inspect_cache, monitor_metrics, and tail_logs to gather evidence for cloud-mode validation.

Does this Dispatcher orchestration approach support security hardening and performance tuning?

Dispatcher orchestration supports security hardening and performance tuning through dedicated playbooks, coordinating technical advisory and config-authoring tasks to ensure release readiness across AEMaaCS cloud deployments.

How do I troubleshoot AEM Dispatcher incidents using runtime traces?

Troubleshooting AEM Dispatcher incidents uses incident-response playbooks that execute runtime traces like tail_logs and inspect_cache, gathering evidence to resolve issues and manage rollback triggers during cloud deployments.

What do I need to run cloud-mode validation for AEM Dispatcher configurations?

Cloud-mode validation for AEM Dispatcher requires meeting the MCP tool contract core-7-tools, executing static checks and runtime traces as evidence within playbook-driven workflows for AEMaaCS release readiness.