mcpField
A
aem-workflow

aem-workflow

github.com/adobeDevelopment316997 installsUpdated today
Repository

About aem-workflow

aem-workflow is a skill that routes AEM Cloud Service workflow requests to specialist guidance for design, development, triggering, launchers, debugging, and triage. It also defines Cloud Service constraints and delegates broad requests to an orchestrator.

Key features

  1. 01Intent-based specialist routing
  2. 02Workflow model design guidance
  3. 03Custom process step development
  4. 04Workflow triggering and launcher setup
  5. 05Debugging and incident triage
  6. 06Cloud Service implementation constraints

Use cases

  1. 01Designing models with steps, splits, and variables
  2. 02Implementing a custom WorkflowProcess step
  3. 03Starting workflows or configuring launchers
  4. 04Investigating failed or stuck workflow instances

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/adobe/skills --skill aem-workflow

After installing, type/aem-workflowin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
workflow-debugging/
reference.md
workflow-development/references/workflow-development/
participant-step-patterns.md
process-step-patterns.md
variables-and-metadata.md
workflow-development/references/workflow-foundation/
api-reference.md
architecture-overview.md
cloud-service-guardrails.md
jcr-paths-reference.md
quick-start-guide.md
README.md
workflow-launchers/references/workflow-foundation/
api-reference.md
architecture-overview.md
cloud-service-guardrails.md
jcr-paths-reference.md
quick-start-guide.md
README.md
workflow-launchers/references/workflow-launchers/
condition-patterns.md
launcher-config-reference.md
workflow-model-design/references/workflow-foundation/
api-reference.md
architecture-overview.md
cloud-service-guardrails.md
jcr-paths-reference.md
quick-start-guide.md
README.md
workflow-model-design/references/workflow-model-design/
model-design-patterns.md
model-xml-reference.md
step-types-catalog.md
workflow-orchestrator/references/workflow-foundation/
api-reference.md
architecture-overview.md

Details

From the project README

AEM Cloud Service Workflow

Route user requests to the appropriate specialist skill based on intent.

Intent Router

User IntentSkillPath
Create a workflow model, add steps, design OR/AND splits, configure variablesModel Designworkflow-model-design/SKILL.md
Implement a custom WorkflowProcess step, ParticipantStepChooser, OSGi service registrationDevelopmentworkflow-development/SKILL.md
Start a workflow from code, HTTP API, Timeline UI, Manage PublicationTriggeringworkflow-triggering/SKILL.md
Configure a launcher, auto-start on asset upload, overlay OOTB launcherLaunchersworkflow-launchers/SKILL.md
Workflow stuck, failed step, missing Inbox task, stale instances, thread pool exhaustion, purgeDebuggingworkflow-debugging/SKILL.md
Classify a workflow incident, determine required logs, Splunk queries, data gathering checklistTriagingworkflow-triaging/SKILL.md
End-to-end lifecycle or requests spanning multiple concernsOrchestratorworkflow-orchestrator/SKILL.md

How to Use

  1. Match the user's request to one row in the Intent Router table above.
  2. Read the linked SKILL.md for that specialist skill.
  3. Follow the workflow, references, and output contract defined in that skill.
  4. For broad or ambiguous requests that span multiple concerns, use the Orchestrator which coordinates across all specialist skills and loads foundation references.

Cloud Service Constraints

ConstraintDetail
No JMXNo retryFailedWorkItems, countStaleWorkflows, restartStaleWorkflows, purgeCompleted via JMX
/libs is immutableNever write to /libs; use /conf/global/ or /apps/ overlays
Model design-time path/conf/global/settings/workflow/models/<id>
Model runtime path (for API calls)/var/workflow/models/<id>
Launcher config path/conf/global/settings/workflow/launcher/config/
Service usersAlways use workflow-process-service sub-service; never admin credentials
OSGi annotationsDS R6 (@Component, @Reference from org.osgi.service.component.annotations)
Deploy viaCloud Manager pipeline — no Package Manager in production

Specialist Skills

Comments

Markdown supported