write-product-spec: a Claude Code skill by Warp
For teams that want a behavior-first PRODUCT.md spec written before a feature is built. Skip it if the change is a small fix or you need a technical design doc.
- Score
- 68of 100
- Rank
- #194of 239
- Installs
- 29Kon skills.sh
- Security
- Mixed 3 scanners
- Updated
- 2026
- Context
- ~97tokens always
Install
npx skills add https://github.com/warpdotdev/common-skills --skill write-product-spec Run it in your terminal. View the source
Using the Claude app rather than Claude Code? You can add a skill there too. How to add it in the app
What does write-product-spec do?
write-product-spec is a skill from Warp that writes a PRODUCT.md for a significant feature under specs/<id>/, where the id is a Linear ticket, a GitHub issue or a short feature name. It describes the feature only from the consumer's side, whether that is a person using the UI, a developer calling an API or code reading a data model. Claude gathers missing context with questions and asks whether a Figma mock exists for visual work. The core is a Behavior section of numbered, testable invariants covering states, errors, edge cases, focus and accessibility. Implementation and test plans are left to a companion TECH.md from write-tech-spec.
When should you use write-product-spec?
Use it when
- A feature's behavior is unclear before coding starts
- You want an agent to implement from a written spec
- You need a PRD with edge cases listed
Skip it when
- The change is a trivial fix or UI tweak
- You need implementation details or test plans
What it needs and what it can touch
You need
- Linear MCP or the gh CLI, only to create new tickets
What it can do
- Writes spec files to your project
- Creates a Linear ticket or GitHub issue only when you ask
From reading its instructions, not from running it.
Why it scores 68
Strongest on upkeep (100 of 100), weakest on adoption (41).
Is write-product-spec safe to install?
At least one scanner raised a medium warning. Read the results below. Scanners often miss what other scanners catch, and a skill can change after a scan. Read its source before you install it.
| Scanner | Result | Date |
|---|---|---|
| Gen Agent Trust Hub | Passed | Sep 15, 2026 |
| Socket | Passed | Sep 15, 2026 |
| Snyk | Medium risk | Sep 15, 2026 |
Details
- Installs
- 28,951
- Repository stars
- 695
- Last repository change
- Tokens always loaded
- about 97
- Tokens when used
- about 3,210
- License
- MIT
- Data confidence
- High
Did it do the job for you?
Alternatives to write-product-spec
All skills for this job- Get spec-driven-implementation
spec-driven-implementation
For teams building large features who want PRODUCT.md and TECH.md specs checked in before and during coding.
-
Get writing-planswriting-plans
For developers who give Claude a spec and want a test-first build plan before any code is written.
- Get brainstorming
brainstorming
For anyone who wants Claude to pin down what they really want before it builds.
-
Get Elephant Goldfish ModelElephant Goldfish Model
For engineers who write design docs before building and want fresh-eyed agent reviewers.
write-product-spec