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 sequencing market entry — geo / segment / vertical, beachhead selection, regulatory-delta. Triggers on 'should we enter market X', 'which segment first'.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Do NOT use for build-vs-buy decisions on capability gaps (route to build-buy-partner (P1)), positioning narrative (route to competitive-positioning (P3); this skill composes P3), or per-customer economics within the entered market (route to unit-economics-modeling (O1)).
mental-models.md § 23.mental-models.md § 21.mental-models.md § 16.Pick one of three axes; do not mix:
Mixing axes ("enter European healthcare enterprise") = three entries simultaneously. The correct framing is to pick one axis at a time and sequence the others.
Within the chosen axis, score 3–5 candidate beachheads on:
regulatory-regime slot; e.g. EU + B2C + processing PII = GDPR-floor; EU + B2B + no PII = thin delta).The beachhead is rarely the largest segment; it's the segment where we win cleanly and from which adjacent segments become accessible.
Three concrete cost categories — each named, not estimated:
Total entry cost = these three. Compare against runway-frame.md (O3) for whether the band has headroom.
For the chosen beachhead, write the 18-month failure mode:
If the failure mode has no mitigation, the entry is not ready. Sit with it.
Beachhead = first move. Map the next 2–3 expansion moves explicitly:
Un-sequenced beachhead wins are dead-ends. The sequence is the long-game; the beachhead is just the first move.
Before emitting the entry plan, verify three things:
runway-frame.md (O3) band; if it doesn't, the entry is not yet financeable and must be deferred or staged.All three must pass. If any fails, the entry plan is not ready to emit; return to the failing step.
Produce the entry plan artifact. P2 composes P3 (competitive-positioning) for the narrative against incumbents in the target segment.
WHEN to use this
WHEN NOT to use this
build-buy-partner (P1).competitive-positioning (P3); this skill composes P3.unit-economics-modeling (O1).funnel-analysis and content-funnel-design.entry-axis-frame.md — chosen axis (geo / segment / vertical), why this axis first, what's deferred.beachhead-scorecard.md — 3–5 candidate beachheads scored on the four Step-1 dimensions; named winner with reasoning.entry-cost-table.md — sales-motion delta, product delta, operating cost; compared against runway band.expansion-sequence.md — beachhead + next 2–3 moves, with the unlock-mechanism named per move.Horizontal SaaS, US-only, mid-market, considering EU expansion.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。