What problem does it solve? When starting a software change, teams often skip structured planning and jump straight to code, leading to unclear scope, missed risks, and no rollback strategy. This Skill produces a standardized proposal.md document that captures intent, scope, approach, affected areas, risks, and success criteria before any implementation begins. ## Core Features & Use Cases - Structured Proposal Generation: Produces a proposal.md with intent, in/out of scope, technical approach, affected areas, risk table, rollback plan, dependencies, and success criteria. - Multi-Mode Persistence: Stores the proposal in Engram memory (mem_save with topic_key upserts), the openspec/ filesystem, both (hybrid), or returns it inline (none), depending on the artifact store mode. - Pipeline Integration: Consumes exploration analysis from sdd-explore, reads the project skill registry, and hands off to downstream phases like sdd-spec and sdd-design. - Use Case: An orchestrator launches this sub-agent with a change name like "add-dark-mode" plus exploration findings; it returns a concise proposal with a risk level and a structured envelope for the next pipeline phase. ## Quick Start Ask the orchestrator to create a proposal for your change, for example: create an SDD proposal for the change named add-dark-mode using the exploration results.
