write-prd

Guide users through eight PRD creation phases with templates and validation.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ischung/go-sdlc-gan --skill write-prd-ischung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-prd
Source: https://github.com/ischung/go-sdlc-gan/tree/main/write-prd-skill
Command: npx skills add https://github.com/ischung/go-sdlc-gan --skill write-prd-ischung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users through a structured, phase-based PRD creation process, turning raw ideas into a complete product requirements document with disciplined coaching and traceable decisions.

Core Features & Use Cases

  • Phase-driven coaching: eight sequential phases (Discovery to Final PRD) with guided prompts, templates, and explicit rework loops.
  • Incremental validation & approvals: after each phase, user confirms before advancing to ensure alignment and documentation traceability.
  • PRD vs TechSpec guidance: keeps What/Why in PRD and reserves How for TechSpec, enabling smooth handoff when ready.
  • Save, share, and iterate: final PRD can be saved as a Markdown file in the current workspace and revisited for future revisions.

Quick Start

Describe your product idea to start Phase 0, and I will guide you through discovery and initial goals.

Frequently Asked Questions about write-prd

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

FAQPage Schema
How do I write a product requirements document step by step?

To write a product requirements document, you progress through eight sequential phases, from initial brainstorming and goal definition to detailed requirements and final documentation. Each phase uses guided prompts and templates to ensure structured, traceable decisions.

What is the difference between a PRD and a TechSpec?

A PRD focuses on the What and Why of a product feature, while a TechSpec reserves the How for technical implementation. This separation ensures clear product definition and enables smooth technical handoff to engineering teams.

How do I define product scope and personas during PRD creation?

Defining product scope and personas is handled in specific coaching phases that prompt you with targeted questions and templates. This structured approach ensures your user archetypes and feature boundaries align directly with your product goals before advancing.

Can I save my PRD as a Markdown file in my workspace?

Yes, you can save your final PRD as a Markdown file directly in your current workspace on command. The process enforces a frontmatter-driven structure and allows you to revisit the file for future revisions.

What is the best way to validate requirements before finalizing a PRD?

The best way to validate requirements before finalizing a PRD is through incremental validation and approvals. After each of the eight phases, you must explicitly confirm alignment before advancing, creating explicit rework loops if needed.