Specification

When the user needs to write a PRD, feature spec, technical spec, or define requirements. Use when the user says 'write a spec,' 'PRD,' 'product requirements,' 'define the feature,' 'what should we build,' 'scope this,' 'requirements doc,' or is starting a new feature/project and needs structured planning.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add 0xranx/agentbrief --skill specification
Manual install
git clone --depth 1 https://github.com/0xranx/agentbrief.git /tmp/agentbrief
mkdir -p ~/.claude/skills
cp -r /tmp/agentbrief/briefs/product-manager/skills/specification ~/.claude/skills/specification

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Product Specification

You are a product manager writing specifications that engineering teams can build from. Your specs are precise enough to implement but flexible enough to allow good engineering judgment.

## Spec Structure

### 1. Problem Statement (1-3 sentences)
- What user problem are we solving?
- Why does it matter NOW?
- What's the cost of NOT solving it?

### 2. Success Metrics
- **Primary metric**: The one number that tells us if this worked
- **Secondary metrics**: Supporting signals (2-3 max)
- **Guardrail metrics**: Things that must NOT get worse

### 3. User Stories
Format: `As a [persona], I want to [action] so that [outcome]`

Prioritize using MoSCoW:
- **Must have** — Launch blocker
- **Should have** — Expected but not blocking
- **Could have** — Nice to have
- **Won't have** — Explicitly out of scope (this is important!)

### 4. Scope & Non-Scope
- **In scope**: Exactly what we're building
- **Out of scope**: What we're explicitly NOT building (and why)
- **Future considerations**: Things we're deferring but designing for

### 5. User Flow
Walk through the happy path step-by-step:
1. User does X
2. System responds with Y
3. User sees Z

Then list edge cases and error states.

### 6. Technical Constraints
- Platform/framework requirements
- Performance requirements (latency, throughput)
- Data requirements (storage, privacy, retention)
- Integration points with existing systems

### 7. Open Questions
Read the full skill on GitHub

Details

Skill name
specification
Path
briefs/product-manager/skills/specification/SKILL.md
License
MIT
Repo updated
28 March 2026

FAQ

What does the Specification skill do?

When the user needs to write a PRD, feature spec, technical spec, or define requirements. Use when the user says 'write a spec,' 'PRD,' 'product requirements,' 'define the feature,' 'what should we build,' 'scope this,' 'requirements doc,' or is starting a new feature/project and needs structured planning.

How do I install the Specification skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add 0xranx/agentbrief --skill specification. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Specification popular?

It lives in 0xranx/agentbrief, which has 43 GitHub stars and 0 forks.

Related skills

Typescript Advanced Types

43

0xranx/agentbrief

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.

Software Development

Analytics Setup

43

0xranx/agentbrief

When the user needs to set up product analytics, event tracking, or says 'set up analytics,' 'add tracking,' 'GA4,' 'Mixpanel,' 'PostHog,' 'Amplitude,' 'what events should we track,' 'conversion tracking,' 'funnel tracking,' or is launching a product and needs to instrument it for data collection.

Data & Analytics

API Documentation

43

0xranx/agentbrief

Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.

Software Development

Arbitration Tax Disputes

43

AlsKozlov/ru-legal

Налоговый спор в АС после исчерпания досудебной стадии. Срок иска — 3 мес с получения решения УФНС (ст.198 АПК). Госпошлина по ст.333.21 НК. РФ practice: cuда выигрывают налогоплательщики 30-40% дел (значительно ниже чем по другим категориям; за последние годы коэффициент ухудшается для бизнеса).

Finance & Crypto

Payment Provider Protocol

47

vtex/skills

Apply when implementing a VTEX Payment Provider Protocol (PPP) connector or working with payment/connector endpoint files. Covers all nine required endpoints: Manifest, Create Payment, Cancel, Capture/Settle, Refund, Inbound Request, Create Auth Token, Provider Auth Redirect, and Get Credentials. Use for building or debugging any payment connector that integrates with the VTEX Payment Gateway.

Finance & Crypto

Assess Ip Landscape

45

pjt222/agent-almanac

Map the intellectual property landscape for a technology domain or product area. Covers patent cluster analysis, white space identification, competitor IP portfolio assessment, freedom-to-operate preliminary screening, and strategic IP positioning recommendations. Use before starting R&D in a new technology area, when evaluating market entry against incumbents with strong patent portfolios, preparing for investment due diligence, informing a patent filing strategy, or assessing freedom-to-operate risk for a new product.

Finance & CryptoIn 1 list

Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.