Design validation and maintained regression protection before test authoring. Use for TDD increments, acceptance or regression evidence, test boundary/oracle decisions, and multi-factor interaction coverage.
日本語の概要は準備中です。原文の説明を表示しています。
4,809 件 ・ 関連度順
概要と使いどころ
Design validation and maintained regression protection before test authoring. Use for TDD increments, acceptance or regression evidence, test boundary/oracle decisions, and multi-factor interaction coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Review existing tests against the software and contracts they actually exercise. Use to assess whether a test has justified unique protection, detects consequential faults, tolerates valid refactors, earns its lifecycle cost, or deserves strengthening, replacement, consolidation, or removal consideration. Reviews are read-only and evidence-backed, including TDD and regression tests.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrator context window discipline enforcement. Prevents the orchestrator from reading source files it will not edit, running diagnostic commands that waste context, and rationalizing delegation bypasses. Use when setting up orchestrator guardrails, reviewing delegation discipline, or diagnosing context window waste in multi-agent workflows. Activates PreToolUse hooks that surface decision points before source file reads and diagnostic command execution.
日本語の概要は準備中です。原文の説明を表示しています。
Use when orchestration or planning agents are producing task plans, task prompts, or TASK.md instructions that must be unambiguous, verifiable, and resistant to hallucination. Applies CLEAR (Concise, Logical, Explicit, Adaptive, Reflective) to structure and write agent task prompts, then adds CoVe (Chain of Verification) checks where accuracy risk is meaningful. Activates on draft task prompts, swarm plans, migration tasks, and multi-step plans requiring independently executable steps.
日本語の概要は準備中です。原文の説明を表示しています。
Look up prior Claude Code sessions when context is lost or forgotten. Use when asked what was done before, what happened in the last session, or any request to recall past conversation history, prior decisions, experiments, or outcomes. Indexes and searches raw JSONL transcripts from ~/.claude/projects/ via DuckDB. Returns verbatim user messages, summarizes AI actions and sub-agent outcomes, detects tool errors and user frustration signals, and reports tool usage statistics. Summaries cached at ~/.claude/kaizen/session-summaries/.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a repository has a valuable agentic workflow, prompt chain, playbook, command, or runbook that should become a portable ChatGPT/Codex Skill without losing its real decision logic.
日本語の概要は準備中です。原文の説明を表示しています。
Organizes an author’s response to peer review. Extracts every referee and editor point, tags severity and type, orders the revision by dependency, flags defensible pushbacks as questions, and builds a numbered comment → response → location letter whose substantive answers the author writes. Use when the user has referee reports, a revise-and-resubmit decision, or an editor’s letter and wants to plan the revision, draft the response letter, or check that every point was addressed. The reviewer-side twin is journal-review.
日本語の概要は準備中です。原文の説明を表示しています。
Designs publication tables for social-science manuscripts. Covers whether a result belongs in a table at all, column order, row grouping and panels, decimal precision, standard-error and confidence-interval conventions, self-contained titles and notes, and code-generated output. Use when building or revising a regression, balance, descriptive, or robustness table, or when working with modelsummary, stargazer, gt, esttab, or booktabs. Finished tables go to figure-table-audit for end-stage QA.
日本語の概要は準備中です。原文の説明を表示しています。
Designs and diagnoses list experiments (the item count technique), covering whether indirect measurement is warranted, control-list construction against floor and ceiling effects, design variants, estimators and assumption tests in the list package, and power planning for the precision penalty. Use when the user measures a sensitive attitude or behavior and asks about list experiments, item count, unmatched count, or veiled questioning, or has an implausible prevalence estimate. Deciding whether sensitivity bias exists at all goes to survey-design.
日本語の概要は準備中です。原文の説明を表示しています。
Runs a deliberative two-model committee of GPT-6 Astra and Claude Opus under a selectable chair, Fable by default, with `/model-committee-astra`, `/model-committee-opus`, and `/model-committee-sol` selecting the others. Use when a consequential decision has several defensible options and two model families should propose, critique, revise, and cross-rank them against a predeclared rubric before converging, as in research design, interpretation, architecture, manuscript strategy, or evaluation design. Not for factual lookups, independent-coder reliability, brainstorming, routine implementation, or final professional judgment.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a referee report for a journal editor. Produces a recommendation, claim-and-design summary, three to six decision-driving concerns, additional concerns, and a revision plan through five parallel adversarial finders, Breaker, Butcher, Shredder, Void, Situator, a Blue Team error filter, Chief Reviewer synthesis, Tone Guard legal pass, and optional confidential editor note. Use when the user has been asked to referee a manuscript. Self-audits go to paper-review-lite or presubmit, and author responses go to referee-response.
日本語の概要は準備中です。原文の説明を表示しています。
Writes or reviews a pre-analysis plan before data collection — registry choice (OSF, AEA RCT Registry, AsPredicted, registered reports), PAP structure, models and decision rules locked in advance, analysis code run on simulated data, contingencies for attrition, failed manipulations, and exclusions, deviation records, and timeline. Operationalizes the pre-data-collection side of DA-RT. Use when the user asks to draft or audit a pre-registration or PAP, choose a registry, decide what to lock versus leave exploratory, or handle a later deviation. Hypotheses and estimands come from hypothesis-building, post-hoc reporting from methods-reporting.
日本語の概要は準備中です。原文の説明を表示しています。
Design and format publication-quality tables. Use for column order, row grouping, notes, statistical precision, accessibility, and reproducibility.
日本語の概要は準備中です。原文の説明を表示しています。
Run one consequential, contestable decision through a deliberative committee of GPT-6 Astra and Claude Opus, chaired by fable (default), astra, opus, or sol. Not for factual lookups, brainstorming, routine implementation, independent-coder reliability, or final professional judgment. Use when several options are defensible and the two model families should propose, critique, revise, and cross-rank under a predeclared rubric.
日本語の概要は準備中です。原文の説明を表示しています。
Consults Fable as an independent, read-only reviewer at an effort the caller matches to the question. The calling session (usually Opus, or Haiku) holds the task and escalates one decision point. Use before committing to an interpretation or a substantial piece of writing or analysis, when stuck or not converging, when changing approach, or as a final check on a finished task. Fallback for when the native advisor tool is unavailable. Not for a session already running Fable.
日本語の概要は準備中です。原文の説明を表示しています。
Writes or reviews a pre-analysis plan before data collection: registry choice (OSF, AEA, AsPredicted, registered reports), locked models and decision rules, code run on simulated data, contingencies, and deviation records. Use when drafting or auditing a pre-registration or PAP, choosing a registry, or handling a deviation.
日本語の概要は準備中です。原文の説明を表示しています。
Turns dictated captures in a deliverable's inbox/ into a proposed planning-wiki diff, classifying and tracing each statement; decisions need the author's assent. Use to intake notes or process the inbox.
日本語の概要は準備中です。原文の説明を表示しています。
An AI analyst for buying B2B software. Investigates what vendors claim, checks the evidence, surfaces contradictions and unanswered questions, and produces a shareable Decision Brief with the questions to ask before you buy. Quick Eval by default; Deep Eval on request. Use when asked to evaluate, compare, vet, or research B2B software vendors.
日本語の概要は準備中です。原文の説明を表示しています。
Create a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work.
日本語の概要は準備中です。原文の説明を表示しています。
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
日本語の概要は準備中です。原文の説明を表示しています。
Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code. Use when the user wants to clarify requirements, stress-test an idea, compare approaches, or plan before coding.
日本語の概要は準備中です。原文の説明を表示しています。
High-precision semantic search and content retrieval via Exa API. Use when: (1) Deep research requiring semantic understanding, (2) Code documentation and examples lookup, (3) Company/professional research, (4) AI-powered comprehensive research tasks, (5) URL content extraction with structured output. Triggers: "research", "find papers", "code examples", "company info", "LinkedIn profiles", "deep analysis". Differentiator: Exa excels at semantic/neural search while grok-search is better for real-time news and general web content.
日本語の概要は準備中です。原文の説明を表示しています。
Apply systematic problem-solving techniques for marketing challenges including campaign complexity (simplification cascades), creative blocks (collision-zone thinking), recurring campaign patterns (meta-pattern recognition), assumption constraints (inversion exercise), audience scale uncertainty (scale game), and dispatch when stuck. Techniques derived from proven problem-solving frameworks adapted for marketing execution.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
日本語の概要は準備中です。原文の説明を表示しています。