A product spec is a written plan that shows exactly how a new feature should work from the user's point of view. It makes the desired behavior clear and complete. This skill helps you create a PRODUCT.md file for any significant feature in Warp.
The spec focuses on what the user sees, does, and experiences. It does not include any internal implementation details. The term "user" depends on the feature type, such as a human using the app, a developer using a CLI, or another service calling an API. The goal is to describe the surface shape and invariants from that consumer's perspective.
Writing the product spec is usually the first step. After the spec is agreed upon, you can write a companion tech spec for implementation details. The spec is saved in a folder with the feature name or ticket number. You can also ask for a Figma link for UI features to capture visual states accurately.
Global
mkdir -p ~/.claude/skills/write-product-specProject
mkdir -p .claude/skills/write-product-specSource Repository
Grill With Docsmattpocock/skills
Stress-test your plan, refine your terms, and update docs instantly
To Prdmattpocock/skills
Generate a complete PRD from your conversation and codebase understanding
Lark Doclarksuite/cli
Create read summarize edit translate and manage Lark cloud documents
Github Actions Docsxixu-me/skills
Answers your GitHub Actions questions with exact official documentation links
Readme I18nxixu-me/skills
Localize your repo READMEs automatically with structure and selector intact
Ubiquitous Languagemattpocock/skills
Build a shared glossary of terms from your conversations with clear definitions
Doc Coauthoringanthropics/skills
Co author documents step by step with context refinement and reader testing
Edit Articlemattpocock/skills
Polish your article drafts by improving clarity structure and flow