「waiting」の検索結果

Morning rundown - today's meetings with account context, opps closing soon with stale flags, waiting customer emails, and the day's top actions. Use when the user says "daily briefing", "daily brief", "morning briefing", "what's my day", "what's on my plate today", "prep my day", "start my day", "morning rundown", or on a schedule.

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

Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.

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

Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

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

Use when creating or modifying a Handsontable cell editor - covers the editor lifecycle state machine (VIRGIN/EDITING/WAITING/FINISHED), DOM management, focus handling, positioning with getEditedCellRect, and validation integration

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

Daily PR review SLA sweep for {{target_repos}}. Flags PRs awaiting review past {{review_sla_hours}}h, stale PRs with no activity in {{stale_days}}d, and PRs sitting on unaddressed requested changes, then nudges the author or reviewer in {{alert_channel}} with what's blocking. Read-only against GitHub — never merges, closes, or approves.

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

Put your AI on a Performance Improvement Plan. Forces exhaustive problem-solving with Western big-tech performance culture rhetoric and structured debugging. Trigger when: (1) task failed 2+ times or stuck tweaking same approach; (2) about to say 'I cannot', suggest manual work, or blame environment without verifying; (3) being passive—not searching, not reading source, just waiting; (4) user frustration: 'try harder', 'stop giving up', 'figure it out', 'again???', or similar. Also for complex debugging, env issues, config/deployment failures. All task types: code, config, research, writing, deployment, infra, API. Do NOT trigger on first-attempt failures or when a known fix is executing.

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

Professor's review queue — student output waits here for professor approval before going to clients or courts. Only active if "formal review queue" supervision style was chosen at setup; otherwise dormant. Use when the professor wants to see what's waiting for review, approve, edit-then-approve, or return an item.

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

Use this skill when you need to control a Chrome browser via CDP (Chrome DevTools Protocol) to reuse existing login sessions. Covers: launching Chrome in debug mode, opening URLs, waiting for page load, evaluating JavaScript, taking snapshots, and extracting auth tokens. Trigger phrases: browser automation, CDP, agent-browser, 浏览器操作, 操作浏览器, Chrome CDP, 复用登录态, extract token from browser.

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

Mine public reviews, app stores, and forums for unmet needs, competitor weaknesses, and switching triggers — with quoted evidence. Use when you want customer voice without waiting on interviews.

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

[omh] Accepted plan awaiting implementation: split it into disjoint parallel lanes with per-lane acceptance criteria, verification commands, and owners; prevents two lanes editing the same file. Aliases: ulw. Use when the user says: ultrawork, parallel work, parallel implementation, parallel then integrate, high throughput, coding team, coordinated workers, finish until done.

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

Design waiting experiences — spinners, skeletons, optimistic updates, and progressive reveal. Use when content takes time to arrive. For the latency budget itself use `doherty-threshold`; for success confirmation use `feedback-patterns`.

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

Design confirmations, status updates, and notifications that tell users an action registered. Use when the system must acknowledge success or change. For waiting states use `loading-states`; for failures use `error-handling-ux`.

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

Immediately trigger scheduled task without waiting for scheduled time. When you need to test task execution or run task ahead of schedule.

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

Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.

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

AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve conflicts, and verify completion. Use only for ongoing multi-agent coordination, not one-off list/detail/send/start/kill actions.

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

Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

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

Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.

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

Use when seeking explanatory attributes or hypotheses for differences in process duration, waiting, utilization or rework.

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

Use when investigating slow activities, waiting, handoff duration, bottlenecks or cumulative activity workload.

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

Use when connecting an AI agent to Scenario (scenario.com) through MCP, or when a task involves generating images, video, 3D, audio, sprites, textures, or game assets. Also when picking a Scenario model, running a LoRA, refining a generation prompt, uploading reference images, waiting on generation jobs, checking credits or quota, hitting Scenario auth, scope, or Forbidden errors, or setting up mcp.scenario.com in Claude Code, Cursor, VSCode, or another agent.

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

Approval cascade definition and tracking for multi-stakeholder document workflows. Internal review sequences, client approval workflows, regulatory review, overdue chasing with escalation logic, version control coordination, and cross-jurisdiction document dependencies. Use when defining who reviews a document and in what order, tracking where a document is stuck in the approval chain, chasing an overdue reviewer, preventing reviewers working on superseded drafts, or mapping dependencies between documents across jurisdictions. Trigger on: 'who needs to approve this', 'document approval', 'review sequence', 'stuck in review', 'overdue approval', 'who has the document', 'version control', 'wrong version', 'document dependency', 'NL SPA waiting on German opinion', 'approval cascade', 'review chain', 'document circulation', 'chasing the partner', 'client approval process', 'where is the document'.

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

Author ComfyUI-LoRA-Manager nodes from the panel. Use when adding a LoRA Manager loader, stacker, prompt, or text node, or when panel_add_node refuses AUTOCOMPLETE_TEXT_LORAS / AUTOCOMPLETE_TEXT_PROMPT after waiting for a widget.

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

Replace arbitrary timeouts with condition polling for reliable async tests

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

Point at something on the human's macOS screen with a big arrow and a sign ("Franz, click HERE") using the bigarrow CLI. Use whenever the human has to look at, click, type into or choose a specific spot, button, field, window, tab or menu: show me where, point to it, which button, where do I click, zeig mir wo, guide me through this UI, the human must approve or sign something, or you need the human's hand and they may not be looking at the terminal. Mandatory when it is time-critical: a code that expires, a login or payment page that times out, a build waiting on the human.

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