菜单
Defines the unique mechanism that explains why the offer works differently from the old way. Use after product-offer and before MVP scope.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Chooses the correct next action for prospects based on offer readiness, awareness, trust, friction, price, urgency, and MVP maturity. Use after message-system to define CTA and acquisition path.
Consolidates all Pi Strategy artifacts into the final handoff file .ai/strategy/handoff/strategy-brief.md for downstream SDD, build, or go-to-market packages. Use after acquisition-path.
Initializes the Pi Strategy workspace in a project by creating .ai/strategy directories, index.md, and optional .ai/steering guidance. Use before running the strategy pipeline in a new or existing project.
Identifies whether a raw product, SaaS, devtool, community, course, method, or service idea has enough reachable market signal to continue. Use at the beginning of Pi Strategy before user, offer, MVP, or build work.
Turns offer, mechanism, MVP, and proof into clear technical messaging: positioning, promise, pillars, hooks, claims, objection matrix, CTA options, FAQ seeds, words to use/avoid, and a skeptical developer explanation. Use after proof-system.
Defines the smallest MVP or deliverable capable of proving the offer and mechanism. Use after product-offer and unique-mechanism, before proof, messaging, acquisition, downstream deliverables, or build planning.
| name | strat-unique-mechanism |
| description | Defines the unique mechanism that explains why the offer works differently from the old way. Use after product-offer and before MVP scope. |
Explain why the solution works in a way the old way does not.
../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md..ai/strategy/signal/* and .ai/strategy/offer/product-offer.md..ai/strategy/offer/unique-mechanism.md.# Unique Mechanism
## Old Way
## Why The Old Way Fails
## New Way
## Mechanism Name
## Mechanism Summary
## Steps
Use 3 to 7 steps.
1.
2.
3.
## Why It Works
## Proof Hooks
## Visual Metaphor
## Mechanism One-Liner
## Risks
## Assumptions
## Open Questions
Avoid vague mechanisms like "we use AI to accelerate". Prefer concrete pipelines such as "Signal → Offer → MVP → Page".