write-product-spec

To write a product spec for complex features, you define a standard structure covering the problem statement, goals, non-goals, UX details, success criteria, and validation. This ensures unambiguous expectations before implementation begins.

A PRODUCT.md file should include a summary, problem statement, goals, non-goals, UX references, success criteria, validation methods, and decisions. This structure defines feature behavior unambiguously for implementation and review.

You need a detailed product specification for significant, complex, or ambiguous features where written documentation improves implementation and review. It provides a canonical contract to guide development and define validation.

To document non-goals and edge cases in feature requirements, you follow a standard spec structure that explicitly separates what is out of scope. You can also add design references and track open questions for clarity.

The best way to validate feature behavior in a product spec is to define explicit success criteria and validation methods within the document. This creates a canonical contract that guides repo wrappers and ensures correct implementation.