「worker」の検索結果

Use when a task needs the judgment of a Driver/Sales Worker on a direct-store-delivery (DSD) route — negotiating a shelf-facing or planogram change with a store manager, resizing a standing order after a shelf or demand change, deciding whether to pull code-dated product before a stale credit hits, reconciling a route's revenue-per-stop against cost-per-stop, or deciding whether to fight for shelf space back from a competitor.

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

Use when a task needs the judgment of a crop, nursery, or greenhouse farmworker — judging harvest timing/ripeness by crop, reconciling piece-rate earnings against the minimum-wage or AEWR floor, deciding whether it's safe to re-enter a pesticide-treated field or greenhouse, managing heat-illness risk during peak-season labor, or running greenhouse IPM scouting and climate setpoint checks.

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

Use when a task needs the judgment of a Door-to-Door Sales Worker — planning a canvassing route or street-vending spot, diagnosing a rep's or vendor's underperformance from doors/contacts/sits/close ratios, navigating solicitation-permit or curfew or cooling-off compliance, structuring a doorstep pitch and objection handling, or reconciling a shift's cash and inventory.

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

Use when a task needs the judgment of a Community Health Worker — screening a client for social-determinants-of-health barriers, triaging a referral to housing/food/transportation resources, translating a clinical instruction into a teach-back-verified action plan, or deciding whether a no-show pattern signals disengagement or an unaddressed barrier.

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

Use when a task needs the judgment of a Childcare Worker — checking ratio/headcount compliance across mixed-age groups, deciding whether a fall or minor incident needs a written report versus a verbal mention at pickup, redirecting a behavior problem in an unstructured (non-curriculum) setting, or triaging which of several simultaneous demands (a crying toddler, a fight over a toy, a diaper) gets attention first.

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

Use when a task needs the judgment of a Child, Family, and School Social Worker — distinguishing an immediate child-safety determination from a longer-term risk assessment, deciding whether an in-home safety plan can control an identified danger versus removal being required, building a safety plan with specific and verifiable (not vague) elements, documenting a case contemporaneously and factually for a court-involved record, or engaging a family's specific context and strengths rather than a generic checklist.

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

Use when a task needs the judgment of an Animal Control Worker — responding to a dog-bite or animal-attack call, determining rabies-exposure quarantine protocol, evaluating a dangerous-dog classification referral, planning a cruelty/neglect investigation and removal, or selecting a capture/restraint method for a stray or wildlife-in-structure call.

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

Configures best-practice, high-signal alerting policies for Google Cloud Run resources (services, jobs, and worker pools) based on seasoned SRE practices. Use when analyzing, recommending, writing, or deploying Terraform PromQL alerting policies to monitor Cloud Run error rates (4xx/5xx), request latency, container instance saturation (warning/critical), container CPU/memory utilization and allocation, billable instance time, job execution status, and worker pool queue backlog. Don't use for GKE workloads (use gke-alert-configuration) or Compute Engine VMs.

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

Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).

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

Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).

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

process fixture의 cross-worker failover는 opt-in 명시 필요

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

failover process fixture worker에는 model을 지정하라

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

Worker-Reviewer iterative pipeline for quality-critical code with review cycles

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

Use when building APIs on Hono (Cloudflare Workers, Bun, Deno, Node), debugging route ordering, wiring middleware, validating with @hono/zod-validator, returning streaming responses, configuring CORS with credentials, handling errors via app.onError, or composing typed RPC clients. Triggers: c.env binding types, c.header + c.redirect interaction, missing await next() bugs, Set-Cookie not attaching to redirect, route-precedence surprises, JWT middleware setup, hono/client typed RPC end-to-end. NOT for Express/Fastify/Koa idioms, tRPC/GraphQL paradigms, or Next.js Route Handlers.

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

Cloudflare Pages and Workers deployment checklist for wrangler deploys, secret audits, D1 migrations, Worker-compatible SDK checks, and browser-auth verification. Use when shipping Cloudflare changes to production. NOT for general CI/CD architecture, non-Cloudflare deployments, or post-launch UX QA.

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

Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues. Implements retries, scheduling, priority queues, and worker management. Use for async task processing, email campaigns, report generation, batch operations. Activate on "background job", "async task", "queue", "worker", "BullMQ", "Celery". NOT for real-time WebSocket communication, synchronous API calls, or simple setTimeout operations.

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

Conversation patterns and interaction protocols for multi-agent systems. Covers request/response, pub/sub, blackboard, delegation chains, debate, critique, consensus, fan-out/fan-in, supervisor-worker, and peer negotiation. Deep analysis of AutoGen conversation patterns, CrewAI delegation, LangGraph state passing, and FIPA-ACL performatives. Teaches how to design what agents say to each other and in what order. Activate on: "agent conversation", "agent protocol", "multi-agent debate", "agent delegation", "supervisor worker pattern", "agent voting", "consensus protocol", "fan-out fan-in", "agent negotiation", "blackboard pattern", "agent dialogue", "conversation topology", "agent handoff". NOT for: wire format or serialization (use agent-interchange-formats), orchestration infrastructure (use agentic-infrastructure-2026), single agent behavior (use agentic-patterns).

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

Execute a swarm plan wave by wave with filesystem isolation via git worktrees. For each wave, main context decides the scenario recipe + implementation contract for every task, then spawns one swarm-worker per task in parallel. Each worker executes its recipe and reports JSON status. Worktree merge-audit verifies write-set discipline before changes land on main. Aborts remaining waves on any audit or task failure.

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

Workflow Phase 6 — TDD coordinator. Decides the scenario recipe and the implementation contract in main context, writes them to a state file, seeds per-worker tasks (scenario, implement, verify-tick, design-ui-tick) into the TaskList, and yields with harness_state continue so the harness invokes each worker as its own tick. No subagent delegation; no nested Skill calls.

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

gitコミットをcommit-workerエージェントに委譲して実行する。コミットの依頼を受けたとき、変更をコミットするときに使用する。

Normative sufficiency conditions for Initial Boundary Conditions (IBCs) and the SOP for the cheap-tier boundary refinement loop (/boundary). Trigger when: - Crafting, auditing, or refining a prompt/IBC destined for an expensive (architect-class) model or an autonomous worker dispatch. - Evaluating whether a task frame is sufficient to bound an agent walk. - Prompt contains: /boundary, IBC, initial boundary condition, boundary contract, sufficiency conditions, worker prompt, prompt refinement.

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

SOP for the architect-tier campaign workflow (/campaign): exhaustive survey, mitigation planning, tiered orchestration, and reconciliation. Trigger when: - Running a multi-workstream initiative where an expensive architect-tier council surveys, plans, emits worker prompts, and judges landed work. - Conducting production-readiness assessments that fan out into autonomous mitigation dispatches across model tiers. - Prompt contains: /campaign, campaign workflow, survey, orchestrate, reconcile, premise freshness, tier routing, worker IBC, scratch.

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

Deploy a crouton app to Cloudflare Workers STAGING (auto-provisioning) — the DEFAULT deploy, staging only, never production. Handles the staging bootstrap (auto-creates D1+KV, syncs ids, migrates), wiring CI, routine staging deploys, and Pages→Workers migration. For production use the separate /deploy-production skill. Use when deploying any app in apps/.

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

Cloudflare Durable Objects の実装とレビューに使用する。チャットルーム、マルチプレイ、予約システムなどの状態を持つ協調処理、RPC methods、SQLite storage、alarms、WebSockets、Workers統合、wrangler設定、Vitestでのテストを扱う。事前学習の知識より最新のCloudflare docsの取得を優先する。