スキルを探す

調査・スパイクを「問いに答える」でなく「判断の危険を潰す」ために走り切る。何を決めるための調査かを計画として出して依頼者と合意し、裏付け一つで閉じず反証で開き、結論から読める形で報告するまでを担う。次の判断・見積もりが決められず調べる必要があるとき、使い捨ての実験で確かめたいときに使う。

事業仮説を支える一次/二次情報を整理し、意思決定に足る「根拠」「不確実性」「次の調査」を可視化する。でたらめな引用や推測の断言を避け、出典の実在を重視する。

Work the review of a research run with rs_review — read the manuscript and record the panel's concerns with the evidence that grounds each one, keep the author's reply and the re-review's finding in their separate columns, run the devil's advocate with the concession threshold the tool enforces, and write the panel report and traceability matrix a response-to-reviewers letter is built from. Use when a document is ready for review, when a concern has to be answered or re-reviewed, or when an attack or a concession is being recorded.

日本語の概要は準備中です。原文の説明を表示しています。

Get literature into a research run when the plugin fetches nothing — fetch the source yourself with web_fetch / web_search or take a file the person already has, READ it with the pdf_* tools or ocr, then ingest record and text together with rs_cite, bind locators, and cite with [@key]. Use when a run needs sources, when a library export has to come in, when a citation key is unknown, or when a claim cannot be checked against a source.

日本語の概要は準備中です。原文の説明を表示しています。

Write the document of a research run — plan the question and the outline with rs_plan, write prose and declare its claims together with rs_write, choose the claim strength the evidence actually holds, follow the section structure the run's kind maps to, read the draft back, and build a watermarked draft before the gated clean build. Use when a run's document has to be written, a section drafted, a claim bound to a source, or a build attempted.

日本語の概要は準備中です。原文の説明を表示しています。

Work the verification ladder of a research run with rs_verify — read the ladder report before claiming anything is checked, run the two file rungs (r1-record, r2-locate) that need no reader, record the r3-support verdicts and strength verdicts that only a reader can make, tell a miss from an inconclusive, and know what a clean build will still refuse. Use when a document is written and about to be called checked, when a claim's quote does not match its source, or when a gate or build answers with an integrity refusal.

日本語の概要は準備中です。原文の説明を表示しています。

Run a research project as a folder on disk — open the run root first, record the user's own instruction verbatim, open the two frame gates and stop for the human to answer them, and keep the stage the ledger says it is. Use when the user asks to start, resume or check a research run, a paper, a review, a brief, a report, a literature review or a protocol.

日本語の概要は準備中です。原文の説明を表示しています。

Hand a research run over as a file — read `rs_open action=capabilities` for the formats this build writes, choose between `md`, `docx`, a self-contained `html`, the `ris`/`bib`/`enw` library exports and `tex`, pick `draft=watermark` while working or `draft=clean` to hand it over, and read `build/build.json` for what was built from which bytes. Use when a document is finished enough to leave the run, when a citation style or an export has to be chosen, or when a build refuses.

日本語の概要は準備中です。原文の説明を表示しています。

Choose the design and the numbers a research run can honestly claim — write the structured METHOD RECORD (databases, date of access, search string, criteria, screening counts) that r0 validates, pick the claim strength a design can actually carry, record a statistic as data rather than prose, route to the reporting guideline the design owes, and decide what to preregister. Use when a run's question, design, search or statistics have to be settled before the writing, or when a claim needs a strength or a number attached to it.

日本語の概要は準備中です。原文の説明を表示しています。

Record the statements a journal requires and a reader checks — authors with their CRediT contributions, ethics approval that names the body and the reference number, how consent was taken, funding with grant numbers, conflicts of interest, data availability with an address or a reason, and the use of generative AI — as a validated record that the submission folder prints and the manuscript never carries. Use when a run is heading for submission, when an author asks who should be listed, when consent, approval or data sharing has to be stated, or when the venue's AI policy comes up.

日本語の概要は準備中です。原文の説明を表示しています。

ファイル編集・コマンド実行・調査・複数ツール呼び出しを伴う作業の最終応答時に、指定の日本語Markdownテンプレ（タイトル/解釈の要約/対応内容/影響）で対応内容を報告する。複数ターンに分かれた作業の最終完了時、複数ファイル編集を含む実装完了時、調査・分析タスクの結果報告時、新規ファイル作成を伴う作業の完了時に必ず参照する。単発の質問への即答（ツール呼び出しなし、または1〜2回のRead/Bashのみ）は対象外。

Create concise checklist cheatsheets from official tool docs. Use for docs URLs, setup guides, or updating existing cheatsheets. Don't use for long tutorials or API references.

日本語の概要は準備中です。原文の説明を表示しています。

Product-discovery coach for Fishbowl engineers — inspired by Marty Cagan's work (never impersonates him). Stage-routes between opportunity brief, research, PRD, ticket drafting, and outcome review. Triggers on "product coach", "help me with product", "I need to write a PRD", "I want to do discovery", "opportunity assessment", "who is this for", "why are we building this", or when an engineer is starting, resuming, or post-mortem-ing product-adjacent work. Invoke with a short description of what you want to do, or invoke bare to be surveyed and routed.

日本語の概要は準備中です。原文の説明を表示しています。

Conduct a Marty-Cagan-style opportunity assessment interview and produce a ~2-page Opportunity Brief in Confluence. Covers business objective, customer, problem, success metric, current alternatives, assumptions/risks, and what we don't know yet. Triggers on "opportunity brief", "opportunity assessment", "discovery brief", "who is this for", "why are we building this", "validate this idea", "product discovery", or any request to frame a feature before implementation. One question at a time. Records accepted research gaps as structured Confluence Decision pages with bidirectional links.

日本語の概要は準備中です。原文の説明を表示しています。

Save the latest learning as a numbered markdown file under ~/.claude/learnings and update the learnings index with title and tags. Use when the user says "save", asks to record a learning, or wants the current insight stored for later.

日本語の概要は準備中です。原文の説明を表示しています。

Load when a task asks to research, verify, compare, or look up framework/package behavior, release notes, standards, RFCs, CVEs, or unfamiliar APIs; use repository evidence first, then official docs, and not for codebase navigation alone.

日本語の概要は準備中です。原文の説明を表示しています。

Search, summarize, and synthesize economics literature. find research gaps, position your contribution.

日本語の概要は準備中です。原文の説明を表示しています。

Econometrics skill for Difference-in-Differences (DID) analysis. Activates when the user asks about: "difference in differences", "DID", "DiD", "diff-in-diff", "parallel trends", "treatment group", "control group", "pre-treatment", "post-treatment", "policy evaluation", "natural experiment", "staggered DID", "event study regression", "two-way fixed effects DID", "callaway santanna", "sun and abraham", "双重差分", "倍差法", "平行趋势", "处理组", "对照组", "政策评估", "事件研究", "交错DID", "渐进处理"

日本語の概要は準備中です。原文の説明を表示しています。

Draft economics papers with proper structure and academic style

日本語の概要は準備中です。原文の説明を表示しています。

Guidance on writing high-quality requirements: the requirement quality characteristics and the EARS (Easy Approach to Requirements Syntax) patterns — ubiquitous, event-driven, state-driven, optional-feature, unwanted-behaviour — for unambiguous, singular, verifiable requirements, plus defect/anti-pattern review and verification & traceability. Use when authoring or reviewing requirements. Original synthesis citing EARS (Mavin et al.) and NASA public-domain guidance; not a reproduction of ISO/IEC/IEEE 29148 or the EARS paper.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrator (not a knowledge pack): routes a free-text systems-engineering question to the right catalogue pack(s), reads them with you, and answers with pack and chapter citations. Runs only on explicit `/se <question>`; carries no source content. Use when you do not know which `/pack` to ask.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from OMB Circular A-94 (revised 2023-11-09) on guidelines and discount rates for benefit-cost and cost-effectiveness analysis of federal programs. Use for BCA principles, benefit/cost measurement, discount-rate policy, uncertainty/sensitivity, distributional incidence, and decision reporting. Rescoped at build to A-94 only (Army CBA Guide unreachable). Does not replace A-11 budget preparation detail, agency-specific statutory BCA rules, or Army CEAC process templates.

日本語の概要は準備中です。原文の説明を表示しています。

杰弗里·杨（Jeffrey Young）图式疗法：图式、模式、内在儿童概念与应对风格——心理教育呈献。

日本語の概要は準備中です。原文の説明を表示しています。

Schema Therapy according to Jeffrey Young: Schemas, modes, inner child concept, and coping styles — psychoeducationally presented.

日本語の概要は準備中です。原文の説明を表示しています。