What problem does it solve? Turning a rough feature idea or exploration analysis into a well-structured change proposal is slow and inconsistent. This Skill standardizes the proposal phase of spec-driven development by generating a concise proposal.md with intent, scope, capabilities, risks, and success criteria. ## Core Features & Use Cases - Structured Proposal Generation: Produces a proposal.md with Intent, Scope, Capabilities, Approach, Affected Areas, Risks, Rollback Plan, and Success Criteria sections. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, writing to openspec/changes/ or an Engram store as configured. - Interactive Question Round: Offers a proposal-shaping question round covering business rules, edge cases, and scope boundaries before finalizing. - Use Case: After exploring a codebase for a new dark-mode feature, delegate to this Skill to produce a proposal defining which capabilities are new or modified, so the sdd-spec phase knows exactly which spec files to create. ## 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.
