One-click install
npx skills add https://github.com/richardwu/agent-skills --skill prd-richardwu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/richardwu/agent-skills/tree/main/skills/prd
Command: npx skills add https://github.com/richardwu/agent-skills --skill prd-richardwu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams and engineers often lack a concise, actionable specification when starting a feature, which causes misaligned expectations, rework, and slow implementation. This Skill formalizes feature intent into a single, structured document that developers and stakeholders can act on.

Core Features & Use Cases

  • Guided Clarification: Prompts 3-5 essential, lettered clarifying questions to resolve ambiguous requirements before drafting.
  • Structured PRD Output: Produces a markdown PRD with Introduction, Goals, Prioritized User Stories with verifiable acceptance criteria, Functional Requirements, Non-Goals, Technical considerations, Success Metrics, and Open Questions.
  • Developer-Friendly Artifacts: Formats user stories and requirements explicitly for junior developers or AI agents and saves the result to a tasks folder for integration into workflows.
  • Use Case: Product manager needs a scoped PRD and user stories for a new onboarding flow; the Skill asks clarifying questions, accepts answers like "1A,2C", and outputs tasks/prd-onboarding-flow.md.

Quick Start

Ask the skill to create a PRD by saying: Create a PRD for a passwordless login feature and answer the clarifying questions when prompted.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I write a product requirements document with user stories and acceptance criteria?

A PRD should include goals, prioritized user stories with verifiable acceptance criteria, functional requirements, non-goals, technical considerations, success metrics, and open questions to ensure actionable feature implementation.

What's the best way to structure user stories for a new feature specification?

The best way to structure user stories in a feature specification is to prioritize them alongside verifiable acceptance criteria and functional requirements, ensuring developers understand exactly what to build and how success is measured.

Can I use this PRD generation process for an onboarding flow feature?

Yes, you can use this PRD generation process for an onboarding flow feature by answering guided clarifying questions about the requirements, which then outputs a structured markdown file to your tasks folder.

Do I need prior technical knowledge to create implementable product requirements?

You do not need deep technical knowledge to create implementable product requirements, as the guided clarification process resolves ambiguous inputs and formats user stories explicitly for junior developers or AI agents.

Why should I include open questions in a product requirements document?

You should include open questions in a product requirements document to track unresolved technical considerations and feature planning ambiguities, preventing implementation delays and misaligned stakeholder expectations.