sdd-propose

Create structured SDD change proposals with intent, scope, and approach.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/Codenburg/skills --skill sdd-propose-codenburg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/Codenburg/skills/tree/main/sdd-propose
Command: npx skills add https://github.com/Codenburg/skills --skill sdd-propose-codenburg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need for a structured approach to creating Software Design Documentation (SDD) change proposals, ensuring clear intent, scope, and approach.

Core Features & Use Cases

  • Structured Proposal Creation: Guides the user through creating a structured proposal.md document with intent, scope, and approach.
  • Interactive Mode: Offers interactive questions to refine the proposal by uncovering business rules, implications, and product tradeoffs.
  • Execution and Persistence: Handles artifact persistence based on the mode (engram, openspec, hybrid, none) and ensures the proposal is created in the appropriate location.
  • Proposal Review: Provides a summary of the created proposal, including intent, scope, approach, and risk level, ready for the next phase (specs or design).

Quick Start

Create an SDD change proposal using the 'sdd-propose' skill by executing the 'orchestrator' role and providing the necessary change details.

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 software design documentation change proposal?

To create a software design documentation change proposal, you can use an automated skill to generate a structured proposal.md document. It guides you through defining the intent, scope, and approach for your proposed software changes.

What is the best way to refine business rules and product tradeoffs for a software design proposal?

The best way to refine business rules and product tradeoffs is through an interactive proposal shaping mode. It asks targeted questions to uncover implications and ensure your software design documentation captures all necessary context.

How does artifact persistence work for SDD proposals across different modes?

Artifact persistence for SDD proposals works by saving the generated proposal document based on your selected mode, such as engram, openspec, hybrid, or none. This ensures the structured documentation is created in the appropriate location.

Can I generate a summary for a software design proposal ready for the specs phase?

Yes, you can generate a summary for a software design proposal ready for the specs phase. The summary includes the intent, scope, approach, and risk level, providing a clear review before moving to the next stage.

Do I need to delegate execution to a sub-agent for SDD proposal creation?

Yes, you need to delegate execution to the sdd-propose sub-agent to create SDD proposals. This delegation handles the interactive proposal shaping, artifact persistence, and summary generation required for the change management process.