Solution Design

An instruction contract for guiding the engineering and design of new or existing software projects. It helps move from the problem and requirements to a verifiable design and a delivery plan, keeping documentation proportional to the project's size, complexity, risk, and way of working. Document types describe responsibilities; they do not imply that every type must become a separate file.

Activation Contract

Load this skill when the user:

• starts a new project or feature and needs to decide the design;
• asks to document architecture, data, API, requirements (PRD), decisions (ADR), or a delivery plan;
• asks for "software design", "PRD", "SDD", "design doc", "document the system", or similar;
• wants to align design with an existing repository.

Do not load for: writing code with no design decision to document, or PR reviews.

Hard Rules