sdd-propose

To create a change proposal, provide the change name and exploration notes to generate a structured proposal.md. This document includes Intent, Scope, and Approach sections to guide implementation and governance.

The openspec convention requires storing change proposals at openspec/changes/{change-name}/proposal.md. This ensures consistency with artifact storage and review workflows for engineering change requests.

Yes, a generated change proposal validates and includes rollback plans, success criteria, and dependency references. These elements enable safe, auditable changes during engineering change management.

You can convert exploration analysis or user input directly into a structured proposal document. The output applies openspec conventions to produce a formal proposal.md with all required governance sections.

The best way to document change dependencies and scope is using a structured proposal format. This approach respects openspec conventions and validates rollback plans alongside dependency references for auditable governance.

You need a formal proposal document when managing engineering change requests that require rollback plans, success criteria, and dependency references. It converts exploration analysis into auditable artifacts for safe implementation.