# AI use cases for Pullboard (pullboard-dev/pullboard)

Repo: [pullboard-dev/pullboard](https://github.com/pullboard-dev/pullboard) | Use cases: 5 | Page: https://dedupedai.com/use-cases/pullboard-dev-pullboard/

Pullboard is a local coordination board, stored in a git repo, that lets AI agents build software from specs you approve, with a second agent verifying each change before it counts.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- See a builder and verifier agent work one rule: https://dedupedai.com/use-cases/pullboard-dev-pullboard/tour-the-agent-review-loop/
- Set up agent coordination in an existing repo: https://dedupedai.com/use-cases/pullboard-dev-pullboard/add-agent-coordination-to-existing-repo/
- Ship one approved feature with a second-agent check: https://dedupedai.com/use-cases/pullboard-dev-pullboard/ship-approved-feature-with-verifier/
- Start a new project from a spec blueprint: https://dedupedai.com/use-cases/pullboard-dev-pullboard/start-project-from-blueprint/
- Watch and steer agents from one local board: https://dedupedai.com/use-cases/pullboard-dev-pullboard/steer-agents-from-one-board/

## How to see a builder and verifier agent work one rule with Pullboard

Repo: [pullboard-dev/pullboard](https://github.com/pullboard-dev/pullboard) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Run the guided tour to watch a coordinator, builder and verifier handle one approved rule end to end.

**Who it is for:** A developer who has heard of agent-built software and wants to see the review loop on a safe repo before using it on real work.

**The problem:** It is hard to judge whether agents can be trusted with a build without seeing how claims, submits and verdicts actually flow.

**The outcome:** You see one rule filed, built, rejected, fixed and accepted, with a receipt in the activity log.

### Steps

1. `npm i -g pullboard`
2. `pullboard tour`
3. Approve the one rule the tour asks for, then watch the coordinator, builder and verifier take their turns.
4. Read the receipt the coordinator writes when the verifier accepts the fix.

### Prompt to paste into your agent

```text
In the repo <path>, install Pullboard with `npm i -g pullboard` and run `pullboard tour`. Report the final accepted verdict and the reason the verifier gave. Verify that the greeting for a blank name now returns "world" in the test the builder added.
```

### Caveat

The tour needs git and Node 22.13 or newer, and the README says Windows is not tested yet, so run it on Linux or macOS.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/pullboard-dev-pullboard/tour-the-agent-review-loop/

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

Repo: [pullboard-dev/pullboard](https://github.com/pullboard-dev/pullboard) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README

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

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

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

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

### 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 to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/pullboard-dev-pullboard/add-agent-coordination-to-existing-repo/

## How to ship one approved feature with a second-agent check with Pullboard

Repo: [pullboard-dev/pullboard](https://github.com/pullboard-dev/pullboard) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README

File a spec-linked item, let a builder claim and submit it, then have a verifier accept or reject the exact commit.

**Who it is for:** A developer with an approved requirement who wants a builder agent to implement it and a separate agent to check the result.

**The problem:** Agent output is often merged on trust, and no one checks it against the requirement it was supposed to meet.

**The outcome:** The feature lands only after a different agent verifies the submitted commit against the approved row, with evidence recorded.

### Steps

1. `pullboard add web "Checkout" --specs G1 --criterion "card payment takes one step"`
2. `pullboard worktree web --model "$PULLBOARD_MODEL"`, then `cd` into the worktree it prints and run `pullboard next` and `pullboard submit 1`.
3. `pullboard worktree review --model "$PULLBOARD_MODEL"`, then `cd` into that worktree and run `pullboard next --verify`.
4. `pullboard verify 1 accept --note "paid in one step; without the fix the test fails"`

### Prompt to paste into your agent

```text
In the repo <path>, file a Pullboard item linked to approved spec row G1, have a builder agent claim and submit it, then have a separate verifier agent run `pullboard verify <id> accept` or reject with a reason. Report the verdict and the note. Verify that the verifier checked out the exact submitted commit before deciding.
```

### Caveat

The example commands use placeholder names like web and G1, and the gate in Pullboard.json must run your real tests, or submits will not be green.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/pullboard-dev-pullboard/ship-approved-feature-with-verifier/

## How to start a new project from a spec blueprint with Pullboard

Repo: [pullboard-dev/pullboard](https://github.com/pullboard-dev/pullboard) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Create a board from a bundled blueprint for your kind of project, so the rules and starter items are ready.

**Who it is for:** A developer starting a new web app, library, iOS app or data pipeline who wants the spec rules and starter items set up for that kind of project.

**The problem:** Every new project means rewriting the same baseline rules and starter items before any agent can start useful work.

**The outcome:** A new board starts with the spec rules and starter items for your project type, ready for an agent to begin.

### Steps

1. `npx pullboard init --blueprint web-app`
2. Review the spec rows the blueprint wrote and approve the ones you agree with.
3. Commit the setup with `git add -A && git commit -m "chore(repo): set up pullboard"`.
4. Run `pullboard blueprint save` once your rules are approved, to reuse them for the next project. (inferred, check the README)

### Prompt to paste into your agent

```text
In an empty git repo <path>, run `npx pullboard init --blueprint web-app` and list the spec rows and starter items it created. Report which rows are still drafts that need your approval. Verify that the rows are marked draft until approved.
```

### Caveat

The README lists ten bundled blueprints and says the feature is new in 0.8.29, so check your installed version supports the blueprint you want.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/pullboard-dev-pullboard/start-project-from-blueprint/

## How to watch and steer agents from one local board with Pullboard

Repo: [pullboard-dev/pullboard](https://github.com/pullboard-dev/pullboard) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Open the Pullboard View to see what needs your decision, follow item history and export a snapshot.

**Who it is for:** A developer running several agents in parallel who needs to see open decisions and approve changes without reading every terminal.

**The problem:** With many agents working at once, pending questions and approvals get lost across terminals.

**The outcome:** You answer only the calls that need you, follow each item's claims and verdicts, and save a replayable snapshot.

### Steps

1. `pullboard view`
2. Check the Needs you section for decisions passed up, rows to approve and held lanes.
3. Open an item to read its claims, submits and any reject reasons in the timeline.
4. `pullboard view --export` (inferred, check the README)

### Prompt to paste into your agent

```text
In the repo <path> with Pullboard set up, run `pullboard view` and list the items under Needs you. Then run `pullboard view --export` and report the file it writes. Verify that the snapshot contains the same items shown in the live view.
```

### Caveat

The README says the board is one SQLite file inside .git on your machine and is not hosted, so the view only shows items from repos on that machine.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/pullboard-dev-pullboard/steer-agents-from-one-board/