product-specs-writer — Claude Code skill: what it does, how to install
product-specs-writer turns a rough feature idea into a PRD, user stories or a technical spec with acceptance criteria a tester can run against.
no license 222 installs ★ 54 updated 2026-02-26
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a claude-codeWhat product-specs-writer does
The skill kicks in when you ask for a requirements doc, a user story, acceptance criteria, an API contract, a rollout plan behind feature flags or a set of success metrics. Its rules sit in rules/, split by prefix: prd-*, stories-*, criteria-*, technical-*, api-*, edge-*, design-*, rollout-*, metrics-*, maintenance-*.
What you get is a working frame, not prose: a hierarchy running from the problem statement down to implementation, INVEST checks for stories, completeness checklists for both the PRD and the technical spec, and a taxonomy that sorts failures into validation, authorization, resource, system, business-logic and third-party errors.
Anti-patterns get a section of their own — specs written by committee, implementation detail settled too early, a release that tries to cover everything, docs nobody updates. Templates ship as markdown blocks, so porting them into Jira or Notion takes manual work.
What it helps with
- draft a PRD with problem, metrics and scope boundaries
- split a feature into INVEST-shaped user stories
- write acceptance criteria a QA engineer can test
- document API contracts and versioning rules
- map edge cases and failure behaviour before coding
Example prompts for the agent
- Write a PRD for report export: the problem, success metrics, and what falls outside scope.
- Break this feature into user stories that pass INVEST, with acceptance criteria for each.
- Draft a technical spec with edge cases and a feature-flag rollout plan.
How to install product-specs-writer
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a claude-code2Manually: put the files in place
~/.claude/skills/product-specs-writer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-specs-writer/
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a codex2Manually: put the files in place
.agents/skills/product-specs-writer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a cursor2Manually: put the files in place
.cursor/skills/product-specs-writer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ncklrs/startup-os-skills skills/product-specs-writer2Manually: put the files in place
.github/skills/product-specs-writer/SKILL.md1Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a gemini-cli2Platform CLI
gemini skills install https://github.com/ncklrs/startup-os-skills --path skills/product-specs-writerManually: put the files in place
.devin/skills/product-specs-writer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about product-specs-writer
How do I install product-specs-writer in Claude Code?
Run npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a claude-code. The skill lands in ~/.claude/skills/product-specs-writer/SKILL.md.
What does product-specs-writer do?
It helps you write product documentation: PRDs, user stories, acceptance criteria, technical specs, API contracts, rollout plans and success metrics. The guidance lives in rules/, alongside templates and completeness checklists.
Does it work outside Claude?
Yes, it also runs in Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode. On GitHub Copilot install it with gh skill install ncklrs/startup-os-skills product-specs-writer.