Product Management

Independently maintained, portable procedures for customer problem discovery, product decisions, requirements and experiments. The packaged workflows are self-contained; facts, targets, constraints and commitments stay consumer-owned.

Skill	Use it to
product-discovery	Frame an unmet need from customer evidence and competing explanations.
product-prioritization	Compare defined options using supplied outcomes and constraints.
product-requirements	Describe observable behavior, outcome measures and small useful slices.
product-experiments	Design or assess a falsifiable test with an observation plan and decision criteria.

Inspect factual evidence before asking questions. Questions should resolve product choices or material gaps; none of these workflows requires an interview when the context is sufficient. Use the consumer's domain language and retain negative evidence, confounds and unknowns. Estimates, baselines and targets need support rather than invented precision.

For ideas approaching commitment, conditional decision pressure-testing guidance connects consequential assumptions, credible alternatives, independent disconfirming evidence and tests that can justify building, changing, deferring or stopping. It introduces no mandatory interview or numeric scoring model.

The result is a product decision or learning artifact, with open questions visible. Technical owners assess implementation feasibility. Project Management covers authorized execution and tracking; Product Development covers implementation; Communication covers prose. Drafting a brief or experiment does not authorize outreach, live instrumentation, tracker updates, rollout or provider mutations.

Product Management's optional evidence-based skill routes are documented in the workflow hooks guide.