generate-prd

Generate structured Product Requirements Documents with clarifying questions and standard sections.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/teaglebuilt/aiconfig --skill generate-prd-teaglebuilt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-prd
Source: https://github.com/teaglebuilt/aiconfig/tree/main/.claude/skills/generate-prd
Command: npx skills add https://github.com/teaglebuilt/aiconfig --skill generate-prd-teaglebuilt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs), ensuring clarity and alignment for new features and projects.

Core Features & Use Cases

  • Structured PRD Generation: Creates detailed PRDs with sections for Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and more.
  • Clarifying Questions: Asks targeted questions to gather necessary information before generating the PRD.
  • Use Case: When planning a new feature like a "user profile editing page," this Skill will guide you through defining its purpose, user interactions, and technical considerations, resulting in a ready-to-use PRD.

Quick Start

Use the generate prd skill to write a prd for a new feature that allows users to upload profile pictures.

Frequently Asked Questions about generate-prd

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

FAQPage Schema
How do I generate a product requirements document for a new feature?

To generate a product requirements document, provide your new feature details to the Skill. It asks clarifying questions to gather requirements and structures the output into sections like Goals, User Stories, and Functional Requirements for development teams.

What sections are included in a PRD created with this Skill?

A PRD created with this Skill includes sections for Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics. This structured documentation ensures clarity and alignment for new features.

How do I gather user stories and functional requirements for feature planning?

You gather user stories and functional requirements by answering targeted clarifying questions from the Skill. It prompts you for essential details about user interactions and technical considerations before structuring the feature planning documentation.

Does PRD generation work without providing all initial project specifications?

Yes, PRD generation works without initial project specifications because the Skill actively prompts you with clarifying questions. It gathers the necessary details about your feature's purpose and interactions before generating the final documentation.

Can I define non-goals and success metrics when writing product requirements?

Yes, you can define non-goals and success metrics when writing product requirements. The Skill structures your PRD to explicitly include these sections, ensuring clear project boundaries and measurable outcomes for your development teams.