メニュー
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.
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.
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.
Maps the surface problem, deeper problem, cost of inaction, failed attempts, desired outcomes, transformation gap, and priority problem. Use after market signal and user context, before offer creation.
| name | strat-message-system |
| description | 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. |
Explain the offer to a technical audience with clarity, specificity, and desire.
../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md..ai/strategy/signal/* and .ai/strategy/offer/*..ai/strategy/gtm/message-system.md.# Message System
## Positioning
Format: [Product] is a [category] for [audience] who want [outcome] without [pain/sacrifice].
## Main Promise
## Message Pillars
## Headline Options
## Subheadline Options
## Hook Bank
### Pain Hooks
### Desire Hooks
### Mechanism Hooks
### Proof Hooks
### Speed Hooks
### Risk Reversal Hooks
### Technical Hooks
## Claims
### Safe Claim
### Bold Claim
### Specific Claim
### Technical Claim
## Objection Matrix
| Objection | Hidden Fear | Response | Proof Needed |
|---|---|---|---|
## CTA Options
## FAQ Seeds
## Words To Use
## Words To Avoid
## Non-Marketing Explanation
Explain the offer like speaking to a skeptical developer.
Avoid "revolutionize", "transform your life", "scale effortlessly", "dominate the market", and empty "irresistible offer" language. Prefer clarify, validate, reduce waste, define scope, prove demand, ship, test, and measure.