「continuation」の検索結果

Execute a Prometheus work plan in Codex with Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and Stop-hook continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.

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

Session handoff — compress current context into a structured prompt for seamless continuation in a new session. Use when: switching sessions, running low on context, or needing to hand off work.

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

Persists and restores mid-session workflow progress across context resets. Use when resuming workflows, saving state, or handling context compaction. Triggers on: handoff, save state, resume workflow.

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

Prevent session idle during background agent work via SubagentStop prompt hook auto-continuation

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

End-to-end workflow orchestrator. Walks the 11-phase pipeline, invoking each phase skill in order inside an internal loop, yielding at consent gates (/approve-direction, /approve-swarm, /grant-commit), and exiting cleanly on yield/failure/done. Decides swarm-vs-solo at Phase 6. Auto-loops /tdd on integrate failures that don't require a spec change. The harness_continuation Stop hook is a safety net that re-fires harness only when the loop exited mid-flow.

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

Expert-level complex analysis knowledge. Use when working with complex functions, holomorphic functions, Cauchy's theorem, contour integration, Laurent series, residues, conformal mappings, or analytic continuation. Also use when the user mentions 'holomorphic', 'analytic', 'Cauchy theorem', 'residue', 'contour integral', 'Laurent series', 'conformal map', 'Riemann mapping', 'Mobius transformation', 'harmonic function', 'entire function', or 'meromorphic'.

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

Considers adapting the basal insulin rate at hospital admission for patients using insulin pump therapy. Triggered by clinician questions such as "Should we adjust the basal rate upon admission for pump therapy?" or when evaluating pump continuation versus transition to scheduled subcutaneous insulin.

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

This skill determines whether a patient using a hybrid closed-loop insulin pump can continue this therapy upon hospital admission. It is triggered by questions such as "Can hybrid closed-loop pump be continued given hospital constraints?"

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

This skill confirms whether a hospital has the necessary policies and expertise to support inpatient insulin pump therapy, including informed consent, standardized order sets, and device management guidance for imaging and surgical procedures. Triggered by questions such as "Are hospital policies and expertise in place for insulin pump use?" to ensure safe continuation of pump therapy in noncritical illness.

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

This skill suggests continuing personal CGM with or without ADIP rather than discontinuation for inpatients already using it who are at high risk for hypoglycemia. Trigger phrases include "Should I continue or discontinue personal CGM for this inpatient who is already using it?" and "Is it appropriate to maintain personal CGM during hospitalization?"

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

This skill recommends follow-up morning cortisol and/or ACTH stimulation tests or insulin-induced hypoglycemia to assess HPA axis recovery in postoperative Cushing's syndrome patients with at least one intact adrenal gland. Triggers include postoperative remission (morning cortisol <5 µg/dL or UFC <28–56 nmol/d) and the need to evaluate HPA recovery before glucocorticoid discontinuation.

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

使用状态绑定的最小 Tool Surface、exact Action Gateway、来源可追踪的 MissionSpec 与 Verification Manifest、宿主无关 Flight Progression Engine、可选且无权威的 App Server continuation、顺序持久 Wave、一层原生 Agent、困难后强制战术指导、证据型 Capability Profile、显式 Manual Verification、不可变宿主 Evidence、恢复检查点和仅本地 Git，治理复杂 Codex 开发。用户要求飞控接管、继续、自主开发、修复或完成多步骤软件项目，需要有界并行子代理，或实现前必须建立文档工程时使用。

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

显式启用或关闭一个受治理 Run 的本地 Codex App Server continuation。仅当用户使用精确命令 `$flight-connect-host` 并依次提供 run_id、thread_id 与 ENABLE 或 DISABLE 时使用；不能把自然语言同意、Lead 判断、UI 操作或已有 credential 当作启用授权。

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

Coordinate Codex work across the current task, internal subagents, user-owned tasks, worktrees, handoffs, formal review gates, or recurring automation. Use for delegation, parallel roles, another Codex task, cross-repo work, QA/review handoffs, scheduled follow-up, or task inspection and continuation. Chinese triggers include 子Agent/子进程/子对话, 另一个对话接手, 并行处理, 分给QA, 多仓库收口, 巡检, 持续推进, 定时自动继续, 创建/读取/转交任务.

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

Explicit-only workflow that writes a redacted continuation handoff to a unique temporary Markdown file. Use only when the user explicitly asks for a handoff for another session.

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

Debrief a finished Otameshi Tenshoku trial from the employer's side: set the observed facts against the completion criteria agreed before the start, keep expectations added afterwards, second-hand or off-the-job observations and the company's own late or missing support apart, settle the hours actually worked separately from any evaluation, and draft feedback to the candidate that states facts, support gaps and what happens next without promising a hire or continuation the company has not decided. Use when a hiring manager, recruiter or small-business owner wants to review a trial, decide what to tell the candidate, or work out the settlement after a shortfall; do not use to judge the candidate's aptitude or predict a hire, to cut pay or demand unpaid rework because of dissatisfaction, to compare candidates, or to send the feedback, pay, or update records on the user's behalf.

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

Write a continuation summary for governed work.

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

Design a self-improvement loop for a shipped product's AI agents — production traces feed evals, evals feed improvement proposals (prompts, playbooks, retrieval configs), and a human approval gate promotes changes with rollback. Technique-agnostic: chooses per project between ACE-style evolving playbooks, GEPA/MIPROv2 offline optimization, or simple eval-driven iteration via references/techniques.md. Load when the user asks to make my product's agents self-improving, learn from production traces, add a learning loop, evolve prompts or playbooks safely, promote agent improvements, or GEPA-style optimization. NOT harness-evolution (that improves the coding agent), NOT experimentation (product A/B tests), NOT agent-run-retro (dev-phase manual retros — this skill is the production-scale continuation).

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

Use this skill when the user asks how to determine whether a CMV operation is interstate vs intrastate, why it matters (federal vs state rules apply), the "continuation of journey" rule, state-specific intrastate exemptions, and what happens when an intrastate carrier picks up an interstate load. Cite 49 CFR 390.5 + state-specific exemptions.

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

Create handoff packages for session transitions. Use when ending sessions, preparing for continuation, saving session state, or creating resumable context.

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

Write and restore session state — session start, session end, memory write, handoff, continuation. Enforces what gets persisted so the next session resumes instead of restarting.

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

Requires OFOX_API_KEY — create one at https://app.ofox.ai, plus a publicly reachable reference video the user is authorized to use. Use when a user has a rough 3D white-model, clay, wireframe, blockout, previs, or animatic clip and wants a finished visual treatment that preserves its shot order, cut timing, camera framing, spatial layout, and motion directions. Distinguishes that structure-preserving job from a continuation beginning at the reference's final state. Do not use for two still endpoints (keyframe-animation), for appending and locally joining a new ending (video-extend-edit), or when still-image references must be combined with the video in one request — first/last-frame anchors conflict with video references in the shipped core, while mixed image/video references are untested.

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

Designs and verifies fail-closed continuation of a living durable agent after its VM, process, provider session, backend, or context window disappears. Use for body leases, generation fencing, cold-birth failure, process GC, native resume, cross-harness rebodiment, resurrection capsules, capability translation, ambiguous-effect reconciliation, and capacity-aware handoff. NOT for reviving an intentionally retired identity, generic disaster recovery, copying credentials or raw transcripts, ordinary process restart, or claiming metaphysical continuity.

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