prd

Generate a PRD from conversation context and publish it to the issue tracker.

38|6|Updated Sep 13, 2012
One-click install
npx skills add https://github.com/pixelastic/oroshi --skill prd-pixelastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/pixelastic/oroshi/tree/main/tools/ai/claude/config/skills/prd
Command: npx skills add https://github.com/pixelastic/oroshi --skill prd-pixelastic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Core Features & Use Cases

  • Synthesize the current context and repository understanding into a structured PRD.
  • Sketch out major modules and testing considerations to inform planning.
  • Publish the generated PRD to the project issue tracker using the standard workflow (prd-end).
  • Ensure the PRD aligns with project glossary terms and stakeholder expectations.

Quick Start

Provide the current conversation context and project details to generate a 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 PRD from existing conversation context?

To generate a PRD from conversation context, provide the current project details and the tool will synthesize the context into a structured PRD.md without conducting an interview, ensuring it aligns with stakeholder expectations.

What is the best way to turn codebase understanding into product requirements documentation?

The best way to turn codebase understanding into product requirements documentation is to use a tool that explores the repository, outlines major modules, and drafts a structured PRD.md using a provided template.

Can I automatically publish a generated PRD to my project issue tracker?

Yes, you can automatically publish a generated PRD to your project issue tracker by triggering the standard prd-end workflow after the documentation is drafted.

Does generating a PRD this way require interviewing stakeholders?

Generating a PRD this way does not require interviewing stakeholders, as it directly applies existing context and codebase understanding to satisfy product requirements without user interviews.

How to ensure generated product requirements align with project glossary terms?

To ensure generated product requirements align with project glossary terms, the tool synthesizes the current context and checks the drafted PRD.md against project terminology and stakeholder expectations.