What problem does it solve? Turning a vague feature idea into a structured, reviewable change proposal is slow and inconsistent. This Skill generates a standardized proposal.md document capturing intent, scope, capabilities, risks, and rollback plans so teams can align before writing specs or code. ## Core Features & Use Cases - Structured Proposal Generation: Produces a proposal.md with intent, in/out scope, capabilities, approach, affected areas, risks, rollback plan, and success criteria. - Interactive Question Rounds: Runs product-focused question rounds to uncover business rules, edge cases, and scope boundaries before finalizing the proposal. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact storage modes, writing to openspec/changes/ or an Engram store as configured. - Use Case: After exploring a codebase for a dark-mode feature, delegate to this Skill to produce a concise proposal defining new and modified capabilities that downstream spec and design agents consume. ## 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.
