z-write-prd

Generates decision-ready MVP PRDs from ideas, research notes, and interview materials.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/zh30/zstack --skill z-write-prd-zh30
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: z-write-prd
Source: https://github.com/zh30/zstack/tree/main/evals/runs/2026-08-01-grok-output-contracts-before-label-fix/raw/skill-snapshots/z-write-prd
Command: npx skills add https://github.com/zh30/zstack --skill z-write-prd-zh30

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Independent developers often jump from a rough idea straight into code without a clear product definition, causing scope creep and wasted effort. This Skill turns ideas, research notes, interviews, or rough specs into a structured, decision-ready MVP PRD that a solo founder or coding agent can build from directly. ## Core Features & Use Cases - Structured PRD generation: Produces a full PRD covering problem, persona, goals, non-goals, P0/P1/P2 requirements with acceptance criteria, user journeys, metrics, risks, and indie-sized milestones. - Evidence handoff contract: Ends every PRD with a fixed seven-row evidence table classifying claims as primary behavior, observed experiment, secondary public, search signal, or assumption, so downstream skills never over-trust unvalidated inputs. - Quality enforcement: Ships with a PRD template and a quality-bar checklist that blocks fake research quotes, untestable requirements, missing non-goals, and bloated word counts. - Use Case: After running customer interviews for a SaaS idea, paste your notes and ask for a PRD; the Skill drafts a 3,000-5,000 word document with labeled assumptions, P0 acceptance criteria, and a milestone plan sized for one person. ## Quick Start Turn my interview notes and feature list into a decision-ready MVP PRD with P0 requirements and acceptance criteria.

Frequently Asked Questions about z-write-prd

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

FAQPage Schema
How do I write a PRD for an MVP as a solo founder?▼

Provide your idea, notes, or interview material and the Skill drafts a PRD with problem statement, one primary persona, P0/P1/P2 requirements with acceptance criteria, non-goals, metrics, and indie-sized milestones. It keeps the core around 3,000-5,000 words and labels every assumption.

What should a product requirements document include?▼

This PRD structure covers overview, users, solution, P0 user journeys, functional and non-functional requirements with acceptance criteria, UX notes, data and integrations, risks, milestones, and an evidence handoff table. Non-goals and open questions are mandatory sections.

Can I generate a PRD from customer interview notes?▼

Yes, paste interview notes or a market validation report and the Skill maps supported pains into requirements and rejected ideas into non-goals. It never invents quotes or upgrades interview enthusiasm into validated payment or retention claims.

When should I not use a PRD writing skill?▼

Skip it when you have no product intent yet and only need market validation, when you need architecture or system design documents, or when you only want landing page copy. Those cases belong to validation, engineering design, or marketing workflows.

What is an evidence handoff table in a PRD?▼

It is a fixed seven-row table ending the PRD that records the current decision, evidence classes, supported claims, unproven items, contradictions, source anchors, and next validation step. Evidence classes are limited to primary behavior, observed experiment, secondary public, search signal, and assumption.