write-a-prd

Name: write-a-prd
Availability: InStock
Author: Lucas

Create Markdown product requirements documents from idea and interview inputs.

2|20|Updated Jan 20, 2026

Search Tags:#acceptance criteria #feature planning #prd #product requirements #user interviews #scope definition

Ready to run

npx skills add https://github.com/LucasMatuszewski/JSystems-SilkyCoders-1 --skill write-a-prd-lucasmatuszewski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/LucasMatuszewski/JSystems-SilkyCoders-1/tree/main/.agents/skills/write-a-prd
Command: npx skills add https://github.com/LucasMatuszewski/JSystems-SilkyCoders-1 --skill write-a-prd-lucasmatuszewski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn a rough product or feature idea into a clear Product Requirements Document by forcing the missing decisions out into the open before writing begins.

Core Features & Use Cases

Structured discovery: asks the right clarifying questions about users, flows, scope, constraints, and edge cases.
Requirements shaping: converts interview answers and repo context into a PRD with goals, user stories, acceptance criteria, and out-of-scope items.
Use case: a team wants to plan a new MVP feature and needs a document that developers can use to design and implement it without ambiguity.

Quick Start

Ask me to help write a PRD for your feature idea, and I will interview you, gather the needed details, and draft the document.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema

What should be included in a PRD for an MVP feature?▼

To write a product requirements document from a rough feature idea, you can use a structured discovery process that interviews you to clarify user personas, scope boundaries, and acceptance criteria before drafting the final PRD.

How do I define out-of-scope boundaries for product requirements?▼

Defining out-of-scope boundaries for product requirements involves explicitly listing features and flows that the current MVP or PoC will not address, preventing scope creep during implementation.

Can I generate acceptance criteria from user interview inputs?▼

Yes, you can generate acceptance criteria from user interview inputs by applying requirements shaping to convert your answers and repo context into a structured PRD with clear testable conditions.

What is the best way to plan scope definition for a new PoC?▼

The best way to plan scope definition for a new PoC is to conduct a structured discovery first, answering clarifying questions about constraints and edge cases to shape accurate requirements before development begins.

Why does my PRD lack clear user stories for developers?▼

Your PRD lacks clear user stories for developers because it was likely written without structured discovery, meaning missing decisions about user flows and edge cases were not forced out into the open before writing began.