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'.
日本語の概要は準備中です。原文の説明を表示しています。
Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Wing-1 deep-thinking skill for articles, papers, opinion pieces, case studies, and long-form decision documents. Routes the user's content through 8 thinking frameworks at four depth levels (Quick / Standard / Deep / Research) and returns insight tied to the user's goal, not framework completion.
Do NOT use when:
agent-docs-writing or write a direct summary.judge-bug-hunter, judge-code-quality, or adversarial-review.adversarial-review (diff-bound) or threat-modeling.bug-analyzer or systematic-debugging.| Depth | Time | Frameworks | Reference module |
|---|---|---|---|
| L1 — Quick | ~15 min | SCQA, 5W2H | scqa-framework, 5w2h-analysis |
| L2 — Standard | ~30 min | L1 + Critical Thinking, Inversion | + critical-thinking, inversion-thinking |
| L3 — Deep | ~60 min | L2 + Mental Models, First Principles, Systems Thinking, Six Hats | + mental-models, first-principles, systems-thinking, six-hats |
| L4 — Research | 120 min+ | L3 + Cross-source comparison via web search | + comparison-matrix |
Every framework module is a project-local guideline under docs/guidelines/agent-infra/. Nothing is loaded from upstream at runtime.
Open with ONE decision point (per ask-when-uncertain — a single numbered-options block answerable with a single number is one question; never three separate asks):
Depth levels are scope descriptors, not wall-clock promises (per direct-answers — no duration estimates): L1 skim · L2 standard · L3 deep · L4 exhaustive-research.
If the user does not answer, default to L2 Standard with auto-selected frameworks.
Auto-suggest matrix:
| Content type | Default frameworks |
|---|---|
| Strategy / business article | SCQA + Mental Models + Inversion |
| Research paper | 5W2H + Critical Thinking + Systems Thinking |
| How-to guide | SCQA + 5W2H + First Principles |
| Opinion piece | Critical Thinking + Inversion + Six Hats |
| Case study | SCQA + Mental Models + Systems Thinking |
Regardless of depth, open with two short blocks:
2A — Basic structure.
📄 Type: [article/paper/report]
🎯 Core thesis: [one sentence]
Structure:
├─ Argument 1 → [key support]
├─ Argument 2 → [key support]
└─ Argument 3 → [key support]
Key concepts: [3–5 terms with one-line definitions]
2B — SCQA breakdown. Apply the four-element decomposition from scqa-framework:
**S (Situation)**: [context the article establishes]
**C (Complication)**: [problem identified]
**Q (Question)**: [core question]
**A (Answer)**: [main solution / conclusion]
Structure quality — clarity / logic / completeness: [★★★☆☆]
2C — 5W2H gap check (L1+). Quick scan: which of What, Why, Who, When, Where, How, How much are well-covered, partial, or missing? Flag the 1–2 most critical gaps.
Load only the frameworks the user's depth bought. Each framework follows the same pattern: load reference module → apply lens → produce one fixed-shape block.
L2 additions:
critical-thinking) — argument strength score (X/10), strengths, weaknesses, logical fallacies detected.inversion-thinking) — pre-mortem on the article's recommendation: "how would this fail?", missing risk factors, mitigations.L3 additions:
mental-models) — pick 3–5 models from different disciplines (physics, biology, psychology, economics, math), apply each lens, surface cross-model patterns.first-principles) — strip to fundamental truths, validate each core assumption, rebuild from base.systems-thinking) — map relationships, feedback loops, leverage points.six-hats) — White (facts), Red (feelings), Black (cautions), Yellow (benefits), Green (creativity), Blue (process).L4 addition:
comparison-matrix) — web-search 2–3 related sources, compare SCQA across sources, identify consensus vs divergence, synthesize integrated perspective.verify-before-complete (completion evidence).Output shape is driven by Step 0 goal, not by frameworks applied. Pick exactly one of the four blocks below.
For problem-solving: Applicable solutions (2–3 from content) → Application plan with timed action steps → Success metrics → Risk mitigations from Inversion.
For learning: Core concepts (definition + example) → Mental models gained → Connections to prior knowledge → First Principles fundamental question → 3 verification questions (understanding / application / evaluation).
For writing reference: Key arguments + evidence (with paragraph citations) → Quotable insights with context → Critical analysis (strengths for citing, limitations for balanced discussion) → Alternative perspectives from Mental Models → Gaps and counterfactuals.
For decision-making: Options presented → Multi-model evaluation (economic + risk + systems lens) → Six Hats decision analysis → Scenario analysis (best / worst / most likely) → Synthesized recommendation.
Regardless of goal, close with three fixed blocks:
## 🎯 Top 3 takeaways
1. **[Insight]** — Why it matters: [...] · One action: [specific, time-bound]
2. **[Insight]** — Why it matters: [...] · One action: [specific, time-bound]
3. **[Insight]** — Why it matters: [...] · One action: [specific, time-bound]
## 💡 Quick win — one tiny, specific action for the next 24 hours.
## 🧭 Frameworks used
✅ SCQA ✅ 5W2H ✅ Critical ✅ Inversion
□ Mental Models □ First Principles □ Systems □ Six Hats
adversarial-review / judge-bug-hunter.content-quoting-floor (≤15 words, one quote per source).asking-and-brevity-examples § Volatile-fact freshness.All 8 framework modules are project-local guidelines under docs/guidelines/agent-infra/ (full text adopted under the Reference-Guideline Sunset Policy). Each carries an ## ADOPT citation footer pinning its MIT upstream origin.
scqa-framework — situation / complication / question / answer decomposition.5w2h-analysis — completeness check (7 questions).critical-thinking — argument quality / fallacy detection.inversion-thinking — pre-mortem on decisions, distinct from adversarial-review.mental-models — Munger's multi-discipline toolkit.first-principles — fundamental-truth extraction.systems-thinking — feedback loops + leverage points.six-hats — White / Red / Black / Yellow / Green / Blue protocol.comparison-matrix — cross-source synthesis (L4 only).Deprecated — on-demand upstream loading. Earlier revisions of this skill described loading some modules "on demand from a SHA-pinned URL", backed by an
external_sourcefrontmatter pin. That capability was never wired (no fetcher ever consumed the pin; it was schema-only metadata), so the pin and itsrefresh_trigger/sunset_criterionbundle have been removed — every module is local, no runtime fetch is needed. If a future revision genuinely needs live upstream content, build an explicit fetch step; do not reintroduce a non-functional metadata pin.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。