sdd-propose

Generate an SDD change proposal document from a change name and exploration analysis.

2|Updated Jul 29, 2025

Search Tags:#architecture #sdd #change management #capabilities #proposal #spec contract #risk planning

Ready to run

npx skills add https://github.com/kurojs/EnderDots --skill sdd-propose-kurojs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents ambiguous change planning by producing a structured SDD change proposal that clearly states intent, scope, capabilities, approach, risks, and how success is measured.

Core Features & Use Cases

Change proposal authoring: Creates a proposal.md artifact for a specific change name, suitable for downstream specs work.
Mode-aware persistence: Supports engram, openspec, hybrid, and none so you can choose whether it writes to filesystem or only returns output.
Contract with spec generation: Forces the Capabilities section to be filled so the next phase can reliably create or update spec files.

Quick Start

Ask the AI to create an SDD change proposal for change name "add-dark-mode" and persist it as an openspec artifact.

Frequently Asked Questions about sdd-propose

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

FAQPage Schema

What is an SDD change proposal and when do I need one?▼

An SDD change proposal is a structured document stating change intent, scope, capabilities, approach, risks, and success metrics. You need one during architecture workflow phases to prevent ambiguous change planning before creating downstream spec files.

How do I generate a proposal.md file for a spec-driven development workflow?▼

Provide a change name and exploration analysis to generate a proposal.md artifact. The output is persisted under sdd/{change-name}/proposal or openspec/changes/{change-name}/proposal.md, establishing a clear contract for subsequent spec generation.

Can I use SDD proposals with different persistence modes like engram or openspec?▼

Yes, SDD proposals support engram, openspec, hybrid, and none persistence modes. You can choose to write the proposal artifact to the filesystem or only return the output in the completion envelope based on your workflow.

Does the SDD proposal process require existing spec files to work?▼

No, the proposal generation optionally reads existing specs. It requires YAML-frontmatter discovery metadata and a change name, but it can produce a structured proposal document independently before any downstream specs are created or updated.

What limitations exist when authoring architecture change proposals?▼

The main constraint is that the Capabilities section must be filled to ensure the next phase can reliably create or update spec files. Without this forced contract, downstream spec generation from the proposal artifact would fail.