product-intelligencelisted

# Product Intelligence Own the transition from an ambiguous idea to an approved, evidence-backed product direction. Keep one decision and evidence context, then hand each activated artifact to its existing specialist owner. ## Trigger boundary Use this skill to: - evaluate or develop a business or software idea end to end; - research users, demand, competitors, substitutes, pricing, sizing, or trends for a pending product decision; - determine roles, entities, lifecycle, permissions, workflows, information architecture, experience states, technical concerns, or future-change boundaries before implementation; - turn uncertain product direction into an evidence-backed implementation proposal. Do not use it for: - a clearly bounded implementation task with settled requirements; - a standalone PRD or task breakdown, owned by [`prd-taskbreaker`](../prd-taskbreaker/SKILL.md); - an existing specification-pack traceability audit, owned by [`development-spec-suite`](../development-spec-suite/SKILL.md); - an isolated market fact lookup with no product decision; - visual polish after product behavior is settled; - code implementation or runtime verification. ## Decision brief Before prescribing artifacts or solutions, record: - permanent context ID, pending decision, accountable owner, and deadline or horizon; - risk if wrong, target actor/population and geography, current alternatives, and product state; - goals, non-goals, scope, constraints, appetite, acceptable uncertainty,