sdd-propose

To create a structured change proposal for spec-driven development, you transform exploration conclusions into a document defining intent, scope, approach, risks, rollback, dependencies, and success criteria. This ensures your orchestrator pipeline retains full context for downstream phases.

Spec-driven development proposal persistence saves your change proposal artifacts so downstream pipeline phases can locate them. You need it when running an SDD orchestrator to prevent losing context between exploration and design phases across engram, openspec, hybrid, or none modes.

You write change proposals to openspec directories by generating a proposal markdown file at `openspec/changes/{change-name}/proposal.md`. This enforces persistence contracts so the orchestrator can automatically access the documented scope, risks, and approach.

Yes, you can use direct user intent instead of exploration output to generate an SDD proposal. The system digests direct change descriptions or exploration analysis to draft the required proposal, summarizing key problems, affected areas, and success criteria.

Yes, the SDD proposal phase supports Engram memory persistence by calling `mem_save` with a defined topic key and metadata. It honors engram, hybrid, and none modes, reading Engram observations when available to maintain pipeline context.

Generating change proposals without exploration output limits the context available for documenting intent and affected areas. You must manually provide direct change descriptions, which may increase the risk of missing implicit scope, dependencies, or rollback criteria typically identified during exploration.