write-prd

Draft structured PRDs from product ideas with goals, users, and metrics.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/radenadri/skills-alena --skill write-prd-radenadri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-prd
Source: https://github.com/radenadri/skills-alena/tree/main/skills/write-prd
Command: npx skills add https://github.com/radenadri/skills-alena --skill write-prd-radenadri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn a vague product idea into a structured PRD by guiding discovery, clarifying goals and boundaries, and separating product outcomes from engineering tasks.

Core Features & Use Cases

  • Interview-led discovery phases to identify user needs, goals, and constraints.
  • Narrative shaping to produce a concise PRD covering problem, users, scope, requirements, risks, and success criteria.
  • Phase-based drafting workflow with review and verification to ensure handoff readiness.

Quick Start

Provide a product idea and target users, and I will draft a complete PRD.

Frequently Asked Questions about write-prd

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

FAQPage Schema
How do I draft a product requirements document from a vague idea?

To draft a product requirements document from a vague idea, provide your product concept and target users. The system guides an interview-led discovery phase to clarify goals, scope, and constraints, resulting in a structured PRD.

What should be included in a product requirements document for engineering handoff?

A product requirements document for engineering handoff must capture goals, users, non-goals, success metrics, assumptions, risks, and handoff steps. This structured narrative separates product outcomes from engineering tasks to ensure alignment.

How does interview-led discovery improve product planning?

Interview-led discovery improves product planning by identifying user needs, goals, and constraints early. This process shapes a concise narrative covering problem definition, scope, requirements, and success criteria for team alignment.

What is the best way to define product scope and separate it from engineering tasks?

The best way to define product scope and separate it from engineering tasks is using a phase-based drafting workflow. This process clarifies boundaries and produces a structured document distinguishing product outcomes from technical implementation.

Can I use a PRD to align teams on success criteria and risks?

Yes, you can use a PRD to align teams on success criteria and risks. The drafting workflow explicitly captures assumptions, risks, success metrics, and non-goals to verify handoff readiness and ensure cross-functional alignment.