「judgment」の検索結果

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.

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

Use when the user wants to create a new CLAUDE.md from scratch for a repository, bootstrap project memory for a new repo, set up a repo for Claude Code for the first time, or completely rewrite an existing CLAUDE.md deemed unsalvageable. Produces a lean, high-signal file under 80 lines (120 hard cap) by scanning the repo for mechanical content (stack, commands, structure) and interviewing the user for judgment content (WHY, gotchas, out-of-scope, approval gates, testing philosophy, external docs like Confluence pages). NOT for auditing or incrementally improving an existing CLAUDE.md — that is the claude-md-improver skill's role.

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

Read-only runbook for how the VNX fabric actually works — state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this one is pure reference.

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

Use when Codex must make a high-quality judgment on any complex problem, not only technical problems. Trigger when a question has high complexity, uncertainty, cost of being wrong, long-term impact, value tradeoffs, possible structural causes, or when the user asks for 全面思考, 深度理解, 系统性分析, 帮我想清楚, 从根上看, 这件事到底怎么看, 方法论, 复杂问题拆解, 系统方案, 架构判断, 策略判断, or 根因分析. Also trigger for project and engineering high-risk scenarios such as multi-module, multi-environment, multi-data-source, multi-state, financial truth, live trading, ledger, revenue, customer assets, order governance, broker interfaces, online availability, major solution selection, and system closure.

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

当用户需要分析企业/组织/产品的竞争格局、评估"做大"是否真的更好、判断某公司的护城河来源是否可持续时调用。典型触发信号：涉及"规模经济""市场占有率""大企业的困境""先发优势""网络效应""赢家通吃"等话题。不适用于纯财务分析(用 value-assessment)或纯心理偏差检查(用 misjudgment-checklist)。

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

当用户面临重要决策、评估他人行为、诊断群体现象或反思自身判断偏差时激活此 skill。典型触发信号：用户在做重大选择前需要排查认知陷阱；用户发现自己或他人做出了"不合逻辑"的行为需要解释；用户试图理解一个群体为何集体犯错。不适用于纯技术性决策（如数学计算、代码调试）或情绪安抚场景。

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

当用户因失去(或即将失去)某样东西而做出不成比例的激烈反应,或在损失后急于"扳平"、无法止损时调用。典型触发信号:沉没成本陷阱、赌徒式加注、拍卖中的非理性竞价、无法放弃已投入大量资源的失败项目。不适用于一般的投资估值(用 value-assessment)或从众行为(用 misjudgment-checklist)。

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

当用户需要评估某项投资、收购标的、商业机会或重大资源投入是否"值得"时调用。典型触发信号:涉及"内在价值""安全边际""护城河""定价权""买还是不买"等决策。不适用于纯心理学偏差分析(用 misjudgment-checklist)或规模效应判断(用 scale-advantage-analysis)。

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

Construction document review with PE judgment — RFI research, submittal analysis, coordination checking, scope gap detection. Use when reviewing drawings, specs, submittals, or RFIs. Triggers: 'review', 'coordination', 'what's missing'.

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

Executes a QA specification (specs/qa/QA-<N>-<slug>.md) written by /plan-qa: drives every step with the plan's drivers, verifies each Expected line mechanically ([assert]) or by evidence-backed judgment against the plan's written criterion ([judge]), pauses at named operator handoffs, and writes the results artifact QA-RESULTS-<N>-<slug>.md. Use only when the user asks to run or execute a QA plan — never trigger automatically.

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

Choose, configure, launch, and collect bounded subagents for research and engineering decisions. Root agents and delegation-capable subagents should read this before delegating: every task requires an explicit model tier, and high-leverage work such as research ideation, round planning, plateau pivots, large research reviews, hard optimization, disputed evidence, and expensive experiment portfolios requires frontier judgment.

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

Rewrite a rule so anyone applies it the same way. Use when a stated rule or claim takes the reader's judgment to apply.

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

Apply the Minimum Sufficient Language (MSL) principle through the MSL Kernel to write anything a reader must act on. Bind the reader and what they already know, partition facts from the machinery that produced them, emit each admitted fact as an action, a verification, a judgment, or a state, and stop when every claim is checkable and the reader can act. Use for status updates, work-in-progress reports to your own user, closeout and convergence comments, tickets, pull request and review write-ups, incident and postmortem notes, emails, memos, and any draft for readers outside the work. Also use when the user says MSL, Minimum Sufficient Language, write this for stakeholders, drop the jargon, make this readable, or asks for a paste-ready draft.

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

Use when surfacing the assumptions underlying an analytical judgment, the user asks "what are we assuming?" / "are these assumptions still valid?", or before publishing a high-impact assessment. Standard SAT applied during major assessments.

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

Use when assigning a confidence level to an analytical judgment, the user asks "how confident are we?" / "what is the confidence on X?", or the orchestrator's tradecraft pipeline calls for a confidence level before publishing. Provides three named levels (High, Moderate, Low) with 0-100 score ranges aligned to STIX, and the rule that confidence cannot exceed what the weakest load-bearing claim supports.

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

Use this skill whenever the user asks for an HTML-first visual design deliverable or design judgment: interactive prototype, slide deck, motion demo, infographic, dashboard, landing page, whitepaper, changelog, business card, social cover, brand system, design critique, multi-variant exploration, or export to MP4, GIF, PPTX, PDF, or SVG. It is optimized to make AI agents do the routing, template selection, verification, and export prep so humans spend less time prompt-engineering. Do not use for production web apps, SEO sites, backend systems, or pure copy edits.

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

Evaluate and act on code-review feedback with technical judgment. Use before applying external suggestions, especially when feedback is ambiguous, broad, or may conflict with repository constraints, and carry confirmed corrections to relevant consumers without widening scope.

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

Organize month-end or quarter-end close blockers, reconciliations, owners, and evidence gaps into a routine control pack. Use when the work is finance close coordination and issue tracking. Do not use for accounting judgment, policy interpretation, or final technical accounting conclusions.

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

Package interview loops, schedules, feedback follow-ups, and candidate next steps for recruiting operations. Use when the work is routine hiring coordination and recap packaging. Do not use for final hiring decisions, compensation judgment, or sensitive people-policy advice.

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

Close out a review/meta branch that lands an evidence-ingest / curation batch: create the named nodes, ingest verified evidence, appraise Trust Magnitude, calibrate stars, wire suites, correct upstream naming, stage ONLY the intended artifacts (dropping CRLF churn and blocking leaks), validate, and open the PR. Use when a curation/ingest batch is verified and ready to land, or when the user says "close the review/meta branch", "land the ingest batch", "wrap up the intake PR", "/gaia-review-meta-close". Wraps the deterministic hygiene in scripts/review_meta_close.py and gates the judgment calls (calibration, Origin, suite promotion, naming, merge) behind explicit human checkpoints.

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

Ask Daniel a blocking decision as options with a recommendation and honest pros/cons, rather than prose. Use whenever work is blocked on a judgment call, a product decision, an approval, or a choice between approaches — instead of writing "let me know which you prefer" at the end of a message.

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

Apply source-aware mechanical-engineering judgment to research, analysis, coding, writing, teaching, research identity, and release work. Use for thermal-fluid systems, heat transfer, fluid mechanics, thermodynamics, HVAC, energy systems, turbomachinery, piping, multiphase flow, experiments, correlations, CFD, reduced-order models, AI/ML, uncertainty, engineering datasets, literature reviews, citations, manuscripts, reviewer revisions, Overleaf packages, figures, proposals, research software, reproducibility, public releases, engineering teaching materials, or a research-project logo and visual identity.

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

Iterative manuscript improvement workflow where a reviewer agent critiques, an author agent revises, a verifier checks the revision, and the loop repeats until acceptance or a human-pause condition is reached. Use for virtual peer review, reviewer-author revision loops, rebuttal preparation, resubmission polishing, journal paper improvement, response-to-reviewers drafting, and deciding when additional data, experiments, theory, modeling, or author judgment is required before further revision.

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

Provide constructive, evidence-based research mentoring feedback on student manuscripts, proposals, analyses, code, figures, and presentations. Use for advisor-style review that teaches the next improvement without impersonating an advisor or making unsupported scientific judgments.

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