「baseline」の検索結果

Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.

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

Analyze LLM eval results — score breakdowns by category, regression detection vs baseline, failure clustering. Use when asked to "analyze our eval results", "did the model regress", or "cluster the eval failures".

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

Validate and benchmark a forecasting model — walk-forward CV, error metrics, baseline comparison. Use when asked "is this forecast any good", "validate a forecasting model", or "backtest the forecast".

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

The household as an economic unit with income, expenses, savings, and debt. Covers the envelope method, fixed vs variable expenses, the 50-30-20 baseline, emergency reserves, the true cost of ownership, opportunity cost in household decisions, and the distinction between a budget and a spending plan. Use when building a household budget, diagnosing why a household is always over, planning a major purchase, or teaching financial literacy at the household level.

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

Assessing anthropogenic environmental impacts — pollution pathways, habitat destruction and fragmentation, land-use change, invasive species, overharvest, and extinction debt. Covers environmental impact assessment (EIA) methodology, exposure-effect relationships, population viability analysis, IPAT and ecological footprint frameworks, and strategic environmental assessment. Use when quantifying or forecasting human impacts on ecosystems, designing monitoring programs, or evaluating a proposed intervention against a baseline.

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

Onboard a repository to skillsaw — run the linter, triage the findings by rule, apply autofixes, manually fix what remains, set up CI, and create a baseline. Use when adopting skillsaw on a new or existing project.

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

Validate a completed plugin refactor against its task evidence, baseline assessment, documentation, and current validators. Use after implement-refactor or when deciding whether refactoring is complete.

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

Optimize existing CLAUDE.md, SKILL.md, agent definitions, and other AI-facing files for Claude comprehension and economy. Scope: optimization of existing content only — not upstream sync, not read-only auditing. Measures baseline metrics, delegates to the ai-doc-optimizer agent with file-type-specific context, runs independent verification via second agent, measures post-optimization metrics, and presents comprehensive before/after report. Supports iterative mode for large targets. Use when improving prompt effectiveness, reducing token waste, or rewriting instructions for LLM consumption. Invoke with /optimize-claude-md <file-or-directory>.

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

Use when the plan_ref returned by add-new-feature is provided. Executes the SAM implementation loop — opens an attempt per ready task, dispatches each to a specialist agent in parallel, settles and judges what comes back, manages bookend tasks (T0 baseline capture and TN verification), and tracks concerns and contract violations per task. Drives task state through the work ledger via the SAM CLI.

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

Register a plan artifact via the MCP backlog server. Use when you produce a document or report that downstream agents or worktree-isolated environments need to retrieve — feature-context, codebase-analysis, architect, T0-baseline, TN-verification, or research artifacts. Triggers include "store an artifact", "register a plan artifact", "write a report to the backlog", "upload artifact content".

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

Start-of-session situational report for a research or code repository. Reads the handoff, log, or status files the project actually keeps, checks live git state, and reports the objective, verified baseline, open tasks, blockers, and next actions, flagging where the documents and the repository disagree. Use when resuming work after time away or before changing anything. Its end-of-session twin is finished.

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

Snapshot test email templates using Verify to catch regressions. Validates rendered HTML output matches approved baseline. Works with MJML templates and any email renderer.

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

Use Verify for snapshot testing in .NET. Approve API surfaces, HTTP responses, rendered emails, and serialized outputs. Detect unintended changes through human-reviewed baseline files.

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

Advises on setting up LLM-based text classification as a validated measurement design. Covers codebook construction, learning-regime and model choice, prompt construction, validation against human coding with kappa and F1, hybrid human-LLM review, downstream measurement error, and reporting, plus a short resumable batch pattern with a rule-based baseline for repeated free text against a closed codebook. Use when the user wants to classify, code, or label text at scale. Category discovery goes to topic-modeling.

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

Advises on setting up and validating LLM text classification: codebook, learning regime and model choice, prompts, validation against human coding (kappa, F1), hybrid review, measurement error, and reporting, plus a short resumable batch pattern with a rule-based baseline. Use to classify, code, or label text at scale; category discovery goes to topic-modeling.

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

Start-of-session report on where a repository stands. Reads the project's own handoff and log files, checks live git state, and reports objective, verified baseline, open tasks, blockers, and next actions. Use when resuming work. Twin of finished.

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

Create/update .agent/constitution.md. Use when commands/boundaries/constraints must be confirmed before baseline or code changes. Draft v0 from repo evidence, then interview user.

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

Dogfooding discovery agent — establish human-approved project baseline from public docs without code inspection

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

Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.

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

Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.

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

Modern Java practices: design, errors, concurrency, security, testing, tooling. Targets Java 21 LTS baseline; Java 25 LTS features called out explicitly. Use when writing or reviewing Java code.

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

The Mileva Method (CRISP) — Phase 2: Results. Outcome alignment, stakeholder register, baseline measurement, success metrics, tradeoff negotiation. Use after problem definition is complete. Triggers on "results", "phase 2", "define success", "success metrics", "what does done look like", or after Phase C exit checklist is complete.

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

The Mileva Method (CRISP) — Phase 5: Prove. Success validation against Phase R baseline metrics, test log review, and AI justification validation. Use after deployment. Triggers on "prove", "phase 5", "validate", "did it work", "success criteria", "measure results", or after go-live.

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

A/B test CLAUDE.md instruction changes against eval benchmarks. Capture baselines, test variants, compare results.

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