What problem does it solve?
Manually drafting Product Requirement Documents (PRDs) from project conversations and codebase context is time-consuming, inconsistent, and often misses critical details discussed in prior team discussions.
Core Features & Use Cases
- Context Synthesis: Automatically compiles existing conversation history and codebase understanding into a structured PRD without requiring additional user interviews.
- Project Alignment: Uses the project's domain glossary and respects existing Architectural Decision Records (ADRs) to ensure the PRD matches team standards.
- Direct Publishing: Posts the finalized PRD directly to the project issue tracker with the appropriate triage label for immediate tracking.
- Use Case: If your team just finished a discussion about adding a new data export feature to your petroleum analytics platform, this skill will generate a complete PRD with user stories, implementation decisions, and testing plans and publish it to your GitHub issues for assignment.
Quick Start
Use the to-prd skill to turn our recent discussion about the new well log visualization feature into a published PRD on the project issue tracker.