write-spec

Convert feature ideas into structured PRDs with goals and acceptance criteria.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/sun2443/designer-skills --skill write-spec-sun2443
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-spec
Source: https://github.com/sun2443/designer-skills/tree/main/product-management/skills/write-spec
Command: npx skills add https://github.com/sun2443/designer-skills --skill write-spec-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You have a vague feature idea or user request, but you need a structured, stakeholder-ready PRD that clarifies goals, scope, requirements, and success metrics.

Core Features & Use Cases

  • Problem-to-PRD conversion: Translates a feature name, problem statement, or user request into a complete PRD with clear structure.
  • Context gathering for better alignment: Guides the user through key questions (users, success metrics, constraints, prior art) conversationally while filling gaps.
  • Connected-tool driven enrichment: Optionally pulls relevant information from connected tools like project trackers, knowledge bases, and design resources when available.
  • Outcome-ready deliverable: Produces sections including problem statement, goals, non-goals, user stories, requirements with acceptance criteria, success metrics, open questions, and timeline considerations.

Quick Start

Use this skill by prompting it with the feature or problem statement you want to spec, and it will generate a structured PRD for you.

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?

Generating a feature specification from a problem statement produces a structured PRD with goals, non-goals, user stories, and measurable success metrics. This process scopes your ideas into defined requirements categorized as Must-Have, Nice-to-Have, or Future Considerations.

What is the best way to define acceptance criteria for user stories?

Defining acceptance criteria for user stories involves translating feature requests into scoped requirements. The generated specification document pairs each user story with clear acceptance criteria to ensure development teams understand the exact conditions for feature completion.

How do I scope product requirements and separate goals from non-goals?

Scoping product requirements requires clarifying exactly what a feature will and will not deliver. The specification process structures your PRD by explicitly defining goals, setting non-goals to prevent scope creep, and categorizing requirements into Must-Have and Nice-to-Have buckets.

Can I create a feature spec from just a problem statement?

Yes, you can create a feature spec from just a problem statement. The conversion process guides you conversationally through key questions about users, constraints, and prior art to fill gaps, ultimately producing a complete, stakeholder-ready PRD.

What should be included in a PRD for new product features?

A PRD for new product features should include the problem statement, goals, non-goals, user stories, requirements with acceptance criteria, and measurable success metrics. It also needs to outline open questions and timeline considerations for stakeholder alignment.