What problem does it solve? Teams often write positioning statements that are vague, adjective-driven, or indistinguishable from competitors. This Skill runs a facilitated workshop that builds a defensible positioning statement from the ground up, starting with real competitive alternatives rather than the product's feature list. ## Core Features & Use Cases - Dunford build-order method: Works bottom-up through competitive alternatives, unique attributes, value and proof, target market, and market category before writing any statement. - Moore statement assembly with swap test: Fills the six-slot For/Who/Is a/That/Unlike template, then validates it by substituting the primary alternative to catch generic claims. - Facilitation loop with collapse rule: Asks at most 4 targeted questions, honours bypasses like "take your best guess", and skips interviewing entirely when upstream artifacts like PROBLEM_STATEMENT.md or PROTO_PERSONA.md already exist. - Use Case: Before a launch brief, a product manager runs the workshop to decide between three category frames, names the status quo as the primary alternative, and ships a positioning package with labelled proof points for sales enablement. ## Quick Start Run the positioning workshop for my product and help me build a defensible positioning statement with the differentiation reasoning behind it.
