prd-personas

Defining user personas for product requirement documents involves capturing roles, jobs-to-be-done, constraints, and success metrics. This skill facilitates discovery sessions to distinguish primary, secondary, and out-of-scope user segments before generating structured markdown documentation.

A broad target audience causes feature prioritization issues because product requirements lack a clear definition of who the product is for and what success looks like. Explicitly identifying excluded personas prevents feature creep and resolves design tradeoffs.

The best way to identify out-of-scope user segments for PRD scope clarification is through a structured interview process. This skill guides you through discovery sessions to explicitly mark excluded personas, preventing feature creep and resolving design tradeoffs.

Yes, you can generate structured markdown documentation for user research. Based on predefined templates, this skill outputs consistent product definition documents detailing captured roles, jobs-to-be-done, and success criteria for your project.

You need to explicitly identify excluded personas in product management when a team is stuck on feature prioritization due to a poorly defined target audience. Clarifying out-of-scope segments resolves design tradeoffs and sharpens overall product scope.