prd

Create product requirements documents through interactive agent-driven sessions.

7|1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/Nirusan/claude-config --skill prd-nirusan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/Nirusan/claude-config/tree/main/skills/prd
Command: npx skills add https://github.com/Nirusan/claude-config --skill prd-nirusan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation of Product Requirements Documents (PRDs) by guiding users through an interactive session to define features, requirements, and scope.

Core Features & Use Cases

  • Interactive PRD Generation: Engages in a dialogue to capture all necessary PRD details.
  • Feature-Specific PRDs: Can create PRDs tailored to individual features within a project.
  • Use Case: Kickstart a new feature development by using /prd --feature=user-authentication to generate a detailed PRD for the user authentication system.

Quick Start

Use the prd skill to create a main project PRD.

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 for a new feature?

A Product Requirements Document generated through this interactive session includes scope definition, user stories, functional and non-functional requirements, and success metrics to fully outline feature development.

Can I create feature-specific PRDs without rewriting the main project scope?

Feature-specific PRDs can be generated without rewriting the main project scope. The session focuses on defining the scope, user stories, and requirements for the individual feature while integrating existing project context.

What context does the PRD generation process need from existing project files?

The PRD generation process integrates with existing project context like brief.md and tech-stack.md files. This ensures the generated requirements and scope align with the established project brief and technical stack.

Does the PRD creation session define both functional and non-functional requirements?

Yes, the PRD creation session defines both functional and non-functional requirements. It also captures user stories and success metrics to provide a comprehensive product requirements document for your project.

What is the best way to define product scope and success metrics for development?

The best way to define product scope and success metrics is through an interactive PRD generation session. It systematically captures requirements and user stories to establish clear development boundaries and measurement criteria.