The retro sticky is the sprint ticket

Most teams run the workshop in one tool and the work in another, then spend an hour moving the first into the second. Skip that hour.

Start where you already start

Kanban, retrospective, brainwriting, flowchart, mind map, architecture, five whys.

Monday morning, in order

Open last cycle on a board. Drag what did not finish into the next one. Turn the three new stickies into issues without leaving the canvas. Close the tab.

What the week looks like

Planning

Cycles of two weeks, estimates in points, a burn-down that counts the same set the list shows.

Design

Architecture on the canvas, mermaid in the doc, and one button that hands the whole flow to an agent as a brief.

Retros and decisions

A retro board, decisions written down as pages, and an incident record that links to the decision it changed.

The API is a door, not a demo

API keys and webhooks, so n8n or a script can read and write the workspace, and an MCP server so a coding agent can search it, read a page and file what it found. We integrate rather than clone.