skills.rest
Oatse
OatseCOMMUNITY
Explore all skills by this author →
GitHub

to-prd

Generates a PRD from conversation context and publishes it to the project issue tracker.

Updated May 23, 2026
Search Tags:#planning#documentation#issue tracker#user stories#prd#product requirements#triage
One-click install
npx skills add https://github.com/Oatse/CWE-Automation --skill to-prd-oatse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/Oatse/CWE-Automation/tree/main/.agents/skills/to-prd
Command: npx skills add https://github.com/Oatse/CWE-Automation --skill to-prd-oatse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a long planning conversation into a structured, actionable PRD is tedious and error-prone. This Skill synthesizes the current conversation context and codebase understanding into a complete PRD and publishes it directly to the project issue tracker, without re-interviewing the user. ## Core Features & Use Cases - Context Synthesis: Converts the existing conversation and codebase exploration into a structured PRD covering problem statement, solution, user stories, implementation decisions, testing decisions, and scope. - Module Planning: Identifies deep modules to build or modify, confirms them with the user, and records architectural and testing decisions. - Issue Tracker Publishing: Publishes the finished PRD to the project issue tracker and applies the ready-for-agent triage label. - Use Case: After discussing a new feature with the AI and exploring the repo, ask it to produce the PRD — it writes the document using the project's domain glossary and ADRs, then files it as a triaged issue ready for implementation. ## Quick Start Turn our current conversation into a PRD and publish it to the issue tracker.

Frequently Asked Questions about to-prd

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

FAQPage Schema
How do I create a PRD from an AI conversation?▼

Invoke the to-prd skill after discussing the feature. It synthesizes the existing conversation context and codebase exploration into a structured PRD with problem statement, user stories, and implementation decisions, without asking you new interview questions.

What sections does a generated PRD include?▼

The PRD includes a problem statement, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and further notes. It avoids specific file paths or code snippets except for decision-rich prototype excerpts.

Does the PRD skill publish to an issue tracker?▼

Yes. After writing the PRD, it publishes the document to the project issue tracker and applies the ready-for-agent triage label. The tracker and label vocabulary must be configured first via the setup command.

When should I not use conversation-to-PRD generation?▼

Avoid it when requirements are not yet discussed, since the skill does not interview the user and only synthesizes existing context. Run it after the feature scope, modules, and testing expectations have been talked through.

Why does the skill ask about modules before writing the PRD?▼

It identifies deep modules with simple, testable interfaces and confirms them with you before writing. This ensures the implementation and testing decisions in the PRD match your expectations.

Related Skills

Explore More Product & Management Skills→
IsKenKenYaIsKenKenYa
2

to-spec

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

Community
Intermediate
arndvsarndvs

do-work

Implements tasks through a plan, test, validate, commit, and preflight execution loop.

Community
Advanced
haryelramalhoharyelramalho

domain-modeling

Creates CONTEXT.md glossaries and ADR files documenting architectural decisions and vocabulary per bounded context.

Community
Advanced
danievanzyldanievanzyl
1

to-prd

Synthesize conversation context into a formal PRD and publish it to the issue tracker.

Community
Advanced