sdd-propose

To create a structured change proposal, you can automate the generation of documents that define the intent, scope, and approach of changes. This ensures consistent technical communication for follow-on development and testing.

Spec-driven development uses structured documentation to manage project changes. It automates creating change proposals that outline the intent, scope, and approach, providing clear guidance for subsequent development and testing tasks.

You can automate change proposal creation by launching this skill to generate structured documents based on provided feature analysis or user input, defining the change intent, scope, and approach for your project.

No specific dependencies are required to define change scope using this approach. It operates independently to generate structured change proposals, outlining the intent, scope, and approach for proposed project changes.

The best way to document technical changes is by generating a structured change proposal. This approach clearly defines the intent, scope, and approach of the change, providing explicit guidance for follow-on development and testing.

You need a formal change proposal in a spec-driven pipeline when introducing a new feature or enhancement. It automates the documentation of the change's intent, scope, and approach to guide follow-on development and testing.