sdd-specify

To create a structured feature specification, you need to capture user intent and requirements through targeted questions, identify unknowns, perform research if needed, and generate a formal specification document defining the new functionalities before development begins.

Capturing intent for new app functionalities requires clarifying the user's goals via specific questions, identifying technical unknowns, and integrating research findings to ensure complete clarity and scope definition before writing the final specification document.

Specification generation fits into product development workflows by reading existing constitutions, determining spec IDs, and producing structured specification documents that outline user needs and scope, ensuring implementation clarity and reducing development friction.

Yes, an existing constitution document is required because the feature specification process involves reading the current constitution to determine spec IDs and align the new requirements gathering with established project guidelines before generating the final spec.

Yes, you can integrate research findings directly into the feature specification because the workflow explicitly identifies unknowns during requirements gathering and performs necessary research to incorporate those findings into the final specification document.

You should avoid automated specification generation for product development when a feature's purpose and scope are already fully defined, or when the workflow lacks an existing constitution to read and determine spec IDs from, making intent capture unnecessary.