to-prd

To generate a PRD from a design discussion, synthesize the conversation context and repository understanding into a structured document with clear scope, success criteria, and milestones. This aligns stakeholders and produces a ready-to-publish artifact without manual drafting.

Yes, you can publish a product requirement document directly to an issue tracker. The skill outputs a ready-to-publish artifact and applies appropriate triage labels for downstream planning and review.

PRD synthesis works with existing Architecture Decision Records by honoring ADRs and glossary terms during document generation. This ensures the final product requirement document aligns with established technical decisions and vocabulary.

The best way to ensure consistent PRD formatting is using a template-driven approach that applies a standardized PRD template and glossary. This guarantees reproducibility and uniform structure across all generated product requirement documents.

To scope features and define acceptance criteria, use PRD synthesis during feature scoping sessions to transform discussions into structured milestones. This captures the problem, scope, and success criteria to align stakeholders for planning.

You need a formal PRD for project planning when a stakeholder requires structured alignment on goals and scope. Use it during design reviews or planning sessions to convert repository context into a publishable issue tracker artifact.