Agent Skills: concurrent-change

Use when work is about to be split across multiple agents, or when deciding whether it should be. Concurrency is a property of the change, not a scheduling decision — what can proceed at once is determined by what the pieces have to agree on. Trigger on any request to parallelise, fan out, delegate to subagents, or run work concurrently, and whenever a plan has more than one independent-looking piece. Do NOT use for single-threaded work, or for splitting purely to appear fast.

ID: bfollington/terma/concurrent-change

Repository

bfollingtonLicense: CC-BY-SA-4.0
526

Install this agent skill to your local

npx skills add bfollington/terma --skill concurrent-change

Skill Files

The files that make up concurrent-change.

Download Skill

More agent skills