Nudgile

Nudgile is built around a simple premise: a retrospective board should be a shared surface for humans and AI agents alike, not two disconnected tools. The board itself stays deliberately analog — columns, post-it notes, votes, a structured discussion phase, and first-class action items with owners and due dates. What is new is the seam between that board and the rest of your engineering workflow. A single personal access token unlocks three transports: the web UI, an MCP server endpoint that plugs into AI editors such as Claude Code and Cursor, and a `nudgile` CLI for shells, CI jobs, and GitHub Actions. Scopes are enforced server-side and tokens are revocable per laptop, per CI job, or per agent, with automatic revocation if a token leaks into a public repository.

Beyond individual boards, Nudgile adds an AI retrospective coach that reads across a team's history rather than a single meeting. It surfaces recurring friction themes that keep reappearing sprint after sprint, sentiment trends over time, and stale action items that nobody closed and nobody mentioned. The intent is to let a team start the next sprint with the signal already collected instead of re-deriving it from memory in the room. Per-team insights are available on the free plan; cross-team rollups and organisation-wide pattern detection sit behind the Business tier.

Nudgile ships with five forkable retrospective templates — Classic (went well / didn't / try next), Sailboat, Mad-Sad-Glad, Starfish, and the 4 L's — each with a defined column set, phase order, and default voting budget. Action items sync out to Jira and Linear, and the board supports phase-driven anonymity so notes stay unattributed during brainstorming and become attributed once discussion opens.