prd

Interview users and explore the repository to define a PRD solution plan.

Updated Nov 14, 2019
One-click install
npx skills add https://github.com/scott-rc/dotfiles --skill prd-scott-rc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/scott-rc/dotfiles/tree/main/configs/claude/skills/prd
Command: npx skills add https://github.com/scott-rc/dotfiles --skill prd-scott-rc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides you to create a complete PRD by interviewing users, inspecting the codebase, and outlining module design, then saving the output in a standardized plan file.

Core Features & Use Cases

  • Structured PRD creation for new features.
  • User interview-driven problem definition and validation.
  • Codebase exploration to validate assumptions and scope.
  • Plan file generation at the project path ./tmp/<name>/plan.md for easy handoff.

Quick Start

Describe the problem, then start the PRD workflow to generate the Brief section at ./tmp/<name>/plan.md.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I create a PRD from user interviews and codebase exploration?

You create a PRD by conducting user interviews, exploring the repository, and defining module goals with acceptance criteria. The structured output is saved to a plan file at ./tmp/<name>/plan.md for straightforward project handoff.

What is the best way to document a planned solution for a new feature?

Documenting a planned solution involves interviewing users, inspecting the codebase, and outlining module design. This generates a standardized plan file containing a structured Brief section to guide development.

How do I define acceptance criteria and module goals for a product effort?

Defining acceptance criteria and module goals requires validating problem assumptions through user interviews and codebase exploration. The finalized solution definition is then compiled into a structured plan document.

Does this PRD workflow require any specific dependencies or components?

No specific dependencies or components are required to run this PRD workflow. You only need to describe the problem to initiate the workflow and generate the plan file at the designated project path.

When should I use an interview-driven approach for product management planning?

An interview-driven approach is applicable when starting a new feature or product effort, or when documenting a planned solution. It validates assumptions and scopes the project by combining user feedback with repository discovery.

Why does the PRD plan file save to the ./tmp/<name>/ directory?

The plan file saves to the ./tmp/<name>/plan.md path to provide a standardized location for easy handoff. This ensures the Brief section, module goals, and acceptance criteria are consistently accessible within the project structure.