prd-development

Structured PRD creation from discovery notes to engineering-ready requirements document. Guide product managers through structured PRD (Product Requirements Document) creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document. Use this to move from scattered notes and Slack threads to a clear, comprehensive PRD that aligns stakeholders, provides engineering context, and serves as a source of truth—avoiding ambiguity, scope creep, and the "build what's in my head" trap. This is not a waterfall spec—it's a living document that captures strategic context, customer problems, proposed solutions, and success criteria, evolving as you learn through delivery. A PRD (Product Requirements Document) is a structured document that answers: When running this workflow as a guided conversation, use workshop-facilitation as the interaction protocol. It defines: This file defines the workflow sequence and domain-specific outputs. If there is a conflict, follow this file's workflow logic. Use template.md for the full fill-in structure.