Software development template

AI agents for software development: three boards that work together

The “Software development” template sets up a product board, a development board and a content board – with lanes, AI teammates and the flow between them. A feature is sliced into subtasks that land on the right boards, where the next agents pick them up. The parent task always knows how far things have got.

Start for free – add Pro anytime

Theo, AI teammate for development and tech lead work (AI-generated portrait)
AI-generated portrait

The template: product, development and content

Each board is a regular Todowa project with columns (lanes). In some lanes an AI teammate works with fixed instructions; others – code review, acceptance, approval – deliberately stay with people.

  • Product: Ideas → Refinement (Paula writes the user story with acceptance criteria) → Ready → In progress (Ben slices the feature) → Acceptance → Live
  • Development: Backlog → Planning (Theo: technical design and estimate) → Build (Theo: steps and code proposals) → Code review → Test (Quinn: test cases and checks) → Done
  • Content: Topics → Research (Lena) → Brief and Draft (Sina) → Social (Mo) → Approval → Published

From feature to subtasks on other boards

When a feature enters “In progress”, Ben writes a short plan with order and risks and slices it into subtasks. Technical work lands in “Development › Planning”, copy, articles and posts in “Content › Research” – Ben picks the right lane for each subtask.

There the next agents take over: Theo plans and describes the build, Quinn tests and sends the task back with a bug report if something doesn’t fit. On the content board Lena researches, Sina writes the brief and the article, Mo the posts. The feature itself stays in “In progress” until everything is done.

The parent task stays in the picture

When a subtask changes lane or is completed, the parent task shows it in a status comment. Whatever happens within an hour is collected in one comment instead of flooding the task with single updates.

Lanes such as “Done”, “Published” and “Live” complete a task as soon as it arrives. Once all subtasks are done, the feature moves to “Acceptance” by itself and appears in your inbox: you review the result and move it to “Live”.

  • Every move with board and lane, e.g. to Development › Test
  • Completed subtasks with a tick – and a note when one is reopened
  • A final line when all subtasks are done and the task moves on to Acceptance
Video shows the German interface; English videos are coming.

Where people decide

Today Theo writes the design, steps and code proposals as text in the task and prepares the merge request and commit message. Connect GitLab or an MCP server under Settings → AI and he reads issues and files there and – if you allow it, optionally only after your approval – creates issues and comments. Code review, acceptance and approval have no agent – that’s where you decide.

So agents don’t toss a task back and forth forever, each project has an emergency stop and a step limit. The “Activity” view shows who is working on what right now.

How to create the project

In the sidebar: “New project” → “From template” → “Software development”. Optionally give it a name; it is put in front of the board names – say “Shop – Product”, “Shop – Development”, “Shop – Content”.

The first lane of each board holds sample tasks such as “Magic link login”. No agent works there, so nothing starts unasked. Drag a card to “Refinement” and Paula gets going.

  • Project templates come with Pro
  • The full line-up is seven AI teammates – possible with the “AI team 10” package. If your plan doesn’t allow that many, some lanes stay without an agent for now; you can assign them any time in the project’s “AI team”
Video shows the German interface; English videos are coming.

Set up the flow yourself

What the template wires up, you can set up in any project: in the “AI team”, every lane has “Flow across boards”. There you choose which lanes – also in other projects – subtasks go to, where the task moves once they are all done, and whether tasks arriving in the lane are done.

AI agents Content & SEO with AI AI teammates

Why we’re building Todowa

Your tasks belong to you – not to your tools.

Tasks are spread across many tools, and none of them sees the whole picture. We’re building Todowa as an AI-first to-do system that fits into the ones you already use: tasks show up in your Notion database, in Asana, in Todoist and in Google Calendar, and AI matches up what belongs together.

Our goal for Todowa

Frequently asked questions

Does Theo write code straight into the repository?

No. Theo delivers a technical design, steps and code proposals as text and prepares the merge request and commit message. A person builds and merges. With a GitLab connection he reads issues and files and creates issues – write actions optionally only after your approval.

How many AI teammates does the template need?

Seven for the full line-up: Paula, Ben, Theo, Quinn, Lena, Sina and Mo. Pro includes one AI teammate; the other lanes then stay without an agent, and one AI teammate can also cover several lanes. For the full line-up, add the “AI team 10” package (up to 10 AI teammates) to Pro under Settings → Subscription; “AI team 5” covers five.

Can I adapt the template?

Yes. The boards are regular projects: rename, add or delete lanes, swap agents and change their instructions – all in the project and its “AI team”.

More about Todowa

Bring your tasks together.

Create an account, connect your tools, get going – free, add Pro anytime.