Write Product Spec
Write a PRODUCT.md spec from the consumer's perspective — behavior, invariants, no implementation details
- What
- Write a PRODUCT.md spec from the consumer's perspective — behavior, invariants, no implementation details
- Cost
- Free
- Needs
- an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse); optional Linear ticket or GitHub issue to anchor the spec
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the product half that lot 32's write-tech-spec was missing. Lot 32 published the driver (spec-driven-implementation) and the tech side (write-tech-spec = TECH.md, the implementation plan anchored in the codebase); this one writes PRODUCT.md: desired behavior from the consumer's perspective — what the user sees, does, and experiences, the invariants that must hold — with zero implementation details (no internal types, state layout, algorithms). The method is generic even though the examples cite Warp: specs go to specs/<id>/PRODUCT.md (Linear ticket, GitHub issue, or kebab-case name), gather behavior via ask_user_question rather than guessing, ask about Figma mocks for UI features (recording "Figma: none provided" explicitly). Usually step one of a two-step process: PRODUCT.md agreed, then write-tech-spec produces TECH.md from it. Distinct from to-spec (lot 33, interview synthesis): this is a behavioral PRD template. By @warpdotdev, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse); optional Linear ticket or GitHub issue to anchor the spec Install "Write Product Spec" for me. Write a PRODUCT.md spec from the consumer's perspective — behavior, invariants, no implementation details Repository: https://github.com/warpdotdev/common-skills/blob/main/.agents/skills/write-product-spec/SKILL.md 1. Fetch the SKILL.md file for the warpdotdev-write-product-spec skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "warpdotdev-write-product-spec". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.