What problem does it solve? Teams often jump from a change's intent straight into code without settling the approach, leaving design decisions implicit, unrecorded, and impossible to review later. This skill structures the design stage of a change: it explores the genuine decisions, settles the approach with the user (or autonomously), and records the frozen design on the DefProd change record. ## Core Features & Use Cases - Decision-space exploration: Identifies genuine decisions (data model, API shape, UI placement, migrations) with options, recommendations, and trade-offs for each. - Adaptive discussion depth: Proposes quick-confirm, walk-the-decisions, or exhaustive discussion tiers, with risk-assessment floors that prevent high-risk changes from being rubber-stamped. - Change-record integration: Stamps the design stage via startChangeStage/finishChangeStage, writes the design to the record or a designDocPath pointer, and caps commit trailers with a stage ceiling for interim design-doc commits. - Use Case: A developer starts work on a billing-related change. The skill reads the change's intent, sees a high risk assessment, walks each design decision with the user, and records the agreed design on the change record before any code is written. ## Quick Start Ask the agent to design the current change, for example: "Run the design stage for this change and record the agreed approach on the change record."
