to-prd

You can generate a PRD by synthesizing the current conversation context and codebase understanding into a structured document. The Skill extracts requirements, goals, success criteria, risks, and milestones to produce a production-ready PRD.

The best way to structure a PRD is using a template-driven approach that automatically applies your standard project template and integrates Architecture Decision Records and glossary terms when available, ensuring stakeholder alignment and consistent documentation.

Yes, you can publish a PRD directly to an issue tracker. The Skill optionally publishes the generated product requirements document to your project's issue tracker and applies appropriate triage labels for immediate team action.

PRD generation works without predefined ADRs or glossary terms. The Skill integrates these elements into the structured document when available, but it can still synthesize feature scope, timelines, risks, and success criteria from the current context alone.

You need a production-ready PRD for product discovery and planning tasks when transitioning from initial discussion to execution. It fulfills structured formatting requirements, covers feature scope and timelines, and ensures stakeholder alignment before development begins.

A PRD for effective stakeholder alignment should include feature scope, timelines, risks, success criteria, and milestones. It applies structured formatting, integrates ADRs and glossary terms, and optionally publishes to an issue tracker with triage labels.