dev3-prd

To write a PRD with clear requirements, you must first clarify unknowns by generating targeted questions and resolving them using codebase context. This ensures the final product requirements document contains a clear problem statement and concrete implementation details.

Pyramid principles in PRD creation structure design specs by leading with the core problem statement, then supporting it with design rationale and implementation details. This top-down approach ensures cross-team coordination aligns with the primary objective.

You generate targeted questions to resolve unknowns by analyzing the feature request against existing codebase context. Answering these questions ensures all design explorations have concrete implementation details before the design document is drafted.

Yes, this PRD workflow integrates directly into the dev-workflow to guide teams from initial feature request to final PRD. It enforces requirements for clear problem statements and design rationale throughout the cross-team coordination process.

You should not use automated question generation for product requirements documents when the codebase lacks sufficient context to answer the targeted questions. Without existing code to inspect, resolving unknowns for design explorations becomes speculative rather than concrete.