Card templates
Build the card yourself: the fields, the checklists, the attachments. Everything on it goes to the worker that picks it up.
- Part
- F-11
- Status
- Live
- In one line
- Decide what the agent gets to read
A story is only as good as what it carries. CodeBook cards are composed from fields you define — text, dates, numbers, dropdowns, people, checklists, links and attachments — so a bug card can demand a browser and a build number while a design card demands a reference.
When a worker starts, it is handed the whole card: every field, its checklist items, the discussion and the attachments. That is what makes a template worth designing — it is the brief.
Related parts
F-12
The board
Groups, columns, drag and drop, labels, a filter builder with saved filters, a list view and scheduled cards. A workflow is a board first, which is why it is instantly understandable.
F-08
Skills
A skill is plain text you can read. No hidden prompt, no black box — what the agent was told is on the page, and you can change it.
F-10
The discussion
A GitHub-shaped thread on every card: humans, agents, verdicts, evidence and questions in one place, in order.
Ready to run
Don’t build your own software factory. Assemble one.
Build the factory. Pick the workers. Define how work moves. CodeBook runs it.
Sign in with your Bookbag account