to-prd

Generate a PRD from conversation context and submit it as a GitHub issue.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/paialex/ai-skills-bank --skill to-prd-paialex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/paialex/ai-skills-bank/tree/main/mattpocock_skills/engineering/to-prd
Command: npx skills add https://github.com/paialex/ai-skills-bank --skill to-prd-paialex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning scattered discussion and design context into a concrete PRD that can be reviewed and shared, without lengthy interviews.

Core Features & Use Cases

  • Context extraction: synthesize conversations and repo context into a structured PRD draft.
  • PRD generation: create a complete PRD with problem, solution, user stories, decisions, and scope.
  • GitHub integration: submit the generated PRD as a GitHub issue for traceability and collaboration.
  • Use cases: when aligning stakeholders on a new feature, starting productization from ongoing discussions, or documenting decisions after a sprint review.

Quick Start

Summarize the active discussion and code context into a PRD and submit it as a GitHub issue.

Frequently Asked Questions about to-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?

A PRD from conversation context is generated by this Skill automatically synthesizing ongoing dialogue and repo context into a structured draft, extracting problems, solutions, and user stories without requiring manual interviews.

Can I create a GitHub issue directly from product requirements?

Yes, creating a GitHub issue directly from product requirements is supported. The Skill integrates with GitHub to automatically submit the generated PRD as an issue, ensuring traceability and stakeholder collaboration.

What is the best way to formalize scattered product discussions into requirements?

The best way to formalize scattered product discussions into requirements is using context-aware extraction. This Skill turns scattered discussions and design context into a concrete, reviewable PRD, bypassing lengthy interview processes.

Do I need to conduct user interviews to generate product documentation?

No, conducting user interviews to generate product documentation is not required. This Skill relies on non-interactive, context-driven extraction from your current conversation to produce a complete PRD.

Does this PRD generation require manual formatting before submitting to GitHub?

No, PRD generation does not require manual formatting before submitting to GitHub. The Skill outputs a complete document with problem statements, user stories, decisions, and scope, then submits it directly as an issue.