skills.rest
Balthael
BalthaelCOMMUNITY
Explore all skills by this author →
GitHub

sdd-propose

Creates a structured change proposal document with intent, scope, capabilities, and rollback plan.

Updated Apr 10, 2026
Search Tags:#workflow#planning#sdd#spec-driven development#openspec#sub-agent#change proposal
One-click install
npx skills add https://github.com/Balthael/ciberbal-ai --skill sdd-propose-balthael
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/Balthael/ciberbal-ai/tree/main/internal/assets/skills/sdd-propose
Command: npx skills add https://github.com/Balthael/ciberbal-ai --skill sdd-propose-balthael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When starting a spec-driven development change, teams often skip structured planning and jump straight to code, losing track of intent, scope boundaries, and rollback strategy. This Skill produces a consistent proposal.md artifact that captures why a change is needed, what is in and out of scope, and which capabilities it affects. ## Core Features & Use Cases - Structured Proposal Generation: Produces a proposal.md with Intent, Scope, Capabilities, Approach, Affected Areas, Risks, Rollback Plan, Dependencies, and Success Criteria sections. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, writing to the filesystem, an Engram memory store, both, or returning inline only. - Capability Contract: Defines New and Modified Capabilities that act as the contract for the downstream sdd-spec phase, referencing existing specs in openspec/specs/. - Use Case: An orchestrator launches this sub-agent with a change name like "add-dark-mode" plus exploration analysis, and receives a concise proposal under 450 words ready for the spec and design phases. ## Quick Start Ask the orchestrator to create a proposal for a change named add-dark-mode using the exploration analysis from the previous phase.

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 change proposal in spec-driven development?▼

Launch the sdd-propose sub-agent with a change name and either exploration analysis or a direct description. It writes a proposal.md containing intent, scope, capabilities, approach, risks, rollback plan, and success criteria.

What sections should a software change proposal include?▼

This proposal template includes Intent, In/Out of Scope, New and Modified Capabilities, Approach, Affected Areas, Risks with mitigations, Rollback Plan, Dependencies, and Success Criteria. Every proposal must include a rollback plan and success criteria.

What is the difference between engram, openspec, and hybrid persistence modes?▼

Engram stores the artifact in a memory store under sdd/{change-name}/proposal, openspec writes proposal.md to the filesystem under openspec/changes/, and hybrid does both. The none mode returns the result inline without creating any files.

Does the proposal step create files in the openspec directory?▼

Only in openspec or hybrid mode does it create openspec/changes/{change-name}/proposal.md. In engram or none mode it never creates openspec directories unless the user explicitly requests file-based persistence.

Why must the Capabilities section be filled in the proposal?▼

The Capabilities section is the contract with the downstream sdd-spec agent. New capabilities become new spec files under openspec/specs/, while modified capabilities become delta specs, so the spec phase knows exactly which files to create or update.

What are the size limits for a change proposal?▼

The proposal artifact must stay under 450 words. It should use bullet points and tables rather than prose, keeping it a concise thinking tool rather than lengthy documentation.

Related Skills

Explore More Software Engineering Skills→
open-platform-modelopen-platform-model

openspec-explore

Guide problem exploration and requirement clarification with clarifying questions and ASCII diagrams.

Official
Intermediate
artagonartagon

openspec-sync-specs

Merge delta OpenSpec requirement changes into main capability specs.

Official
Intermediate
nico0695nico0695

sdd-explore

Inspects repository context and writes an explore.md discovery artifact for spec-driven development.

Community
Intermediate
striderZAstriderZA
72

quick-design

Generate lightweight design specifications for small game changes with acceptance criteria.

Community
Intermediate