prd

Generate structured PRDs with goals, user stories, and acceptance criteria.

17|1|Updated Nov 17, 2024
One-click install
npx skills add https://github.com/mifunedev/orchestra --skill prd-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/mifunedev/orchestra/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/mifunedev/orchestra --skill prd-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PRD Generator helps product teams transform vague feature ideas into structured, implementation-ready PRDs, reducing back-and-forth and ensuring alignment before development.

Core Features & Use Cases

  • Clarifying-question-driven PRD creation to resolve ambiguities.
  • Structured PRD output with goals, user stories, acceptance criteria, functional and non-goals sections.
  • Automatic saving to tasks/prd-[feature-name].md for traceability and handoff.
  • Supports multi-phase pipelines when specs are provided.

Quick Start

Use the PRD generator to turn a feature idea into a detailed PRD by answering a set of clarifying questions, then save the result 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 PRD from a loosely defined feature idea?

To generate a PRD from a feature idea, the skill asks clarifying questions to resolve ambiguities and outputs a structured document with goals, user stories, scope, and acceptance criteria.

What is the best way to structure product requirements to reduce development rework?

Structuring requirements with explicit goals, user stories, non-goals, and acceptance criteria for verification reduces ambiguity and ensures development alignment before coding begins.

How does a clarifying-question-driven approach work for product specification creation?

This approach works by asking targeted questions about your vague feature prompt, consolidating your answers into structured product specifications, and automatically saving the output to a traceable file.

Can I use this for product planning across ideation and discovery phases?

Yes, you can use this for product planning across ideation, discovery, and planning phases, especially when consolidating project goals, scope, and acceptance criteria into a unified document.

Does the generated PRD save automatically to a specific file format?

Yes, the generated PRD saves automatically to a markdown file named tasks/prd-[feature-name].md for traceability and seamless handoff to development teams.

Do I need to provide technical specifications for multi-phase PRD pipelines?

You need to provide specifications to support multi-phase pipelines, allowing the tool to generate production-ready PRDs that satisfy structured sections and acceptance criteria verification.