product-discovery

Defining Jobs to be Done (JTBD) requires capturing the underlying user motivations and business rules driving behavior. This skill facilitates product discovery by structuring user needs analysis to ensure features address actual problems before technical decomposition begins.

Generating a PRD with user stories and acceptance criteria is best handled through lightweight formats that outline desired outcomes and non-functional requirements. This skill creates product requirements documents ensuring alignment between business wants and customer needs.

You need product discovery for user stories when starting development on a new feature or idea. It grounds requirements in real customer problems, preventing the development of solutions that do not address actual user needs.

Structuring product analysis using a JTBD-first approach involves formally documenting the user's problem, desired outcomes, and specific requirements. This skill supports structured analysis of user needs before any technical decomposition occurs.

The product discovery process does not require specific technical dependencies. It relies on adhering to a JTBD-first approach and lightweight PRD formats to efficiently document user needs and business rules.

Yes, you can use this to formally document non-functional requirements for a Product Backlog Item (PBI). The skill generates comprehensive PRD documents that include acceptance criteria and specific requirements for new features.