sdd-propose

Generate structured change proposals with standardized sections to proposal.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a structured change proposal from exploration analysis or user input, streamlining change management.

Core Features & Use Cases

  • Generate a standardized proposal with sections for Intent, Scope, Approach, Risks, Rollback Plan, and Success Criteria.
  • Persist the proposal to openspec/changes/{change-name}/proposal.md.
  • Update existing proposals when re-run to reflect new analysis.

Quick Start

Provide the change name and the exploration analysis to generate a proposal.md in the designated change folder.

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 the change name and exploration analysis. The tool outputs a standardized proposal.md file with sections for Intent, Scope, Approach, Risks, Rollback Plan, and Success Criteria.

What is the best way to standardize change management documentation for a new project?

Standardizing change management documentation requires enforcing a consistent format for every request. This skill automates structuring proposals into sections like Intent, Scope, Approach, Affected Areas, Risks, Rollback Plan, and Success Criteria.

Can I update an existing proposal.md file if my analysis changes?

Yes, you can update an existing proposal. Re-running the process with new exploration analysis automatically updates the existing proposal.md in the designated openspec/changes folder to reflect the latest findings.

How do I include a rollback plan and success criteria in my change request documentation?

To include a rollback plan and success criteria, use an automated proposal generator. It structurally enforces these specific sections within the change proposal.md file alongside Intent, Scope, Approach, and Risks.

Does this proposal generation tool work without any external dependencies?

Yes, this proposal generation tool works without external dependencies. It directly processes your provided change name and analysis input to create the structured proposal.md file in your local openspec directory.