prd

Name: prd
Availability: InStock
Author: jaimedhenriques

Generate product requirements documents with user stories and acceptance criteria.

Updated Apr 1, 2026

Search Tags:#acceptance criteria #feature planning #user stories #prd #product requirements #risk analysis

Ready to run

npx skills add https://github.com/jaimedhenriques/finsyt --skill prd-jaimedhenriques

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/jaimedhenriques/finsyt/tree/main/artifacts/platform/.agents/skills/prd
Command: npx skills add https://github.com/jaimedhenriques/finsyt --skill prd-jaimedhenriques

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague product ideas into clear, actionable Product Requirements Documents that align stakeholders, reduce scope confusion, and guide implementation.

Core Features & Use Cases

Structured PRD Creation: Produces executive summaries, user stories, acceptance criteria, technical specifications, risks, and rollout plans in a consistent format.
Discovery First: Prompts for critical missing context before drafting, helping teams avoid assumptions about goals, constraints, and success metrics.
AI and Software Planning: Supports both traditional software features and AI-powered systems by including evaluation strategy, tool needs, and validation requirements.

Quick Start

Ask the assistant to draft a PRD for your feature, and first have it ask at least two clarifying questions about the problem, success metrics, and constraints.

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 from a vague feature idea?▼

To write a product requirements document from a vague idea, the Skill first asks clarifying questions about goals and constraints, then generates a structured PRD with user stories, acceptance criteria, and rollout plans.

What should be included in a PRD for AI-powered features?▼

A PRD for AI-powered features should include an AI evaluation strategy, tool needs, validation requirements, technical architecture, security considerations, and standard software specifications like acceptance criteria.

How do you define acceptance criteria and user stories for feature planning?▼

Defining acceptance criteria and user stories for feature planning involves translating stakeholder goals into technical specifications, which this Skill structures automatically after prompting for missing context.

Can I generate technical specifications and risk analysis directly from product requirements?▼

Yes, you can generate technical specifications and risk analysis directly from product requirements, as the Skill produces comprehensive documents that align stakeholders and guide implementation.

What is the best way to align stakeholders before drafting a PRD?▼

The best way to align stakeholders before drafting a PRD is to use a discovery-first approach that prompts for critical missing context regarding success metrics, problem definitions, and project constraints.

Does this PRD generation approach support phased rollout planning?▼

Yes, this PRD generation approach supports phased rollout planning by explicitly including rollout phases, technical architecture, and executive summaries within the generated product requirements document.