dev3-prd

To generate clarifying questions for a product requirements document, the Skill analyzes existing feature requests and design artifacts, then outputs unresolved unknowns marked as NEEDS INPUT for human review. It attempts to resolve questions automatically using repository context before soliciting user input.

The pyramid principle for structuring a PRD organizes information hierarchically into an Executive Summary, Component Details, and Implementation Details. This approach synthesizes feature context and design artifacts into a concise, actionable spec ready for engineering handoff.

You can turn feature exploration notes into a formal design doc by processing temporary context and exploration files alongside chosen designs. The Skill synthesizes these artifacts to produce a structured PRD and automatically triggers the implementation workflow upon completion.

Yes, you can automatically resolve PRD unknowns from your codebase. The Skill reads temporary context, exploration findings, and design files to answer clarifying questions, marking them as RESOLVED when sufficient information is found in the repository artifacts.

Yes, this PRD generation workflow supports human-in-the-loop clarification. After attempting to self-resolve unknowns from repository artifacts, it presents only the remaining unresolved questions to solicit necessary human answers before finalizing the product requirements document.

A limitation of automated PRD generation is its dependency on pre-existing exploration files and design artifacts within the .llm path. If the codebase lacks sufficient context, the Skill cannot auto-resolve unknowns and will require manual human input for unanswered clarifying questions.