sdd-propose

You can automate structured change proposals by providing a change name and exploration context to generate openspec proposal documents. The output enforces standardized sections including Intent, Scope, Approach, Affected Areas, Risks, Rollback, Dependencies, and Success Criteria.

A structured change proposal for change management should include Intent, Scope, Approach, Affected Areas, Risks, Rollback, Dependencies, and Success Criteria sections. This standardized structure ensures comprehensive documentation for software development workflows.

You can create an openspec proposal by providing your exploration analysis or user input along with a change name. The automation processes your context and writes the structured proposal directly to openspec/changes/{change-name}/proposal.md.

The openspec proposal generator adapts to persistence conventions defined in skills/_shared/persistence-contract.md and follows standards in skills/_shared/openspec-convention.md. These shared contracts ensure consistent document generation and storage.

Yes, you can generate change management documents without manual formatting by supplying a brief exploration context. The automation enforces the standardized structure with all required sections—Intent, Scope, Approach, Risks, and others—automatically.