write-a-prd

Interview users and analyze codebases to draft structured PRDs for GitHub issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft a complete PRD by interviewing users, analyzing the codebase, and outlining modular requirements to guide product development.

Core Features & Use Cases

  • Guided PRD creation through structured user interviews and stakeholder alignment.
  • Module design and scoping, with traceable decisions and acceptance criteria.
  • GitHub issue generation and documentation ready for review and rollout.

Quick Start

Describe the user's problem to me succinctly, and I will generate a full PRD draft ready to post as a GitHub issue.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I draft a PRD through user interviews?

Draft a PRD through user interviews by describing your problem succinctly, participating in a structured interview process, and outlining modular solutions to produce a comprehensive requirements document.

What is the best way to generate product requirements ready for GitHub issues?

The best way to generate product requirements for GitHub issues is using an interview-driven workflow that gathers requirements, logs decisions, scopes modules, and outputs structured acceptance criteria for direct posting.

Can I scope modules and align stakeholders when planning new features?

Yes, you can scope modules and align stakeholders by applying a guided product design workflow that explores the codebase, traces design decisions, and produces a structured requirements document for review and rollout.

How does interview-driven product design help create a PRD?

Interview-driven product design helps create a PRD by guiding you through structured stakeholder interviews, exploring the codebase, and outlining modular requirements to satisfy traceable decisions and acceptance criteria.

What should I prepare before starting the PRD generation process?

Before starting the PRD generation process, you should prepare a succinct description of the user's problem to initiate the structured interview and codebase analysis for modular requirements gathering.

Does this PRD workflow support logging decisions and acceptance criteria?

Yes, this PRD workflow supports logging decisions and acceptance criteria by satisfying requirements gathering, decision logging, module scoping, and producing traceable design decisions within the generated document.