sdd-propose

Generate structured change proposal documents from exploration analysis or user input.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/adacosdev/dotfiles --skill sdd-propose-adacosdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/adacosdev/dotfiles/tree/main/dot_config/opencode/skills/sdd-propose
Command: npx skills add https://github.com/adacosdev/dotfiles --skill sdd-propose-adacosdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of a structured change proposal from exploration analysis or direct user input, streamlining governance and documentation.

Core Features & Use Cases

  • Generates a markdown proposal containing intent, scope, approach, risks, rollback, and success criteria.
  • Handles multiple persistence modes (engram, openspec, hybrid, none) and coordinates artifact persistence accordingly.
  • Supports integration with a change orchestration workflow by producing the required files in the designated change folder.

Quick Start

Trigger the orchestrator with a change name and exploration analysis to generate a proposal.

Frequently Asked Questions about sdd-propose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the creation of a structured change proposal document?

Automating change proposal creation involves using exploration analysis or direct user input to generate a markdown document with intent, scope, approach, risks, rollback, and success criteria sections.

What sections should a comprehensive change management proposal include?

A comprehensive change management proposal should include dedicated sections for intent, scope, approach, risks, rollback plan, and success criteria to ensure proper governance and structured documentation.

How do I generate a change proposal that supports different persistence modes?

To generate a proposal with specific persistence modes, you can configure the workflow to handle engram, openspec, hybrid, or none modes, ensuring the generated artifacts are saved according to the selected persistence configuration.

Can I use exploration analysis directly to draft a rollback plan and risk assessment?

Yes, you can feed exploration analysis directly into the workflow to automatically draft a complete proposal that outlines potential risks, a rollback plan, and success criteria alongside the intended change scope.

Does the change proposal workflow integrate with existing change orchestration systems?

Yes, the proposal workflow supports integration with change orchestration by producing the required markdown files and coordinating artifact persistence directly within your designated change folder.

What is the best way to structure software change proposals for governance documentation?

The best way to structure software change proposals for governance is to standardize the documentation into specific sections: intent, scope, approach, risks, rollback plan, and success criteria, which this workflow automates.