paw-ps-strategist

To translate market intelligence into a product strategy, you provide curated audience and market data to generate a structured product brief, scope map, and packaging recommendations. This bridges research and execution decisions by aligning stakeholders.

Defining product scope for a v1 release involves creating a detailed scope map from audience insights. This process establishes ship-ready feature sets and clear boundaries to guide engineering teams during execution.

Creating an execution handoff spec requires translating packaging decisions and scope designs into executor-ready documents. The process generates a complete handoff specification to enable seamless delivery by engineering or operations teams.

Yes, you can use audience insights to determine product packaging. The process reads curated inputs to generate packaging recommendations and pricing plans that align with your defined product scope and market strategy.

Yes, you need curated market and audience intelligence as input before generating a product brief. The strategist relies on this provided data to shape the product, define scope, and write updates to curated product decision files.

Product decisions and context are saved directly to curated/product-decisions.md and curated/product-context.md. This ensures generated briefs, scope maps, and handoff specs are persistently available for downstream execution.