skills.rest
Nadav011
Nadav011COMMUNITY
Explore all skills by this author →
GitHub

write-spec

Generates structured PRDs with goals, user stories, requirements, and success metrics from feature ideas.

Updated Sep 15, 2026
Search Tags:#acceptance criteria#user stories#prd#product requirements#scope management#success metrics#feature spec
One-click install
npx skills add https://github.com/Nadav011/nadavai-claude --skill write-spec-nadav011
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/Nadav011/nadavai-claude/tree/main/plugins/nadavai/skills/write-spec
Command: npx skills add https://github.com/Nadav011/nadavai-claude --skill write-spec-nadav011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a vague feature idea or user request into a clear, scoped specification is time-consuming and often results in scope creep, missing acceptance criteria, or undefined success metrics. This Skill guides you through a structured workflow to produce a complete PRD. ## Core Features & Use Cases - Structured PRD Generation: Produces a full document with problem statement, goals, non-goals, user stories, prioritized requirements (P0/P1/P2), success metrics, open questions, and timeline considerations. - Context Gathering: Conversationally collects user problems, target segments, constraints, and prior art, and can pull related tickets, research, or designs from connected tools. - Scope Discipline: Enforces explicit non-goals, MoSCoW prioritization, and scope-creep prevention guidance so specs stay tight and shippable. - Use Case: A product manager hears "enterprise customers keep asking for centralized auth" and uses this Skill to produce a phased SSO spec with acceptance criteria and measurable adoption targets. ## Quick Start Ask the assistant to write a spec for your feature idea, for example: write a spec for adding SSO support for enterprise customers.

Frequently Asked Questions about write-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a PRD from a vague feature idea?▼

Provide the feature name, problem statement, or user request, and the Skill asks conversational follow-up questions about the user problem, target users, success metrics, and constraints. It then generates a structured PRD with goals, non-goals, user stories, and prioritized requirements.

What sections should a product requirements document include?▼

This Skill produces a PRD with a problem statement, 3-5 measurable goals, explicit non-goals, user stories grouped by persona, P0/P1/P2 requirements with acceptance criteria, leading and lagging success metrics, open questions, and timeline considerations.

How do I write good acceptance criteria for a feature?▼

Write acceptance criteria in Given/When/Then format or as a checklist covering happy paths, error cases, and edge cases. Each criterion should be independently testable and avoid ambiguous words like fast or intuitive.

How do I prevent scope creep in a feature spec?▼

Write explicit non-goals with rationale, require that any scope addition comes with a removal or timeline extension, separate v1 from v2 clearly, and keep a parking lot for out-of-scope ideas. The Skill builds these practices into every generated spec.

Can the spec pull context from project trackers or knowledge bases?▼

Yes, if connected tools like a project tracker, knowledge base, or design tool are available, the Skill searches for related tickets, research, and mockups. If they are not connected, it works entirely from the information you provide.

Related Skills

Explore More Product & Management Skills→
sparkline-venturessparkline-ventures
14

synthesize

Cluster collected evidence into problem-framed themes with confidence analysis.

Official
Advanced
kiurakkukiurakku
15

to-tickets

Decompose an approved spec into ordered, sized tickets with dependencies and agent-ready briefs.

Community
Intermediate
alo-expalo-exp
6

write-spec

Generate a structured PRD from a vague problem statement.

Official
Advanced
pproencapproenca
193

dev-rfc

Create RFCs and technical design documents with structured templates.

Community
Advanced