skills.rest
GustavoGutierrez
GustavoGutierrezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

prp-writer

Generate build-ready 12-section Product Requirements Prompts from ambiguous product ideas.

Updated May 9, 2026
Search Tags:#prp#requirements engineering#product specification#scope definition#success metrics#jobs-to-be-done#ai-assisted development
One-click install
npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill prp-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prp-writer
Source: https://github.com/GustavoGutierrez/engineering-skills/tree/main/skills/prp-writer
Command: npx skills add https://github.com/GustavoGutierrez/engineering-skills --skill prp-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of turning vague product ideas and scattered inputs into a complete, unambiguous Product Requirements Prompt (PRP) that can be used directly for AI-assisted development.

Core Features & Use Cases

  • 12-Section PRP Output: Produces a standardized PRP document covering overview, problem, success criteria, user stories, functional/non-functional requirements, constraints, data/UI needs, risks/assumptions, out-of-scope, and open questions.
  • Complexity Pattern Classification: Helps classify the work into A/B/C complexity patterns to guide the level of rigor and solution framing.
  • Jobs-to-be-Done User Stories: Extracts user stories in a Jobs-to-be-Done format to clarify intent, not just features.

Use case example: When you have a new feature request with unclear requirements and stakeholder misalignment, use this Skill to generate a PRP that developers and AI can execute from with clear scope boundaries, measurable success criteria, and explicit risks.

Quick Start

Ask an AI to generate a complete Product Requirements Prompt for your feature, following the 12-section structure and including success metrics, functional and non-functional requirements, constraints, risks, out-of-scope items, and open questions.

Frequently Asked Questions about prp-writer

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

FAQPage Schema
How do I turn vague product ideas into build-ready product specifications for AI-assisted development?▼

To turn vague ideas into build-ready product specifications, you structure ambiguous inputs into a standardized 12-section Product Requirements Prompt covering scope, metrics, and decision-ready details for AI handoffs.

What is the best way to define scope and success metrics for a new feature request?▼

The best way to define scope and success metrics is by generating a standardized product specification that includes measurable success criteria, explicit out-of-scope boundaries, and Jobs-to-be-Done user stories.

How do I write Jobs-to-be-Done user stories for product requirements engineering?▼

Writing Jobs-to-be-Done user stories involves extracting user narratives from your product idea to clarify user intent and desired outcomes rather than just listing features in the requirements document.

Can I use a PRP to align stakeholders and clarify ambiguous feature requirements?▼

Yes, you can use a Product Requirements Prompt to align stakeholders by classifying complexity patterns and explicitly documenting risks, assumptions, and open questions for decision-ready alignment.

What sections are needed for a complete product specification document?▼

A complete product specification document requires 12 sections including overview, problem, success criteria, user stories, functional and non-functional requirements, constraints, data and UI needs, risks, and open questions.

When should I classify complexity patterns in requirement engineering?▼

You should classify complexity patterns during requirement engineering to guide the appropriate level of rigor and solution framing before generating the final build-ready product specification.

Related Skills

Explore More Product & Management Skills→
whawkinsivwhawkinsiv
232

plan

Turn vague product ideas into buildable specifications with user outcomes, screens, and edge cases.

Community
Intermediate
daffy0208daffy0208
34

PRP Generator

Generate structured product requirement prompts with 12 standardized sections.

Community
Basic
phuakyphuaky
2

SpecDriven

Extract user intent into structured specs with measurable success criteria.

Community
Advanced
Andy-HNUAndy-HNU

writing-prds

Capture and organize product requirements into actionable PRDs.

Community
Intermediate