Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when locking the market frame — category, segment, alternative, point-of-view — before messaging, launch, or pricing rides on it. Triggers on 'who are we for', 'opposable audit'.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Do NOT use for peer-versus-peer feature comparison (route to
competitive-positioning), copy generation (route to
messaging-architecture), or pricing-tier construction.
docs/contracts/mental-models.md § 1.mental-models.md § 30.context-spine.Write one sentence: "<Segment> hires <category> to make progress
in <situation>, when motivated by <pressure>, expecting
<outcome>." If you cannot finish the sentence, route to
customer-research; positioning
without job-evidence is invention, not earning.
Each anchor is one sentence; ambiguity here propagates.
For every anchor, write the strongest counter a credible peer would make. Validate each anchor against the rule "a credible peer holds the opposite" — if no counter exists, the anchor is unfalsifiable (either trivially true or invented) and must be replaced before continuing.
The four counters become the assumption ledger: explicit beliefs the positioning rides on. Each gets a re-evaluation trigger (event + metric + threshold) the team will watch for.
Write three sentences in the form "We are not for <adjacent segment>, even though <surface similarity>, because <reason grounded in the product slot>." Non-goals are how positioning earns its category — without them every prospect looks like a fit and the segment dissolves.
For each anchor, walk the chain "if this is true, then…" through two consequences. If a consequence contradicts the product slot, the segment slot, or a shipped commitment, the anchor is wrong — fix the anchor, not the consequence.
Hand the four anchors + assumption ledger + non-goals to
messaging-architecture for
primary-message construction. Do not write copy inside this
skill — that is messaging-architecture's job.
WHEN to use this
WHEN NOT to use this
competitive-positioning.messaging-architecture.fundraising-narrative.unit-economics-modeling.positioning.md — the four anchors (category · segment ·
alternative · point-of-view), one sentence each, opposable.assumption-ledger.md — one row per anchor: the strongest
peer-counter, the load-bearing belief, the re-evaluation trigger
(event + metric + threshold).non-goals.md — three sentences naming adjacent segments the
product refuses to serve, each grounded in the product slot.Mid-market HR analytics tool, contested category:
messaging-architecture for primary
message + audience-by-message matrix.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defining or auditing the activation event — aha-moment selection, retention correlation, falsifiable definition. Triggers on 'what is our aha moment', 'redefine activation'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarial critique — devil's advocate, stress-test, honest teardown ('poke holes', 'be brutal', 'was hältst du davon'); explicit request only. Routine code or design review → code-review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.
日本語の概要は準備中です。原文の説明を表示しています。
Use for an adversarial red-team / blue-team / auditor review of an AI agent's CONFIG + behaviour (rules, skills, MCP, hooks, permissions) — attack-chain → defensive-gap list, not a code audit.
日本語の概要は準備中です。原文の説明を表示しています。