Skills warpdotdev common-skills Warp spec workflow

write-product-spec

Use it when:
You want a feature's behavior pinned down in writing before an agent builds it, as a product spec or PRD.
It does:
Asks you for missing context and for a Figma mock when there's UI, then writes the behavior as numbered rules that can each be tested.
You get:
specs/<id>/PRODUCT.md: a short summary and an exhaustive Behavior section, with no implementation details and no test plan.
Next step:
write-tech-spec, which plans the implementation and the tests from these rules.

Skill 2 of 5 in the Warp spec workflow bundle, after spec-driven-implementation and before write-tech-spec.

TL;DR

A product spec here describes behavior only from the side of whoever uses the feature: the person in the app, code reading a data model, callers of an API, or a developer running a CLI. It names no internal types, modules or algorithms. The Behavior section carries the spec: the happy path, every visible state and transition, all inputs, empty, error, loading and cancelled states, edge cases such as offline, timeouts, races and focus loss, keyboard and accessibility, and what must never regress. Everything else stays thin: a summary of one to three sentences, and Problem, Goals, Figma or Open questions only when they add something. Testing is left out on purpose; it belongs in TECH.md, which write-tech-spec writes from these rules. The folder is named after a Linear ticket, a GitHub issue or a short feature name, and a new ticket is filed only if you ask. Length follows the feature: no spec for trivial fixes, about 30 to 60 lines for a small feature. It's written for Warp, and its worked example specifies Markdown tables in Warp's block list.

Summarizes the skill at 8792394.

npx skills add https://github.com/warpdotdev/common-skills --skill write-product-spec
Total Downloads
28,900 on skills.sh, Nov 9, 2026
Repo stars
678 warpdotdev/common-skills
First seen
May 9, 2026 on skills.sh
Weekly Downloads
90
-86% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21648
Sep 28593
Oct 5944
Oct 12496
Oct 19375
Oct 26365
Nov 2121
Nov 990
Category

Make the agent question you and write the plan down before it writes code.

Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.

Type

A multi-step process the agent follows: interview, debug, run a TDD loop, review.

Effect

Its own steps create or change files, git state or local tools.

Needs

Instructions only. Works in any agent that supports skills.

Publisher

Everyone else. Unverified vendor claims default to community.

Topics

SKILL.md

No copy of its SKILL.md yet.