Does this skill write the actual code for the feature?

No, this skill is specifically designed to create documentation only. It ensures requirements are fully defined and understood before any implementation begins.

How does the skill handle ambiguous requests?

It initiates a clarifying workflow, asking 3-5 targeted multiple-choice questions about the problem, core functionality, scope, and success criteria to eliminate guesswork.

Who is the intended audience for the generated PRDs?

The PRDs are written to be explicit and unambiguous, making them ideal for junior developers to understand and implement without needing heavy jargon.

Can I skip the clarifying questions?

The skill is designed to skip questions where the answers are already reasonably inferable from your initial prompt, focusing only on critical missing information.

Where are the generated PRDs saved?

The documents are saved as Markdown files in the /tasks/ directory of your project using a kebab-case naming convention, such as prd-feature-name.md.

Product Requirement Document Generator

Name: Product Requirement Document Generator
Author: adawalli

byadawalli

•

Productivity & Workflow

Generates structured, actionable Product Requirements Documents by clarifying feature goals and scope through interactive questioning.

The PRD Generator skill streamlines the software planning phase by transforming vague feature ideas into detailed, developer-ready documentation. It uses a structured interactive workflow that asks 3-5 critical clarifying questions with multiple-choice options to define project goals, target users, and success criteria. Once the scope is defined, it generates a standardized Markdown PRD written specifically for clarity and ease of implementation by junior developers, automatically saving the result to a dedicated tasks directory in your project.