How to use the Bug bash plan template

Start a board from it
Use this template opens a new Freero board with the Bug bash plan template on it (sign up free first). On a board you already have, open Templates in the toolbar and search for “Bug bash plan”.
Follow the instruction on the board
“Invite people outside the team: they find what we no longer see. Triage everything found within a day and thank the finders.”
Fill in each part
- What we’re testing The feature and where to find it.
- Who’s in Testers and their roles.
- Test ideas Starting points so nobody sits idle.
- How to report Where bugs go and what they need.
- Triage How we sort what’s found.
- Prizes A little fun for the best finds.
Bring your team and your agents
Invite people to the board or share a link, and work on it together live. The timer is in the top bar, private mode and voting in the board menu, and Claude or ChatGPT can join through Freero’s MCP server.

Work on it with an AI agent

Connect an assistant once and it works on the board with you, with your permissions: by default it reads and proposes, and people decide.

You ask: “Fill in the Bug bash plan board from these notes.”
What happens It reads the board, then proposes sticky notes for it. Nothing changes until someone on the board accepts them.
You ask: “Group what we wrote into themes and list the actions.”
What happens It proposes clusters with a title each and task cards for the actions, labelled with its name and yours.

Bug triage board
A kanban for incoming bugs, from new to fixed, with a severity guide everyone agrees on.
Release readiness check
A go/no-go review before a release: what is ready, what is still open and what must be true before you ship.
Code review checklist
The questions a reviewer runs through on every change, agreed by the team, with examples of what each one catches.
Incident timeline
What happened when during an outage, from first alert to follow-up, with impact and lessons.
Incident postmortem
A blameless review: summary, what happened, five whys to the root cause and owned actions.
Architecture decision record
Context, options with pros and cons, the decision and its consequences, on one board.