sdd-propose

You can create a structured change proposal by generating a Markdown file that defines project modifications, including intent, scope, approach, affected areas, risks, and rollback plans. This clarifies communication and accelerates decision-making for new features.

Documenting software change scope and rollback plans in Markdown involves using predefined sections to capture intent, approach, and risks. This ensures all necessary information is clearly defined, reducing ambiguity for stakeholders reviewing the modifications.

Yes, you can update an existing proposal if the change directory already exists. The process supports iterative updates by reading the current Markdown document and applying modifications to the defined scope, approach, or rollback plans.

A software development proposal should include predefined Markdown sections for intent, scope, approach, affected areas, risks, and rollback plans. Structuring these elements ensures clear communication of project modifications and accelerates stakeholder decision-making.

Yes, the generated change proposal integrates with artifact store modes like engram and openspec. This compatibility ensures the structured Markdown documents fit seamlessly into established software development and change management workflows.

You need to draft a formal change proposal when a new feature request or project modification requires clear communication of intent, scope, and risks. Generating a structured Markdown document reduces ambiguity and formalizes the plan for stakeholders.