sdd-propose

You can generate a structured architectural change proposal by providing a change name and short description. The resulting scaffold defines intent, scope, approach, risks, rollback, and success criteria in a consistent format for reviewable architectural changes.

An architectural change proposal standardizes the documentation of intent, scope, and approach for system modifications. You need one during design phases to ensure traceable, reviewable changes that prevent verbose, inconsistent architectural documentation.

Yes, change proposals can persist directly to Engram or OpenSpec backends depending on your selected mode. Hybrid mode also supports writing the architectural change documentation directly to the filesystem for offline review.

You standardize architectural documentation by generating a structured proposal scaffold. This enforces a consistent format that captures intent, scope, approach, affected areas, risks, rollback, and success criteria for every architectural change.

The best way to ensure traceable architectural changes is to generate structured proposals during exploration or design phases. This standardizes scope and approach documentation, making modifications reviewable and persistent across Engram or OpenSpec backends.

Generating an architecture proposal requires only a change name and a short description as input. The system uses this minimal input to generate a full structured scaffold ready for review, capturing intent, scope, and validation criteria.