prd

Generate a structured product requirements document in Markdown from a feature idea.

207|30|Updated May 16, 2026
One-click install
npx skills add https://github.com/smallnest/goal-workflow --skill prd-smallnest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/smallnest/goal-workflow/tree/main/skills/prd
Command: npx skills add https://github.com/smallnest/goal-workflow --skill prd-smallnest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a vague feature idea into a clear, reviewable Product Requirements Document and then helps prepare it for implementation by breaking the work into small, actionable issues.

Core Features & Use Cases

  • Clarifying questions: Asks a few targeted questions to remove ambiguity before drafting the PRD.
  • Structured PRD generation: Produces a complete PRD with goals, user stories, functional requirements, non-goals, success metrics, and open questions.
  • Issue-ready output: Supports the next step of decomposing an approved PRD into implementable issues for common workflows such as feature planning, bilingual requests, and backlog preparation.

Quick Start

Tell the prd skill to write a PRD for your feature idea, answer its clarifying questions, and confirm the draft before it saves the document.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I turn a vague feature idea into a structured product requirements document?

To turn a vague feature idea into a product requirements document, provide your initial concept to the skill. It asks clarifying questions to remove ambiguity, then generates a structured PRD with goals, user stories, and functional requirements saved as Markdown.

What is the best way to decompose a feature spec into actionable issues for backlog preparation?

Decomposing a feature spec into actionable issues starts with generating a structured PRD. Once the draft is reviewed and confirmed, the skill prepares the approved product requirements for issue decomposition to support backlog preparation and feature planning.

Can I capture bilingual requirements and output a bilingual product spec?

Bilingual requirements capture is supported by this skill. It handles ambiguous feature requests across languages, asks targeted clarifying questions, and generates a bilingual product spec saved under tasks/prd-[feature-name].md in Markdown format.

How does clarifying questions workflow help early product planning?

Clarifying questions help early product planning by resolving ambiguity before drafting the PRD. The skill asks targeted questions to ensure verifiable acceptance criteria and clear non-goals are established, resulting in a reviewable product specification.

What do I need to generate a PRD with verifiable acceptance criteria?

To generate a PRD with verifiable acceptance criteria, you only need an initial feature idea. The skill requires no dependencies and handles the specification workflow by producing numbered functional requirements and open questions in a Markdown file.