'dispatching' 검색 결과

Plan, implement, or review dispatching parallel agents work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests dispatching parallel agents work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

여러 Claude Code 에이전트에 개발 작업을 나누고 독립된 작업 환경에서 병렬로 실행합니다. 작업 의존성과 진행 상황, 변경 사항과 오류 보고서를 관리합니다.

• 의존성을 포함한 개발 계획 나누기
• 독립된 작업 환경에서 병렬 개발하기
• 여러 개발 작업의 진행 상황 확인하기

Dispatches due Xiaohongshu tasks already locked in the operations dashboard to their assigned account workers. It checks task identifiers, records delivery failures, and continues dispatching other tasks without operating the browser or changing content.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Dispatching due tasks to assigned account workers
• Continuing other deliveries when one task fails
• Checking how scheduled tasks should be executed

Use when legacy prompts or older framework flows reference `dispatching-parallel-agents` and you need the modern runtime to resolve that capability cleanly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use multiple Claude agents to investigate and fix independent problems concurrently

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

서로 독립적인 버그나 테스트 실패를 별도 에이전트에 맡겨 동시에 조사하고 수정합니다. 담당 범위를 정하고 결과 검토, 변경 충돌 확인, 전체 테스트와 통합까지 안내합니다.

• 원인이 다른 테스트 실패 조사
• 서로 다른 기능의 독립적인 버그 수정
• 여러 에이전트의 담당 범위 정리

Paperclip 인스턴스가 만든 풀 리퀘스트의 목적과 병합 준비 상태를 확인하고, 미완료 항목을 수정 작업으로 연결한 뒤 최신 변경의 검증 결과를 보고합니다.

• 현재 인스턴스가 만든 풀 리퀘스트 점검
• 검사 실패나 충돌의 수정 요청
• 수정 후 병합 준비 상태 재확인

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Split independent debugging or repair tasks among multiple AI agents. Define a focused scope, constraints, and expected report for each agent, then review their changes, check for conflicts, and test the combined result.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating unrelated failures across test files
• Assigning separate subsystems to different agents
• Writing focused tasks with clear constraints

Deploy ClawHub to production or publish a stable CLI release to npm. Check prerequisites for the exact commit, run the release workflow, and verify the deployed behavior or published version with traceable release evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy ClawHub to production
• Publish a stable ClawHub CLI version
• Check release prerequisites for a specific commit

Investigate independent bugs or test failures concurrently by assigning each problem area to a separate agent. Define clear boundaries and expected reports, then review the fixes, check for conflicts, and run the full test suite before integration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate unrelated test failures in parallel
• Split independent subsystem bugs among agents
• Write focused assignments with clear boundaries

Helps decide whether to handle a task directly, create a subagent, or route it to an agent already familiar with the work. The choice depends on required background knowledge and whether plausible but incorrect results can be checked.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing who should handle a task
• Delegating self-contained research with verifiable sources
• Routing context-heavy reviews to an informed agent

Collect posts from X search, profile, individual post, and list URLs. Organize text, authors, engagement counts, media, hashtags, and mentions into a consistent dataset, with support for collecting additional pages.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Collecting posts from a mixed list of X URLs
• Monitoring posts from selected profiles and lists
• Gathering replies to a specific post

Create Beamer slides from a paper on sewage spills, house prices, and rents in England. A creator and critic pair builds and reviews four talk formats, checking narrative, readability, compilation, and consistency with the paper.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a job market talk from the research paper
• Building a seminar deck centered on the main findings
• Condensing the paper into a short or lightning talk

Assign independent bugs or test failures to separate agents that work at the same time. Define each agent’s scope and expected report, then check for conflicting changes and run the full test suite before integrating fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating test failures with unrelated causes
• Fixing independent problems in separate subsystems
• Defining focused tasks for multiple agents

DOCA-shipped Zero-Touch RoCE RTT congestion control (ZTR RTTCC) reference algorithm on a BlueField-3 DPA: deploy, tune and evaluate doca_pcc_dev_ztr_rttcc_algo through the shipped DOCA PCC sample. Trigger on "my RoCE-v2 flows aren't being throttled", "PCC sample isn't dispatching to my algo", "set-params returns fail", "algorithm loaded but counters are flat", "how do I pick the multipath PCC variant", or "do I need a custom CC algorithm on BF3", even without naming ZTR RTTCC. Your own algorithm through the host library belongs to doca-pcc; the doca_spcx_cc command line to doca-spcx-cc. Covers picking a variant (vanilla / PM / RX-rate / multipath / window-probeless) at DPACC build time, tuning host-set parameters, and DOCA_PCC_DEV_STATUS_FAIL from the algorithm. Refuse and route elsewhere for writing a custom PCC algorithm from scratch, read-only PCC counter inspection, or firmware-only pre-Programmable PCC.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure delegation fleet lanes: which implementer CLI handles which kind of work, with optional model and effort (or variant) dials. Discovers installed CLIs, proposes a lane map for user approval, and writes global or project config only after explicit yes. Use when the user asks to set up, configure, or reconfigure delegation lanes, a fleet of lanes, or which implementer handles feature/tests/ui work — not for dispatching a coding task to an implementer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Parallel research agent orchestration dispatching 5-10 concurrent agents for comprehensive multi-source research with synthesis and validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when facing 2+ independent tasks without a written plan, with no conflicting shared mutable state or sequential dependencies, where parallel delegation beats inline cost; otherwise inline. Planned tasks use subagent-driven-development.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when executing a written implementation plan with independent tasks in the current session where delegation beats inline coordination cost; otherwise inline. Ad-hoc 2+ tasks without a plan use dispatching-parallel-agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development. Covers Spec-Driven Development, Context Engineering, and post-dev workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.