product-brief

To turn a rough idea into a structured PRD, the skill uses guided conversational questioning to clarify your problem, audience, and constraints, then organizes the results into a stakeholder-ready document with goals, user stories, and scope.

The best way to write a product brief for early-stage planning is through guided discovery. This process surfaces missing context, captures assumptions, and defines success criteria to ensure your feature concept is fully refined before execution.

Yes, you can prioritize features and design user flows within a product requirements document. The skill supports product planning workflows by ranking features, defining scope, and planning milestones alongside the core PRD generation.

Yes, the product brief skill outputs markdown ready for project documentation. It generates a comprehensive spec including goals, risks, dependencies, out-of-scope items, and open questions formatted for immediate stakeholder tracking and review.

To capture assumptions and define scope when creating a PRD, the skill asks targeted conversational questions during the discovery phase. This clarifies constraints, identifies open questions, and establishes clear boundaries for your product features.

If your feature concept is too vague for stakeholder tracking, use the guided discovery process to refine it. The skill asks clarifying questions to extract concrete goals, dependencies, and milestones, transforming vague ideas into a structured spec.