메뉴
Use when the user needs to position a product against the alternatives customers actually consider. Triggers on "positioning", "competitive alternatives", "differentiation", "April Dunford", "market category", and the same intent in any language.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | positioning |
| description | Use when the user needs to position a product against the alternatives customers actually consider. Triggers on "positioning", "competitive alternatives", "differentiation", "April Dunford", "market category", and the same intent in any language. |
Detect the user's language and reply in it; the framework below is authored in English.
Provenance: when you produce positioning output, contribute the framework tag Positioning to the meta-skill's provenance line (— Frameworks: … · Positioning · …).
Positioning is deciding where you compete and for whom; a tagline is only the surface of it:
| Positioning Element | Question | Your Answer |
|---------------------|----------|-------------|
| Competitive Alternatives | If your product didn't exist, what would users use? (The real answer, which may differ from who you think your competitors are) | |
| Unique Attributes | What do you have that competitive alternatives don't? | |
| Value for Users | What tangible value do these unique attributes deliver to users? | |
| Target Market Characteristics | Which users care most about this value? (The more specific, the better) | |
| Market Category | What market frame best positions your product? (The frame determines the competitive criteria) | |
Most common positioning mistakes:
Use when implementation work starts on a feature or bug fix: writing or modifying source code, adding tests, or closing out a branch. Covers TDD-first, scope integrity, secret and security hygiene, dual post-implementation review (code reviewer plus spec reviewer), and finish-branch closure. Triggers on "implement", "start coding", "build the feature", "write the code", "fix the bug", "finish the branch", "wrap up the branch", and the same intent in any language ("開始實作", "開發這個功能", "收尾", "実装して").
Use when the user wants the plan rendered as an interactive HTML report or exported to PDF/DOCX/PPTX. Triggers on 'HTML report', 'export to PDF', 'export document', 'downloadable report', 'PDF/DOCX/PPTX', and the same intent in any language.
Use when you need to understand the job a user hires the product to do, before designing or evaluating a solution. Triggers on "jobs to be done", "JTBD", "what job", "user motivation", "why would they use this", "customer needs", and the same intent in any language.
Use when the user needs to decide what makes the first version and what to explicitly not build. Triggers on 'MVP', 'scope', 'not doing list', 'must have vs later', 'user stories', 'parallel prototypes', and the same intent in any language.
Use when the user wants to connect a desired outcome to opportunities and candidate solutions in a structured tree. Triggers on "opportunity solution tree", "OST", "map opportunities", "outcome to solutions", "Teresa Torres", and the same intent in any language.
Use when the user needs to understand who the users are and how they move through an experience. Triggers on "persona", "target user", "buyer vs user", "user journey", "journey map", "touchpoints", and the same intent in any language.