sdd-propose

Creates structured SDD change proposals with intent, scope, capabilities, and rollback plans.

Updated May 24, 2026
One-click install
npx skills add https://github.com/etrigan16/v0-cipher-ar --skill sdd-propose-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/sdd-propose
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill sdd-propose-etrigan16

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns exploration analysis or raw user input into a structured, reviewable change proposal document, ensuring every spec-driven development change starts with clear intent, scope boundaries, risks, and success criteria. ## Core Features & Use Cases - Structured Proposal Generation: Produces a proposal.md with intent, in/out scope, capabilities contract, approach, affected areas, risks, rollback plan, and success criteria. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, writing to openspec/changes/ or an Engram topic as configured. - Interactive Question Round: Runs a proposal-shaping question round covering business rules, edge cases, and tradeoffs before finalizing the document. - Use Case: After exploring a codebase for a new dark-mode feature, the orchestrator delegates to this sub-agent to produce a concise proposal under 450 words that the sdd-spec agent can consume as a capabilities contract. ## Quick Start Ask the orchestrator to create an SDD proposal for your change, for example: create a proposal for the add-dark-mode change based on the exploration analysis.

Frequently Asked Questions about sdd-propose

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

FAQPage Schema
How do I create an SDD change proposal?▼

Delegate to 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 is the Capabilities section in an SDD proposal?▼

The Capabilities section is the contract between the proposal and specs phases. It lists new capabilities that become full spec files and modified capabilities that become delta specs, telling the sdd-spec agent exactly which specs to create or update.

Does sdd-propose always create files in openspec/changes?▼

No. File creation depends on the artifact store mode: openspec and hybrid modes write proposal.md to openspec/changes/, engram mode persists to an Engram topic, and none mode returns the result inline without touching the filesystem.

Why must the proposal stay under 450 words?▼

The size budget keeps the proposal a concise thinking tool rather than lengthy documentation. Bullet points and tables are preferred over prose so downstream agents can parse the contract quickly.

Can the orchestrator run sdd-propose instructions inline?▼

No. The skill has an orchestrator gate requiring delegation to the dedicated sdd-propose sub-agent via the platform's task or sub-agent primitive. Only the executor sub-agent runs the phase steps.