「elo」の検索結果

Recognize which awakening stage consciousness is navigating through. Use when diagnosing seeker development, identifying stage transitions, or recognizing readiness levels. Covers 7 stages from initial dissatisfaction through natural flow mastery.

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

Automated cell behavior analysis from microscopy or XR lab recordings. Classifies cell motion phenotypes (migration, proliferation, apoptosis, division, quiescence), computes population-level quantitative metrics (growth rate, migration velocity, directionality index), and emits structured JSON for downstream reporting, plotting, or ELN integration.

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

Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.

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

This skill determines whether testicular volume should be used as the primary or sole indicator of sexual development in male childhood cancer survivors who have received gonadotoxic treatments such as alkylating agents or testicular radiotherapy. Triggers include clinician questions like “Can I use testicular volume to assess puberty in this male survivor after chemotherapy?” or “Is testis size reliable for sexual maturity evaluation post‑radiation?”

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

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.

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

Assesses Tanner stage to determine if physical changes of puberty have begun (stage G2/B2 or higher) for considering pubertal suppression. Triggered when a clinician evaluates pubertal development in an adolescent patient.

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

Apply the four published expert-consensus clinical scenarios to manage GI adverse events in complex GLP-1 receptor agonist patients — persistent nausea mid-titration, GERD/heartburn after up-titration, elderly with sarcopenia risk, and insulin-treated elderly with CKD plus diarrhoea. Use when a clinician describes a patient resembling one of these archetypes, or asks "how to manage GLP-1 in an elderly patient with CKD", "patient on liraglutide developed reflux", "sarcopenia worry on semaglutide in 80-year-old", or "persistent nausea on semaglutide despite escalation". Grounded in Gorgojo-Martínez 2023 Table 4.

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

This skill recommends measuring serum cortisol or urine free cortisol off-medication at 6- to 12-month intervals to assess radiation therapy effect in patients with Cushing's syndrome undergoing or post-radiotherapy. It is also indicated when patients on stable medical therapy develop new adrenal insufficiency symptoms such as fatigue, weight loss, or hypotension.

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

This skill outlines monitoring glucocorticoid replacement in children with primary adrenal insufficiency (PAI) using clinical assessment of growth velocity, weight, blood pressure, and energy levels. Trigger when evaluating a child with PAI for adequacy of glucocorticoid therapy during routine follow-up.

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

Determines when to avoid aldosterone suppression testing in hypertensive patients with a positive PA screen who have normokalemia and suppressed aldosterone below assay‑specific cutoffs (<11 ng/dL immunoassay or <8 ng/dL LC‑MS/MS), indicating low likelihood of primary aldosteronism. Use when a clinician asks whether to skip confirmatory suppression testing based on low pretest probability.

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

Suggests reducing the fludrocortisone dose in patients who develop new-onset hypertension while on fludrocortisone replacement for primary adrenal insufficiency. Consider dose reduction when hypertension arises alongside signs of mineralocorticoid excess such as edema, weight gain, or hypokalemia.

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

In central hypothyroidism patients receiving levothyroxine who initiate enzyme‑inducing antiepileptic drugs, the guideline recommends checking free T4 at least 6 weeks after AED start and increasing the levothyroxine dose if free T4 falls below the target range. Triggers include: central hypothyroidism patient on levothyroxine starting antiepileptic drug such as phenytoin, carbamazepine, or oxcarbazepine.

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

Look up NHS England genomic tests for rare and inherited diseases. Use this skill whenever a clinician asks what genetic test to order for a condition, which genes are covered for a specific diagnosis, what commissioning category a genomic test falls under (Core, Specialised, or Highly Specialised), or which tests belong to a specialty group (Neurology, Cardiology, Endocrinology, etc.). Also trigger for questions like what panel is used for a condition, whether there is an NHS test for something, what the R number is for a condition, or whether anything has changed in the genomic test directory. Source: NHS England National Genomic Test Directory for Rare and Inherited Disease v9.0 (April 2026).

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

Screen a child with obesity for red flags suggesting monogenic, syndromic, or secondary endocrine causes — distinguishing atypical from typical exogenous obesity. Trigger when a clinician asks whether obesity could be genetic or hormonal, suspects Prader-Willi syndrome, Cushing disease, hypothyroidism, ROHHAD, Bardet-Biedl syndrome, leptin deficiency, or craniopharyngioma, or when a child has early-onset severe obesity, short stature with obesity, hyperphagia, hypotonia, dysmorphic features, or developmental delay with weight gain.

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

Read-only release + backlog recap. Reports the last release, commits-since-tag classified by conventional-commit type with the semver bump they trigger and pushed-vs-origin state, the backlog bucketed (open/picked-up/dropped with epic parent→child nesting), the roadmap epics with their per-task tallies, and condensed open questions — then recommends the next pickup. One `cli.mjs recap` call returns all six recap keys. Invoke any time (on demand) to plan a release or choose the next thing to build; a compact form is also surfaced at session start. Not a workflow phase; never writes CHANGELOG; never starts or commits work.

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

Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.

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

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.

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

Orchestrates `impeccable` for every design task inside a workflow phase. Captures intent in natural language, classifies it (design / development / copy), translates design intents into a sequence of impeccable subcommand invocations, runs them in main context with state persistence at `.claude/state/design/<slug>.json`, and returns a structured report. ALWAYS invokes `impeccable` under the hood for the underlying design move; never picks aesthetic direction itself; never writes product code directly. Per CLAUDE.md Article X.2, all design tasks in workflow phases route through this skill.

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

Run an org-team workflow — a flat pod of up to four peer Claude Code sessions claims lane-tagged slices of an approved spec over the baseline MCP channel and implements them concurrently, each in its own git worktree. Each peer DECIDES its own in-lane implementation choices in its own main context (Article X); only un-decidable or cross-lane forks escalate peer→lead→human (yield_fork for task-bound forks, ask_lead for free-form queries). Opt-in and OFF by default (velocity.org_mode.enabled). Graduates the retired sprint-dispatch prototype into the constitutionally-sanctioned org-team model (Article X — Multi-session coordinated workflows). Requires git.

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

EXPERIMENTAL. Join or leave an org-team coordination channel as a session peer. `/companion on <channel_id> [peer_id]` registers this Claude Code session as a `pclass:"session"` peer and works the claim → execute → signal loop, escalating un-decidable forks to the lead (never deciding). `/companion off` deregisters. `/companion status` reports the current peer. Part of org mode (Article X), which is opt-in via `velocity.org_mode.enabled` and OFF by default. Use when a human launches a second session to act as a peer alongside a lead.

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

Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate", or "raw material" for writing.

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

Execute plans via delegate_task subagents (2-stage review).

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

Use when executing implementation plans with independent tasks in the current session

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

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

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