sdd-propose

Create a structured change proposal by generating a Markdown file that defines intent, scope, approach, affected areas, risks, rollback plans, dependencies, and success criteria. This establishes a clear foundation for software architecture changes before development begins.

A software architecture change proposal should include sections for Intent, Scope (In/Out), Approach, Affected Areas, Risks, Rollback Plan, Dependencies, and Success Criteria. These structured sections ensure all necessary context is captured for change management.

Yes, proposal generation supports persistence to Engram or OpenSpec artifact stores based on configuration. This allows the generated Markdown proposals to be saved directly to your designated spec-driven development artifact storage.

The best way to document a feature request is generating a well-defined proposal document within a dedicated change directory. This proposal serves as the foundation for further design and development in spec-driven workflows.

No, this change management proposal tool requires no external dependencies. It operates independently using internal scripts to generate the structured Markdown files needed for your development workflow.

Generate a rollback plan when initiating any new feature request or software architecture change. The proposal structure includes a dedicated Rollback Plan section to ensure change management preparedness before development starts.