workflow

You can design complex automation workflows by defining them in a standardized .pmc/workflows directory structure, then using steps for mock generation, validation, testing, and registry registration to ensure repeatable deployments across Claude Code.

Workflow mock generation is supported as a dedicated step in the workflow lifecycle, allowing you to create mocks for shell, claude, and workflow states to validate multi-state automation behavior before registry deployment.

Yes, nested sub-workflows are supported to compose end-to-end automation, allowing you to combine multiple state types including shell, claude, and workflow states within a single standardized workflow definition.

The best way to manage workflow definitions across deployments is using a registry-driven structure in the .pmc/workflows directory, which supports local definitions alongside validation commands and registry updates for consistent behavior.

You can validate a workflow before registry registration by running the built-in validation commands on your workflow.json definition, ensuring the standardized structure and state configurations pass checks before deployment.

Inconsistent workflow behavior across deployments often occurs when definitions lack a standardized structure, which is solved by enforcing a .pmc/workflows directory format with registry-driven validation and registration steps.