prd-writer

Generate structured Product Requirements Documents from ambiguous product ideas.

Updated May 9, 2026
One-click install
npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill prd-writer-gustavogutierrez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-writer
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/prd-writer
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill prd-writer-gustavogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Producing clear, testable product requirements is hard, so this Skill helps teams transform vague feature ideas into a structured PRD that aligns stakeholders and guides engineering execution.

Core Features & Use Cases

  • Structured PRD generation: Creates an executive summary, user experience and functionality, technical specifications, and risks using a strict schema.
  • Discovery-first scoping: Forces clarifying questions to avoid missing constraints, success metrics, and non-goals.
  • AI-feature readiness: Includes AI system requirements and an evaluation strategy when applicable, so requirements can be validated.

Quick Start

Use prd-writer to generate a PRD for an AI-powered feature by providing the problem you want to solve, your target users, and any known constraints.

Frequently Asked Questions about prd-writer

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

FAQPage Schema
How do I write product requirements for AI-powered features?

Generating a PRD for AI features requires defining system capabilities and evaluation metrics. The Skill creates AI system requirements and an evaluation strategy alongside standard user stories and technical specifications to ensure validation.

How do I turn a vague product idea into a structured PRD?

Turning a vague idea into a PRD requires applying a strict schema to organize constraints. This Skill converts ambiguous product ideas into a stakeholder-ready structure by forcing discovery-first scoping and generating an executive summary, user stories, and technical specifications.

What is the best way to write user stories with acceptance criteria?

Writing user stories with acceptance criteria is best handled by enforcing a strict PRD schema. The Skill generates user stories paired with specific acceptance criteria, ensuring requirements remain testable and aligned with engineering execution.

Can I use this to document product discovery and identify missing constraints?

Documenting product discovery to identify missing constraints is a core capability. The Skill enforces a discovery-first scoping approach that actively surfaces clarifying questions and handles missing constraints by marking them as TBD.

Does PRD generation include risk analysis and technical specifications?

PRD generation includes comprehensive risk analysis and technical specifications. The Skill outputs a complete document containing technical specs, identified risks, user experience details, and functional requirements in a unified source of truth.