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 mapping funnel-stage to content shape — conversion-pathway, content-as-system, leverage-point selection. Triggers on 'design our content funnel', 'why does mid-funnel leak'.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
editorial-calendar) is locked but one funnel stage is leaking and there is no content shape that would catch it.Do NOT use to plan publishing cadence (route to editorial-calendar),
diagnose quantitative drop-off (route to funnel-analysis), or
draft the asset itself (downstream of this skill).
docs/contracts/mental-models.md § 14.mental-models.md § 6.mental-models.md § 16.context-spine.Identify the leaking stage from
funnel-analysis and the cadence
classification from editorial-calendar.
The content funnel design is a response to a diagnosed leak —
without the diagnosis, content investment is uniform and the
constraint stays where it is.
Review existing assets stage-by-stage. For each, identify shape (awareness explainer, comparison, deep-dive, demo, case study, calculator, onboarding walkthrough) and whose question it answers. The output is a stage × shape grid with current investment weight. Most teams discover their grid is bottom-heavy or middle-empty.
The leverage point is the structural stage, not the leaking one. (The leaking stage is the symptom; the leverage point is where the design choice ripples.) Often: mid-funnel proof is the leverage point when the leak is decision-stage, because mid-funnel proof loads the decision-stage call with conviction. Name the leverage point explicitly; document why it is structural, not parameter.
For each funnel stage in the spine slot, lock the load-bearing content shape:
editorial-calendar).A pathway is two assets in sequence that an audience plausibly walks. For each pathway, name the first-asset → second-asset edge and the question the second answers that the first surfaced. Pathways without a credible edge are wishful inventory, not a funnel.
Validate the design on three checks:
funnel-analysis has a shape designed for it — not just more
content, but the shape the audience asks for at that stage.Hand the artefacts to editorial-calendar
for cadence assignment, to funnel-analysis
for a re-diagnosis four weeks after launch, and to
activation-design for the
activation-stage handoff.
WHEN to use this
WHEN NOT to use this
editorial-calendar.funnel-analysis.activation-design.stage-shape-grid.md — stage × shape matrix, current investment vs. designed investment, leverage-point cell marked.conversion-pathways.md — one row per pathway: first-asset → second-asset edge, question the second asset earns, audience-matrix cell it serves.leverage-point-rationale.md — named leverage stage, why structural, not parameter argument, and the leading-indicator threshold the design will be re-checked against.Mid-market HR analytics, funnel-analysis diagnosed mid-funnel leak (decision-stage conversion is fine, but mid-funnel disqualifies before reaching it):
editorial-calendar re-allocates campaign weight to mid-funnel; funnel-analysis re-diagnoses at week 4.→ Final prose pass for audience-facing output: humanizer — remove AI-writing tells before delivery.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。