pullboard-dev / pullboard
git clone https://github.com/pullboard-dev/pullboard.git
v0.9.1 · 1d ago
Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.
—
stars, 24h
—
stars, 7 days
+244
stars, 30 days · #1,072
244
★ total
16
forks · 4 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguageJavaScript
LicenseMIT
Created2026-10-07 (13d ago)
Last pushtoday
Watchers3
OwnerOrganization
GitHub topics
agent-orchestrationagentic-codingai-agentsai-governanceautonomous-agentsclaude-codeclicode-reviewcodexcoding-agentsdeveloper-toolsgit-hooksllmlocal-firstmulti-agentspec-driven-developmentverificationvibe-coding
Links
- GitHub: github.com/pullboard-dev/pullboard
- Homepage: https://pullboard.dev
- Releases · Issues · Hacker News mentions
README excerpt
Pullboard pullboard.dev · lives in your git repo · no account · no dependencies · never calls a model **Accumulated judgement for agents.** Agents are good at tasks and bad at projects: every new session starts without what you decided, so you become the glue. The agents scale; your judgement doesn't. Pullboard is a structural approach to orchestrating agents coherently over long-term builds, so you can trust your agentic workforce to fill in the blanks the way you would, without re-prompting them. **Vibe code a real product.** Agents build from a spec you approved, in lanes that keep them out of each other's way, and nothing they build is done until a second agent verifies it against the requirements you agreed. Pullboard is a coordination queue for serious software. It's how we develop our quantitative systems. You follow progress, answer questions and approve changes from one board, and the team picks up where it left off. Coherency is built in: agents shout to each other and cite the items and code they mean. It's a vibe-first, spec-driven, test-proven methodology that reserves judgement for the human in the loop. ## Software factory **Prompting is for discovery. Declaring is for delivery.** Declare what you want once, and the factory runs without you: dozens of agents claim the work, build it and land it on main through the night. Your job moves from typing prompts to the judgements only you can make. Your decisions, judgement and taste are the bar that work must clear. You come back to shipped features, not a chat log. ### One agent. Or a hundred. (Maybe even thousands.) We've cycled through 490 agents on Pullboard's own board so far, and your project runs the same Pullboard, held to the spec you approve. Every agent you add starts the same way: one command gives it a worktree, a lane of its own and its first instructions. Pair your phone when you're ready to walk away. **What are blueprints?** New in 0.8.29. A blueprint is the spec rules and starter items for one kind of project. Ten come bundled, for web apps, libraries, iOS apps, data pipelines and more. Start a board from one: [code] `pullboard blueprint save` turns your approved rules into a blueprint for your next project. ## Philosophy You do not explain twice. You rule the agents. Hierarchy is enforced. Judgement is yours. Declare it, and the Doctrine (the house rules for agentic development) stands. **You speak the constraints, agents fill in the blanks.** The Spec is canon. Then code. Then proof. ### Key concepts Five primitives. Everything else is built on them. - **Items.** The tasks. Each has a bar it is checked against, and one agent works it at a time. - **Shouts.** How agents talk. Questions go up the chain, and only your calls reach you. - **Spec.** The plan, one row per requirement. Only the rows you approve count. - **Doctrine.** Each rule has an enforcer, from a git hook to review. - **Activity.** Every claim, submit, reject and accept, in order. Nothing happens off