prd-mode

Generate structured Product Requirements Documents with mandatory sections and saved artifacts.

1|Updated May 7, 2026

Search Tags:#planning #documentation #prd #user-stories #acceptance-criteria #stakeholders #product-requirements

Ready to run

npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill prd-mode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-mode
Source: https://github.com/ChristopherAlphonse/calphonse-skills/tree/main/prd-mode
Command: npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill prd-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to produce clear, actionable PRDs that guide development and satisfy stakeholders. This skill helps junior developers structure the problem, goals, user stories, acceptance criteria, and scope into a concise PRD.

Core Features & Use Cases

Guided PRD structure with sections: Overview, Goals, User Stories, Functional Requirements, Non-Goals, Technical Considerations, and Success Metrics.
Interactive clarification workflow that uses /interrogate-me to surface assumptions, risks, and unanswered questions, integrating them into the PRD.
Auto-generates a saved artifact at /tasks/prd-[feature-name].md with the final PRD document.

Quick Start

Ask the assistant to generate a PRD for a described feature and begin the iterative clarification workflow using /interrogate-me.

Frequently Asked Questions about prd-mode

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

FAQPage Schema

How do I create a product requirements document with user stories and acceptance criteria?▼

To create a product requirements document, you need a structured PRD covering problem statements, goals, user stories, and acceptance criteria. This skill automates structuring these elements into a standardized format saved as a markdown artifact.

What sections should be included in a PRD for software feature requests?▼

A PRD for software features should include Overview, Goals, User Stories, Functional Requirements, Non-Goals, Technical Considerations, and Success Metrics. These mandatory sections ensure stakeholders have sufficient context for development decisions.

How do I identify missing requirements and risks when writing a PRD?▼

Identifying missing requirements and risks when writing a PRD requires an interactive clarification workflow. This skill uses an interrogation process to surface assumptions, risks, and unanswered questions, integrating the findings directly into the document.

Can I use this PRD generation process for junior developers on my team?▼

Yes, this PRD generation process is specifically designed to guide junior developers. It walks them through problem definition, goal setting, and scope clarification to produce development-ready specifications for feature requests.

What is the best way to standardize PRD structure across multiple feature requests?▼

The best way to standardize PRD structure across features is to enforce mandatory sections and save outputs to a consistent file path. This skill auto-generates artifacts at a designated directory, ensuring uniform documentation.

What format is the final PRD document saved in?▼

The final PRD document is saved in markdown format. The auto-generated artifact is stored at a specific path, ensuring the structured product requirements are easily accessible for future development reference.