skills.rest
sebasmzg
sebasmzgCOMMUNITY
Explore all skills by this author →
GitHub

sdd-propose

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

Updated Mar 15, 2026
Search Tags:#architecture#documentation#openspec#proposal#software-design#change-management#engram
One-click install
npx skills add https://github.com/sebasmzg/sebas.dot --skill sdd-propose-sebasmzg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/sebasmzg/sebas.dot/tree/main/.config/opencode/skills/sdd-propose
Command: npx skills add https://github.com/sebasmzg/sebas.dot --skill sdd-propose-sebasmzg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns exploration analysis or user input into a concise, structured change proposal and ensures the resulting artifact is persisted in the project's expected backend so downstream SDD pipeline stages can find and use it.

Core Features & Use Cases

  • Structured proposal generation: Produces intent, scope, approach, affected areas, risks, rollback plan, dependencies, and success criteria as a focused proposal.md.
  • Multi-backend persistence: Supports Engram upserts, openspec filesystem files, or hybrid persistence with clear rules for when and how to save.
  • Registry and idempotency: Loads the skill registry to discover related skills and reads existing proposals to update rather than duplicate, preserving pipeline continuity.
  • Use Case: Create or update a proposal for a change like add-dark-mode using prior exploration analysis and persist it so sdd-spec can continue.

Quick Start

Create a concise proposal for the change named add-dark-mode using available exploration analysis and persist it according to the project's artifact mode.

Frequently Asked Questions about sdd-propose

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

FAQPage Schema
How do I draft a structured software change proposal for a new feature?▼

Draft a software change proposal by generating structured sections for intent, scope, approach, affected areas, risks, rollback plan, dependencies, and success criteria from exploration analysis or direct input.

What is the best way to document software architecture changes before implementation?▼

Documenting software architecture changes involves creating a concise proposal that defines the approach, affected areas, and rollback plan, ensuring downstream pipeline stages can use the artifact for further specification.

How do I persist change management proposals to Engram or openspec backends?▼

Persist change management proposals by applying upsert behavior to save artifacts directly into Engram, openspec filesystem files, or a hybrid backend, ensuring the proposal is accessible for downstream stages.

Can I update an existing proposal instead of creating a duplicate when refining a software design?▼

You can update an existing proposal without duplicating it by reading current artifacts and applying upsert behavior, which preserves pipeline continuity and registry idempotency during change workflows.

What should a software design proposal include for architectural changes like adding dark mode?▼

A software design proposal for changes like adding dark mode should include intent, scope, approach, affected areas, risks, rollback plan, dependencies, and success criteria to satisfy project change workflow requirements.

Related Skills

Explore More Software Engineering Skills→
maxculen86maxculen86

sdd-propose

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

Community
Advanced
lleontor705lleontor705
1

draft-proposal

Convert exploration analysis into a structured SDD change proposal.

Community
Intermediate
oteroweboteroweb

sdd-design

Generate formal architecture design documents from change proposals.

Community
Advanced
a53alia53ali

architecture-decision-record

Write, update, and query Architecture Decision Records using Markdown templates.

Community
Intermediate