sdd-propose

To create a structured change proposal, provide the change description and scope details. The skill parses user input and existing documentation to produce comprehensive markdown content defining scope, risks, dependencies, and success criteria.

Documenting scope and risks for a process improvement proposal involves converting exploration analysis into standardized documents. This ensures scope, approach clarity, dependencies, and success criteria are clearly defined for easy review.

Yes, you can generate proposal documentation from existing project artifacts. The skill supports integration with existing specifications and project management workflows by parsing current documentation to ensure completeness.

Yes, the change proposal generator works without additional dependencies. It operates standalone using provided scripts and references to parse user input and output standardized markdown proposal content.

You need a structured proposal for change management when a product team submits a new feature change or technical upgrade. It reduces manual effort by generating the detailed documentation required for efficient review and approval.

Manually created change proposals often miss key dependencies and success criteria due to inconsistent formatting. Using a structured proposal generator standardizes documentation to ensure all scope, risks, and success criteria are explicitly defined.