sdd-propose

Generate structured change proposals with rollback plans and success criteria.

Updated Nov 19, 2024

Search Tags:#automation #documentation #openspec #proposal #change-management #change-name #persistence-contract

Ready to run

npx skills add https://github.com/Strocs/.dotfiles --skill sdd-propose-strocs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/Strocs/.dotfiles/tree/main/.config/opencode/skills/sdd-propose
Command: npx skills add https://github.com/Strocs/.dotfiles --skill sdd-propose-strocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create structured change proposals from exploration findings or direct user input, enabling consistent governance and faster decision-making.

Core Features & Use Cases

Automates the generation of a proposal.md from a change name and associated analysis.
Supports multiple persistence modes (engram, openspec, none) per orchestration rules.
Produces a complete proposal with sections for Intent, Scope, Approach, Risks, Rollback, and Success Criteria.

Quick Start

Provide a change name and exploration analysis to generate a proposal.md placed under openspec/changes/{change-name}.

Frequently Asked Questions about sdd-propose

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

FAQPage Schema

How do I generate a structured change proposal from exploration analysis?▼

To generate a structured change proposal, provide a change name and exploration analysis to automatically create a formal proposal.md under openspec/changes/{change-name} with sections for Intent, Scope, Approach, Risks, Rollback, and Success Criteria.

What is the best way to automate change management documentation for openspec?▼

Automating change management documentation involves applying orchestration rules to adapt persistence modes like engram, openspec, or none, ensuring the generated proposal adheres to the selected persistence contract.

What sections should be included in a formal change proposal for rollback planning?▼

A formal change proposal must include explicit sections for Intent, Scope, Approach, Risks, Rollback, and Success Criteria to ensure complete governance and faster decision-making.

Can I use direct user input instead of exploration findings to create a proposal.md?▼

Yes, you can use direct user input to create a proposal.md, allowing you to turn exploration findings or immediate requests into actionable change proposals with consistent governance.

Does the generated proposal support multiple persistence modes?▼

The generated proposal supports multiple persistence modes including engram, openspec, and none, adapting to the orchestrator's selected persistence contract.

When do I need to use a persistence contract for change proposals?▼

You need a persistence contract for change proposals when applying orchestration rules to ensure the output adheres to the selected mode and maintains consistent governance across the documentation lifecycle.