Who it is forA 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 problemEvery new project means rewriting the same baseline rules and starter items before any agent can start useful work.
The outcomeA new board starts with the spec rules and starter items for your project type, ready for an agent to begin.
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
npx pullboard init --blueprint web-app- Review the spec rows the blueprint wrote and approve the ones you agree with.
- Commit the setup with
git add -A && git commit -m "chore(repo): set up pullboard". - Run
pullboard blueprint saveonce your rules are approved, to reuse them for the next project. (inferred, check the README)
Prompt for your agent
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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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