to-prd

Synthesize product conversations and codebase context into a structured PRD and publish it to the issue tracker.

4|2|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/saitarrun/devforge-ai --skill to-prd-saitarrun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-prd
Source: https://github.com/saitarrun/devforge-ai/tree/main/skills/prd-synthesis
Command: npx skills add https://github.com/saitarrun/devforge-ai --skill to-prd-saitarrun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of losing critical product context from conversations and the time-consuming, inconsistent process of manually drafting PRDs from chat history, ensuring requirements are captured accurately and aligned with project standards.

Core Features & Use Cases

  • Context-Aware PRD Synthesis: Automatically pulls relevant details from existing conversation and codebase context to generate a complete PRD without requiring additional user interviews.
  • Project Alignment: Ensures all PRD content uses the project's domain glossary and respects existing architectural decisions and ADRs.
  • Automated Publishing: Publishes the finished PRD directly to the project issue tracker with the correct ready-for-agent triage label, no manual follow-up needed.
  • Use Case: After a product discussion about adding OAuth login to your application, use this Skill to instantly generate a full PRD with user stories, implementation decisions, and testing plans, then publish it directly to your issue tracker for the engineering team to start work.

Quick Start

Use the to-prd skill to turn our current conversation about adding OAuth login into a published PRD on the project 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 generate a PRD from existing chat context without conducting user interviews?

You can generate a PRD from existing chat context by using a skill that synthesizes product conversations and codebase details into structured product requirements automatically. It pulls relevant details to create problem statements, user stories, and testing plans without requiring further user interviews.

Can I automatically publish user stories to an issue tracker from informal product discussions?

Yes, you can automatically publish user stories to an issue tracker from informal product discussions. The skill generates a complete Product Requirements Document and publishes it directly to the tracker with the ready-for-agent triage label applied.

How do I align new product requirements with existing architectural decisions and ADRs?

To align new product requirements with existing architectural decisions, the skill ensures all generated PRD content respects project domain glossaries and current architectural decision records. This maintains consistency across the software development lifecycle.

What is the best way to turn a conversation about adding OAuth login into a structured PRD?

The best way to turn an OAuth login conversation into a structured PRD is to synthesize the chat context into a formal document. The skill captures implementation decisions and testing plans, then publishes the full requirements directly to your issue tracker.

Does PRD synthesis work for agile workflows using existing codebase context?

Yes, PRD synthesis works for agile workflows by using existing codebase context. It formalizes informal product discussions into actionable requirements aligned with project standards, fitting smoothly into the software development lifecycle.

Do I need to manually format user stories before publishing them to the issue tracker?

No, you do not need to manually format user stories before publishing them. The skill automatically structures the synthesized product requirements into a complete document and publishes it to the issue tracker with the correct triage label.