# product-specs-writer

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 222 installs · ★ 54 repo stars
- Author: ncklrs
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ncklrs/startup-os-skills/tree/HEAD/skills/product-specs-writer/SKILL.md
- Updated: 2026-02-26
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/product-specs-writer

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/product-specs-writer/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/product-specs-writer/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/product-specs-writer/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/product-specs-writer/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install ncklrs/startup-os-skills skills/product-specs-writer
```

2. **Manually: put the files in place**
- File: `.github/skills/product-specs-writer/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/ncklrs/startup-os-skills --path skills/product-specs-writer
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/product-specs-writer/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add ncklrs/startup-os-skills --skill product-specs-writer -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ncklrs/startup-os-skills/tree/HEAD/skills/product-specs-writer/SKILL.md

## When to use it
- 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
- 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.

## Similar
- [prd-writer](https://affpapa.org/en/nevibecode/skills/prd-writer.md) — skill · 1300 installs
- [reverse-engineering-specs](https://affpapa.org/en/nevibecode/skills/reverse-engineering-specs.md) — skill · 116 installs
- [deanpeters-pm-skills](https://affpapa.org/en/nevibecode/skills/deanpeters-pm-skills.md) — skill · 270 installs
- [project-creator](https://affpapa.org/en/nevibecode/skills/project-creator.md) — skill · 113 installs
- [write-spec](https://affpapa.org/en/nevibecode/skills/write-spec.md) — skill · 3800 installs
- [deliver-user-stories](https://affpapa.org/en/nevibecode/skills/deliver-user-stories.md) — skill · 1000 installs

From the same set: [ncklrs/startup-os-skills](https://affpapa.org/en/nevibecode/by/ncklrs/startup-os-skills.md) — 51 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
