change-orchestration

To manage multi-item software changes, route actions to phase-specific sub-files that handle spec review, planning, implementation, and verification, enforcing gating and auditability across all items.

Yes, change orchestration supports both interactive and external-spec workflows by applying shared validation, status checks, and phase gating to ensure safe progression and auditability.

The best way to track progress across architecture evolutions is using a structured change orchestration workflow that enforces phase gating, routes actions to specific operations, and manages artifacts for end-to-end coordination.

You create a new feature workflow by initializing the process with a command like /sdd-run change create --type feature --name sample-feature, which sets up the structured change orchestration lifecycle.

Yes, change orchestration enforces gating before implementation by performing shared validation and status checks, ensuring safe progression through spec review and planning phases before execution.