prd

Generate structured product requirements documents with success metrics and acceptance criteria.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/y0ncha/aptitude-client --skill prd-y0ncha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/y0ncha/aptitude-client/tree/main/.agents/skills/prd
Command: npx skills add https://github.com/y0ncha/aptitude-client --skill prd-y0ncha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms vague product ideas and stakeholder requests into a clear, measurable, and development-ready Product Requirements Document that aligns business goals with technical execution.

Core Features & Use Cases

  • Structured PRD Output: Produces PRDs following a strict schema with Executive Summary, User Experience & Functionality, AI System Requirements (if applicable), Technical Specifications, Risks, and Roadmap.
  • Discovery-first Process: Enforces an interview phase that asks clarifying questions to avoid assumptions and hallucinated constraints.
  • Validation & Test Guidance: Includes acceptance criteria, measurable success metrics, and testing recommendations for AI components and integrations.
  • Use Case: Use when initiating a new feature or AI product, converting stakeholder notes into user stories, acceptance criteria, and an implementation plan.

Quick Start

Draft a PRD for a recommendation feature that personalizes article suggestions, including executive summary, user stories with acceptance criteria, technical architecture, success metrics, rollout plan, and testing strategy.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I generate a product requirements document from vague ideas?

To generate a product requirements document from vague ideas, use a discovery-first interview process that asks clarifying questions to scope technical specifications, user stories, and acceptance criteria without hallucinated constraints.

What is the best way to write user stories and acceptance criteria for a new feature?

The best way to write user stories and acceptance criteria is translating stakeholder notes into a structured PRD schema, ensuring functionality aligns with measurable success metrics and technical specifications.

How do I create technical specifications for AI-powered features?

Creating technical specifications for AI-powered features requires documenting AI system requirements, integration points, security considerations, and evaluation strategies within a structured product requirements document.

Does the PRD generation process include rollout phases and success metrics?

Yes, the PRD generation process includes rollout phases and success metrics by producing roadmap outputs that define measurable success criteria, testing recommendations, and implementation plans.

Can I use this approach to turn stakeholder notes into a development-ready technical spec?

Yes, you can turn stakeholder notes into a development-ready technical spec by applying a discovery-first process that enforces an interview phase to avoid assumptions and produces a strict PRD schema.