sdd-propose

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

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-propose-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-propose
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-propose
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-propose-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents often jump straight into implementation without a documented rationale, scope boundary, or rollback strategy. This Skill enforces a spec-driven development discipline by generating a structured proposal.md artifact that captures intent, scope, capabilities, risks, and success criteria before any code is written. ## 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 Engram topics, openspec/changes directories, or returning inline results. - Interactive Proposal Shaping: Runs a product question round covering business rules, edge cases, and tradeoffs before finalizing the proposal. - Use Case: An orchestrator agent receives a request to add dark mode; it delegates to this Skill, which produces a concise proposal under 450 words defining the new capability contract that downstream spec and design agents consume. ## Quick Start Delegate a change proposal to the sdd-propose sub-agent with the change name and exploration analysis to generate a structured proposal.md.

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 with an AI agent?▼

Delegate the change name and exploration analysis to the sdd-propose sub-agent, which writes a proposal.md with intent, scope, capabilities, risks, and rollback plan. The orchestrator must delegate rather than execute the skill inline.

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

Engram mode saves the proposal as an Engram topic under sdd/{change-name}/proposal without touching the filesystem. Openspec mode writes proposal.md into openspec/changes/{change-name}/, while hybrid mode does both.

Can the orchestrator run the sdd-propose skill directly?▼

No. The skill has an orchestrator gate requiring delegation to a dedicated sdd-propose sub-agent via task() or equivalent primitives. Only the executor sub-agent runs the phase instructions.

What sections must an SDD proposal include?▼

Every proposal requires intent, in/out scope, a capabilities section (new and modified), approach, affected areas, risks, rollback plan, dependencies, and success criteria. The capabilities section is the contract consumed by the sdd-spec phase.

What are the size limits for a generated proposal?▼

The proposal artifact must stay under 450 words, using bullet points and tables instead of prose. It is a concise thinking tool, not a long-form document.