prd-local

Generate a structured Product Requirements Document from a feature prompt.

Updated Jan 19, 2026

Search Tags:#planning #documentation #feature #prd #product-requirements

Ready to run

npx skills add https://github.com/rhinkle/Mic-Feedback-Monitor --skill prd-local

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-local
Source: https://github.com/rhinkle/Mic-Feedback-Monitor/tree/main/.claude/skills/prd-local
Command: npx skills add https://github.com/rhinkle/Mic-Feedback-Monitor --skill prd-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate clear, actionable Product Requirements Documents from vague feature ideas to align teams and reduce scope creep.

Core Features & Use Cases

Generate a complete PRD from a user-provided feature prompt.
Ask 3-5 essential clarifying questions to resolve ambiguity.
Save the generated PRD to tasks/prd-[feature-name].md for traceability and handoff.

Quick Start

Provide a feature description and answer the clarifying questions to generate and save a PRD at tasks/prd-[feature-name].md.

Frequently Asked Questions about prd-local

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

FAQPage Schema

How do I generate a product requirements document from a feature idea?▼

To generate a product requirements document, provide a feature description and answer 3-5 clarifying questions to resolve ambiguity, producing a structured PRD with goals, user stories, and functional requirements.

What sections should a PRD include for new feature planning?▼

A PRD for new feature planning should include Introduction, Goals, User Stories, Functional Requirements, and Non-Goals sections to align teams and reduce scope creep.

Can I create a PRD automatically and save it for team handoff?▼

Yes, you can create a PRD automatically and save it for team handoff by generating the document from a feature prompt, which is saved at tasks/prd-[feature-name].md for traceability.

How do I turn vague feature ideas into actionable user stories?▼

To turn vague feature ideas into actionable user stories, input the feature prompt and answer clarifying questions, which validates the scope and outputs structured user stories within the PRD.

What is the best way to document non-goals and prevent scope creep?▼

The best way to document non-goals and prevent scope creep is defining them in a structured PRD, which explicitly lists Non-Goals alongside functional requirements to align team boundaries.

Do I need any specific tools or dependencies to write a PRD?▼

No dependencies are required to write a PRD; the workflow operates standalone, gathering input through clarifying questions and saving the validated document directly to a local markdown file.