prd

Generate a structured PRD from a feature description and clarifying questions.

2|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/lhaig/loop --skill prd-lhaig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/lhaig/loop/tree/main/prd
Command: npx skills add https://github.com/lhaig/loop --skill prd-lhaig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate vague feature ideas into a clear, actionable Product Requirements Document (PRD). It reduces miscommunication and provides a single source of truth for scope, goals, and success criteria.

Core Features & Use Cases

  • Clarifying Question Workflow: prompts 3-5 essential questions to resolve ambiguity and surface critical requirements.
  • Structured PRD Generation: outputs a complete PRD with Introduction, Goals, User Stories (with Acceptance Criteria), Functional Requirements, and Non-Goals.
  • Save & Reuse: saves the generated PRD to /tasks/prd-[feature-name].md for archival and collaboration.

Quick Start

Use the PRD skill by providing a feature description. The tool will ask 3-5 clarifying questions and then generate a PRD saved to /tasks/prd-[feature-name].md.

Frequently Asked Questions about prd

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. The tool then outputs a structured PRD with goals, user stories, and functional requirements.

What is the best way to write user stories with acceptance criteria for feature planning?

Writing user stories with acceptance criteria is handled by the structured PRD generation process, which automatically formats your clarified feature requirements into actionable user stories with specific acceptance criteria.

How do you define functional requirements and non-goals when documenting feature specifications?

Defining functional requirements and non-goals requires clarifying feature scope through targeted questions. The generated PRD explicitly separates what needs to be built from out-of-scope non-goals to prevent miscommunication.

Can I save a generated PRD to a markdown file for team collaboration?

Yes, you can save a generated PRD to a markdown file. The tool automatically archives the completed product requirements document to /tasks/prd-[feature-name].md for ongoing team collaboration and reuse.

Does this PRD tool ask clarifying questions before creating the feature specification?

Yes, the PRD tool prompts 3-5 essential clarifying questions before creating the feature specification. This workflow surfaces critical requirements and resolves ambiguity in your initial feature description.