Board Builder
Turns a statement of work, a plan or a Project Brief into a project board: epics and tasks with the document's own codes, priorities, sizes, dependencies and acceptance criteria. It never invents a date, a person or a value: what the document leaves open, it asks you.
Install
In Claude Code
/plugin marketplace add ronalddlopez/turbinez-pm/plugin install board-builder@turbinez-pmFrom the terminal
claude plugin marketplace add ronalddlopez/turbinez-pmclaude plugin install board-builder@turbinez-pmThe first command once; then any agent. Needs Claude Code and Node.js 22 or later.
Connect to Turbinez
/board-builder:connectOptional: the agent then works in a project in Turbinez, with your team. How connecting works
What it makes
The real thing, not a picture: what Board Builder made in our tests.
Built from the Project Brief that Project Intake wrote for Wrenfield, a made-up insurance broker, once the client's answers were in: 7 epics, 41 tasks, every deliverable code kept, and the client's open decisions as their own cards.
Use it
Build the board
From a SOW, a plan or the Project Brief. Ask again and only what's missing is added.
/board-builder:build-board docs/sow.mdCheck it
Compares the board with its document, code by code, and fixes the gaps.
/board-builder:check-boardChange it
In plain words: "Move ORD-2 to In review", "Split the reporting tasks into their own epic".
Its tools
A small local server: your project's files, or the connected project in Turbinez.
| Tool | What it does |
|---|---|
read_board | The whole board, a page at a time, with its totals |
get_cardsearch_cards | One card in full; cards matching some text |
create_cards | Many epics and tasks at once, all or nothing |
create_epiccreate_task | One card |
update_epicupdate_taskmove_task | Change a card; a new code follows every reference |
bulk_update | Change several cards at once; asks first above 5 |
delete_cardsrestructure | Delete cards, or merge, split and move epics. Asks you first |
read_brief | Reads the Project Brief to build from |
Connect to Turbinez
Optional. Connected, Board Builder works in a project in Turbinez instead of the folder's files, with the same tools, and your team sees every change.
/board-builder:connectSigns you in through the browser and links this folder to a project in Turbinez, a new one or one your team already has. From then on, the agents write there.
/board-builder:status- Says which project the folder is connected to and whether the connection works.
/board-builder:import- Brings the folder's own board, Brief and surveys into an empty project, when they didn't come in on connect.
/board-builder:export- Writes the project's copy into
turbinez/, so the agents can work from the files after you disconnect. /board-builder:disconnect- Ends the connection. The folder's files stay, and the agents work from them again.
A folder that already has a board, a Brief or surveys can bring them into a new, empty project when it connects, or leave them where they are.
Connecting needs a free Turbinez account. Turbinez is in early access, inviting teams a few at a time.
What it promises
Nothing invented
No dates, people or values the document doesn't give. The gaps come back to you as questions.
Every change checked
The tools refuse a bad change with a sentence saying what to fix. Nothing broken is ever saved.
Your yes before a delete
Deleting or restructuring cards, or changing more than 5 at once, waits for you. Git keeps the history, so anything can be undone.