This generates PRODUCT.md specs for features in Warp, written purely from the user's perspective with no implementation details. The meat is the Behavior section: numbered, testable invariants covering happy paths, edge cases, empty states, errors, races, and anything else an implementer might not think to ask about. It asks for Figma links upfront if the feature has UI, routes specs into a structured directory by Linear ticket or GitHub issue, and keeps everything except Behavior deliberately thin. Worth knowing it's designed as step one of a two-step process: product spec first, then a companion tech spec. If you're defining behavior before cutting code or need to make a complex feature unambiguous enough to review, this is the format.
npx skills add https://github.com/warpdotdev/common-skills --skill write-product-spec