to-prd

To generate a PRD from conversation context, you need a well-defined discussion scope and codebase understanding. The Skill analyzes the current conversation to extract requirements and produces a document covering the problem statement, user stories, and implementation decisions.

Yes, you can automatically publish a PRD to an issue tracker. The Skill takes the synthesized product requirements document and publishes it directly to the project's issue tracking system using a predefined label for further triage.

To synthesize conversations into product requirements, you need a well-defined conversation context and an understanding of the codebase structure. The Skill uses these inputs to automate requirement synthesis and reduce manual interviews.

Yes, generating a PRD requires codebase understanding. The Skill analyzes conversation context alongside the project's codebase structure to accurately outline the problem statement, solution, and testing decisions in the final document.

The best way to document requirements during project planning is to activate this Skill with your conversation context. It quickly synthesizes the discussion into a structured PRD and publishes it to the issue tracker to streamline the process.

A generated Product Requirements Document includes the problem statement, solution, user stories, implementation decisions, and testing decisions. These sections are automatically extracted and synthesized from the provided conversation context.