skills.rest
scoots31
scoots31COMMUNITY
Explore all skills by this author →
GitHub

to-prd

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

Updated Apr 13, 2026
Search Tags:#feature planning#requirements gathering#user stories#prd#product requirements#github issue
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill to-prd-scoots31
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/to-prd
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill to-prd-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an exploratory conversation about a feature into a structured Product Requirements Document is tedious and often loses context. This Skill synthesizes the current conversation and codebase understanding directly into a complete PRD without re-interviewing the user. ## Core Features & Use Cases - Context Synthesis: Converts the existing conversation and codebase exploration into a PRD with no repeated questioning. - Module Planning: Identifies deep, testable modules to build or modify and confirms them with the user before writing. - Structured PRD Template: Produces problem statement, solution, extensive user stories, implementation decisions, testing decisions, and out-of-scope notes, then submits it as a GitHub issue. - Use Case: After discussing a new billing feature with your AI assistant, invoke this Skill to turn the discussion into a ready-to-review PRD filed as a GitHub issue for the team. ## Quick Start Ask the assistant to turn the current conversation 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 turn a conversation into a PRD?▼

Invoke the Skill after discussing the feature with your AI assistant. It synthesizes the existing conversation and codebase context into a structured PRD covering problem statement, user stories, and implementation decisions, then submits it as a GitHub issue.

How to write user stories for a product requirements document?▼

The Skill generates an extensive numbered list of user stories in the format: as an actor, I want a feature, so that a benefit. The stories cover all aspects of the feature discussed in the conversation.

Does the PRD generation require answering more questions?▼

No. The Skill explicitly does not interview the user; it synthesizes what is already known from the conversation. It only checks with the user about which modules to build and which ones need tests.

Can the PRD be submitted to GitHub automatically?▼

Yes. After writing the PRD using its built-in template, the Skill submits it directly as a GitHub issue, making it immediately visible to the team for review and tracking.

What are the limitations of conversation-based PRD generation?▼

The output quality depends on how much context the conversation contains. It avoids specific file paths and code snippets since they become outdated, so highly technical specifications may need manual detail added afterward.

Related Skills

Explore More Product & Management Skills→
jwh3timesjwh3times
1

to-spec

Synthesizes conversation context into a structured spec published to the project issue tracker.

Community
Intermediate
alysonhoweralysonhower
1

clavix-plan

Convert PRD documents into structured task breakdowns with dependencies.

Community
Intermediate
DonchitosDonchitos
24.7k

create-architecture

Generates a master game architecture document from GDDs, ADRs, and engine reference files.

Community
Advanced
MichaelSolatiMichaelSolati

to-prd

Synthesize conversation and codebase context into structured PRDs and publish them to the issue tracker.

Community
Intermediate