Write Product Spec

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.

skills.sh installs: 28.9K
GitHub stars: 684
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add warpdotdev/common-skills --skill write-product-spec --agent claude-code

Installs into .claude/skills of the current project.

Files

write-product-spec

Write a PRODUCT.md spec for a significant feature in Warp.

Overview

The product spec should make the desired behavior unambiguous enough that an agent can implement it correctly and avoid regressions. Describe the feature purely from the user's perspective — what the user sees, does, and experiences, and the invariants that must hold for them. Do not include implementation details (internal types, state layout, module boundaries, data flow, algorithms).

"User" is not limited to the end user of the Warp app. It means whoever consumes the surface being designed:

For UI / UX features: the human using Warp.
For a data model: the code that reads and writes that model.
For an API, protocol, or library: the callers of that API — other services, client code, plugins, or agents.
For a CLI tool or developer-facing surface: the developer invoking it.

The spec should describe behavior from that consumer's perspective: the shape of the surface, the operations they can perform, what they see back, invariants they can rely on, and edge cases they must handle — without prescribing how the surface is implemented underneath.

SKILL.md on GitHub

Details

Repository: github.com/warpdotdev/common-skills
Categories: Git & Pull Requests, Documentation, Code Review & Quality, Productivity & Planning
First seen: May 16, 2026