Agent skill · product strategy · anthropics
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
Why this skill is useful
Provides a structured template for creating PRDs that includes specific metrics and user stories, which the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.
What this skill does
Write Spec If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Write a feature specification or product requirements document (PRD). Usage Workflow 1. Understand the Feature Ask the user what they want to spec. Accept any of: A feature name ("SSO support") A problem statement ("Enterprise customers keep asking for centralized auth") A user request ("Users want to export their data as CSV") A vague idea ("We should do something about onboarding drop-off") 2. Gather Context Ask the user for the following. Be conversational — do not dump all questions at once. Ask the most important ones first and fill in gaps as you go: User problem: What problem does this solve? Who experiences it? Target users: Which user segment(s) does this serve? Success metrics: How will we know this worked? Constraints: Technical constraints, timeline, regulatory requirements, dependencies Prior art: Has this been attempted before? Are there existing solutions? 3. Pull Context from Connected Tools If ~~project tracker is connected: Search for related tickets, epics, or features Pull in any existing requirements or acceptance criteria Identify dependencies on other work items If ~~knowledge base is connected: Search for related research documents, prior specs, or design docs Pull in relevant user research findings Find related meeting notes or decision records If ~~design is connected: Pull related mockups, wireframes, or design explorations Search for design system components relevant to the feature If these tools are not connected, work entirely from what the user provides. Do not ask the user to connect tools — just proceed with available information. 4. Generate the PRD Produce a structured PRD with these sections. See PRD Structure below for detailed guidance on what each section should contain. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills anthropics/write-spec