本文へ移動
cccskills
無料GitHub で公開

parallel-agent-delivery

Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broad search or audit would be faster fanned out, or when deciding whether work can safely be split at all.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.2 KB
  • references/sources.md827 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Parallel agent delivery

Parallelism is a property of the work, not a preference. Establish it before dispatching.

When it is safe

All three must hold:

  1. Disjoint write surfaces — no two agents touch the same file. Not "unlikely to conflict"; provably disjoint.
  2. No sequential dependency — none needs another's output to start.
  3. Independently verifiable — each result can be judged on its own.

Fail any one and run sequentially. Two agents editing one file produces a merge conflict at best and a silent lost update at worst.

Dispatching

Each agent gets a self-contained brief: the goal, its exclusive surface, the context it cannot see for itself, and the shape of the answer expected. Agents share no memory — anything you leave out is gone.

Ask for a structured return, the same shape from each, so results can be compared rather than re-read.

Read-only fan-out is the easy case

Searching, auditing, and reviewing have no write surface at all, so they parallelize without risk. Reach for parallelism here first and freely.

Integrating

  • Review each result against its brief before merging any of them.
  • Where two disagree on a shared fact, neither is authoritative — resolve it yourself.
  • One agent returning nothing useful is a normal outcome, not a failure to retry blindly.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Split work to look faster when the steps are actually sequential.
  • Let two agents write to one surface because "they probably won't collide."
  • Merge a result you have not read.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

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

cbrock84/headcount2,0312026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

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

cbrock84/headcount2,0312026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

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

cbrock84/headcount2,0312026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

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

cbrock84/headcount2,0312026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

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

cbrock84/headcount2,0312026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

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

cbrock84/headcount2,0312026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する