sdd-propose

Generate structured change proposals with Intent, Scope, and Approach sections.

Updated Jun 22, 2024
One-click install
npx skills add https://github.com/KilloconQ/dotfiles --skill sdd-propose-killoconq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/KilloconQ/dotfiles/tree/main/opencode/.config/opencode/skills/ssd-propose
Command: npx skills add https://github.com/KilloconQ/dotfiles --skill sdd-propose-killoconq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of structured change proposals from exploration analysis or direct user input, organizing them into a proposal.md inside the change folder.

Core Features & Use Cases

  • Automated proposal drafting: Generate a complete proposal document with sections like Intent, Scope, Approach, and Risks.
  • Openspec workflow support: Aligns with OpenSpec's change-management workflow and can read existing specs to inform proposals.
  • Guided execution: Provides step-by-step steps to create the proposal directory, read specs, and persist the proposal according to configuration.

Quick Start

Create a new change proposal by providing the change name and a brief exploration description.

Frequently Asked Questions about sdd-propose

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

FAQPage Schema
How do I create a structured change proposal from exploration analysis?

To create a structured change proposal, you provide a change name and exploration analysis to generate a proposal.md with sections for Intent, Scope, Approach, rollback plans, and success criteria.

What is a change proposal document for product and infrastructure updates?

A change proposal document formalizes product updates, infrastructure changes, and compliance tasks by defining Intent, Scope, and Approach to streamline coordination across teams.

How does OpenSpec workflow support work for change management?

OpenSpec workflow support aligns change proposals with existing specs by reading them to inform the proposal and persisting the output according to configured OpenSpec persistence modes.

Do I need existing specs to generate a change proposal?

You do not need existing specs to generate a change proposal, as you can provide direct user input and a brief exploration description to draft the document from scratch.

Can I use this for compliance tasks requiring formal documentation?

Yes, you can use this for compliance tasks requiring formal documentation, as it produces a structured proposal.md that enforces rollback plans and success criteria for coordinated compliance changes.