DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to split a large task into parallel agent leaves with scoped claims with Unlazy

Run independent leaves in fresh agent contexts using scoped pipelines and ownership claims.

Authorization notice. Unlazy is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA tech lead coordinating several agents on a large change where some subtasks touch separate parts of the codebase.

The problemParallel agents can overwrite each other's files, and no shared record shows which subtask owns which paths.

The outcomeA scoped pipeline under .unlazy/ with a PLAN, ledgers, and claimed leaves, and one reduced status for the whole scope.

What you need first

  • Node.js 16 or newer
  • An AI agent that supports skills, such as Claude Code or Codex CLI
  • A repository with a task to verify and shell commands the gates can run

Steps

  1. Create a scoped pipeline under .unlazy/ with PLAN.md, GATES.md, and gates/leaf-*.md files, and give each ready leaf complete, disjoint OWNS: paths.
  2. Claim each ready leaf for its scope with node /scripts/gate-check.mjs --scope api --leaf leaf-1.2.1 --claim. (inferred, check the README)
  3. Let each agent run only the gates for its claimed leaf, sequentially by default.
  4. Run node /scripts/gate-check.mjs --scope api to reduce the ledgers and dispatch waves together. (inferred, check the README)
  5. Treat the scope as finished only when the output prints ALL MET, since an abandoned wave is a HANDOFF REQUIRED outcome.

Prompt for your agent

Use the unlazy skill in the repo <repo-path> to split <large-task> into scoped leaves with disjoint OWNS: paths. Claim each ready leaf, then run node /scripts/gate-check.mjs --scope <scope-name> and report the reduced result. Verify that the output says ALL MET before you report success.

Caveat. Lease matching is a coordination guard, not write isolation, so parallel agents can still write to the same files outside the claimed paths.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page