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

How to set up agent coordination in an existing repo with Pullboard

Run Pullboard init in a git repo so a coordinator agent can take your requirements and fan out work.

Who it is forA developer with an existing project who wants Claude Code or Codex to build new features from written requirements.

The problemEach new agent session starts without the decisions you already made, so you end up re-explaining the project every time.

The outcomeThe repo holds an approved spec, doctrine, agent instructions and a board, and one coordinator agent leads the work.

What you need first

  • Git installed
  • Node 22.13 or newer
  • A git repository to work in (the tour uses a throwaway repo)
  • npm, to install the pullboard package

Steps

  1. npm i -g pullboard
  2. pullboard init
  3. git add -A && git commit -m "chore(repo): set up pullboard"
  4. Open Claude Code in the repo and describe what to build. That agent becomes your coordinator.

Prompt for your agent

In the git repo <path>, run `pullboard init`, then commit the files it wrote with `git add -A && git commit -m "chore(repo): set up pullboard"`. Report the files created and confirm that SPEC.md and DOCTRINE.md exist at the repo root.

Caveat. The README says the gate must be a command that proves your code, so you still need to set Pullboard.json for your stack before work can be submitted.

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