「iter」の検索結果

Autonomously improve a real artifact (code, training recipe, agent harness, data pipeline, prompt) against an objective and an evaluator, using Hypothesis Tree Refinement (HTR) from the Arbor paper. Use this whenever someone wants to iteratively optimize something over many experiments without overfitting — e.g. "get my model's eval score up", "improve this agent/harness", "tune this pipeline", "beat the baseline on this benchmark", "run a search over approaches and keep the best", "do an MLE-bench / Kaggle-style optimization", or any long-horizon "make this artifact better and don't just memorize the dev set" task. Trigger it even when the user doesn't say "Arbor" or "hypothesis tree" but describes repeated experiment-and-evaluate loops, branching exploration of competing ideas, or worries about a dev/test gap. Runs Claude itself as the coordinator with subagent executors in isolated git worktrees; for the standalone `arbor` CLI tool see references/arbor-upstream.md.

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

This skill determines whether inpatient diabetic patients meet high-risk criteria for CGM initiation using Table 3 factors such as age ≥65 years, BMI ≤27 kg/m², type 1 diabetes, insulin regimen, and specific clinical conditions. It is triggered by clinician questions like "Should I assess this inpatient for CGM initiation based on hypoglycemia risk?" or "Is this patient a candidate for inpatient CGM?"

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

Determines if patient meets criteria for genital gender-affirming surgery affecting fertility. Triggers include patient on hormones, considering surgery.

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

Determines whether an adult patient meets eligibility criteria for initiating gender-affirming hormone therapy. Triggered when an adult patient requests gender-affirming hormones or presents for evaluation of hormone therapy eligibility.

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

Determines if an adolescent meets criteria for initiating sex hormone treatment for gender dysphoria/gender incongruence. Triggered when an adolescent requests sex hormones or presents for gender-affirming hormone therapy evaluation.

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

Determines if adolescent meets criteria for GnRH agonist treatment to suppress pubertal development. Triggers include adolescent requesting to suppress puberty, adolescent with gender dysphoria seeking pubertal blockade, or clinician noting Tanner G2/B2 with request for hormone suppression.

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

If CGM fails or is removed, revert the insulin pump to manual mode provided basic criteria for pump use in hospital are still met. Trigger phrase: "CGM failed, should we switch pump to manual mode?

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

Suggests initiating inpatient CGM for select diabetic patients at high risk for hypoglycemia based on Table 3 criteria. Triggers include "Should I initiate CGM for this hospitalized diabetic patient at high risk for hypoglycemia?" or "Is inpatient CGM warranted for this patient?"

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

Determines if patient meets ICD-10 criteria for transsexualism. Triggered when a clinician uses ICD-10 for diagnostic purposes in gender identity assessment.

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

This skill provides criteria to distinguish unilateral from bilateral primary aldosteronism using adrenal venous sampling results, including lateralization index, contralateral ratio, and clinical factors. It is triggered after AVS when clinicians analyze results and ask 'Is this unilateral or bilateral PA?' or need to guide treatment decisions.

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

Identifies patients with a positive aldosterone-to-renin ratio screening who may proceed directly to subtype testing without confirmatory testing based on specific clinical criteria. Triggers include spontaneous hypokalemia, baseline plasma aldosterone concentration >100 pg/mL (CLEIA), renin suppression, or a clinician questioning the need for a confirmatory test after a positive screen.

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

Determines when adrenal venous sampling may be skipped in primary aldosteronism. Applies to patients <35 years with spontaneous hypokalemia, marked aldosterone excess, and unilateral adrenal lesions suggestive of cortical adenoma on CT.

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

Standard operating procedure for producing a documentation page end to end — gather source material, classify, draft against the measured corpus profile, then run the reader-level and humanizer passes and both gates. Use for any page on a documentation surface, or when rewriting a page that reads as machine-written. Orchestrates technical-writing, reader-level and humanizer in a fixed order.

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

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Preflight a spec draft without saving. Runs the same checks as the write-boundary hooks — PlantUML syntax, required diagram presence, AC-to-sequence traceability, Design calls quality floor, and System delta row resolution — and prints a compact pass/fail table. Use while iterating so the hooks don't bite on save.

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

Propose the next dependency-ready sprint from the ALREADY-DECOMPOSED roadmap — standup's active sibling. Reads docs/roadmap-execution-plan.md + the memory backlog, computes per-task readiness from the roadmap's machine-readable status, orders with roadmap-planner's graph engine, and emits a proposed task-set (sprint-plan manifest shape) with per-feature done-criteria, excluding unready tasks and naming their unmet prerequisite. PROPOSES ONLY — the human confirms/edits before /triage routes it (typically to the `power` track). Distinct from `sprint-plan`, which decomposes a fresh vision.

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

Write the production code that makes a pre-decided set of failing tests pass, within an explicit write_set, following an explicit behavior contract. Used by `/tdd` Step 3 and by `/swarm-dispatch` workers. The caller has already decided architecture, naming, file layout, and abstraction boundaries — this skill executes that recipe with code-structure discipline and a 5-iteration RALPH loop. No scope expansion, no design decisions, no test edits.

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

Workflow Phase 10 — orchestrator for documentation work. Surveys the diff, routes any page on a documentation surface through `technical-writer`, standalone technical reference through the `documentation` skill, tutorials through `technical-tutorials`, and all other prose body work (inline docs, README updates, user-facing copy) through the `prose` skill (which mandates `humanizer` and conditionally `copywriting`). Verifies completeness and marks phase done.

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

Draft a Workflow Phase 1 intake document capturing a new request — the problem, the desired outcome, constraints, and testable acceptance criteria. Use when a user brings a new feature, change, or investigation that doesn't yet have a spec. The output lives at `docs/intake/<slug>.md` and feeds `/scout`, `/research`, and `/spec` downstream.

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

Power batch-sprint helper — hosts the two behaviours that distinguish the `power` workflow track from spec-entry. (1) Per-ticket iteration: security runs once PER TICKET over workflow.json.tickets[] while the mechanical phases run once for the batch. (2) Commit split: at the commit phase, group the batch's working tree into ordered Conventional Commits via commit-split.mjs, closure last. Invoked within a `power`-track workflow; not a standalone feature. Opt-in via velocity.power_mode.enabled; requires git.

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

Oracle-bound spec-review check that every structured Rollout prerequisite binds to an enforcement-type acceptance criterion. A prerequisite whose `enforced-by` is missing, dangling, or points at a non-enforcement AC is a BLOCKER (hard-blocks implementation entry via the checker fan-out verdict); a prerequisite left in free prose is ADVISORY. Read-only. Runs in the spec-review fan-out before implementation.

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

Decompose an MVP vision into a sprint manifest — a prioritized feature list where every feature carries explicit done-criteria (a done-record reference, named edge tests, and a wiring test). Produces the sprint manifest that `sprint-oracle` checks for completeness. Use when planning a sprint of parallel work (Slice A of the sprint-mode epic). Not a workflow phase; the manifest it writes is the completeness contract a sprint is held to.

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

Use for tradeoff analysis, or when the user must pick between concrete options: "A or B?", "which library should we use?", "build vs buy", "compare these approaches". Scores options on weighted criteria, tests sensitivity and reversibility. Skip for open ideation or single-option reviews.

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

Iterative Python via live Jupyter kernel (hamelnb).

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