sdd-propose

To generate a structured change proposal, you need to document the intent, scope, approach, risks, and rollback plans. This skill automates that process by creating a structured markdown file outlining the technical plan within a specified change directory.

A technical change proposal draft should include the project intent, scope, implementation approach, affected areas, potential risks, and rollback plans. This ensures all necessary components for clear documentation of the proposed software changes are defined.

Yes, you can use openspec conventions to persist change proposal artifacts. The proposal generation process supports artifact persistence through openspec or engram conventions to maintain documentation continuity.

To document rollback plans and risks when proposing a new feature, you outline the technical plan and potential failure points. This skill automatically generates a draft proposal document integrating these critical risk management and rollback strategy sections.

Yes, the proposal generation tool integrates with existing software specifications. It uses dependency management to incorporate exploration analysis and current specifications directly into the generated change proposal document.

You need to draft a formal change proposal in software development when a new feature is proposed or significant modifications are planned. It streamlines the creation of structured documentation to ensure the technical plan and affected areas are clearly defined.