TL;DR

Your kanban board is full of ticket titles, and every one of them is a card you had to think of and write. Tekk.coach fills the board for you. Twelve loops read what changed in your code and bring proposals; each one you greenlight becomes a spec with acceptance criteria and a checklist. Your coding agent builds it, and the merged PR moves the card to done. Try it for three days, no setup required.

[Try Tekk.coach →]

How Tekk.coach Does Kanban

Most kanban board tools give you columns and cards. Tekk does too — To Do, In Progress, Done. Three columns. Simple on purpose.

The difference is who writes the cards. Tekk runs twelve loops on your codebase — Security, Reliability, Backend, Payments, Performance, Testing and six more. A loop wakes when your code changes, when Sentry fires, or when part of its area has gone unexamined too long. It reads what changed, follows it to what it touches, works one method from its shelf of skills, and brings at most one proposal. A run that finds nothing records an honest negative instead of inventing work.

You greenlight the proposal or decline it with a reason. Greenlit, it lands in To Do as a spec: what to build, why, the acceptance criteria that say when it's done, and a build-order checklist. Declined, the reason teaches the loops what's noise for your project. You can still write a spec by hand when you know what you want — same board, same acceptance criteria. This is spec driven development applied to every card on your board.

Then the card moves itself. Your coding agent — Claude Code, Codex, Cursor — reads the spec through the Tekk MCP server and marks it in progress when it starts. When the pull request that says Closes TEK-123 merges and the checklist is done, the card moves to Done. That merge is the next change the loops read.

Key Benefits

Cards you didn't have to write. Loops notice the work — the missing ownership check, the retry that charges twice, the query with no index — and bring it to you as a proposal. You spend your time deciding, not drafting.

Codebase-aware specs. The loops don't plan in a vacuum. Each one reads the change in your repo and follows it to what it touches, so a proposal points at the files it actually concerns. Generic advice is not an option.

No ceremony. No sprint planning, no backlog grooming, no custom field configuration, no approval chains. 76% of teams that use Kanban rate it more effective than other methods. Greenlight a proposal, get a spec.

Works with your AI coding tools. If you're building with Claude Code, Codex or Cursor, they work the same board through the Tekk MCP server: list specs, read the acceptance criteria, build, and close the spec with the merge.

Three-day trial. No seat minimums. Connect your repo and the loops start on your next change.

How It Works

  1. Connect your repo. Turn on the loops you want. They start on your next change.

  2. A loop brings a proposal. When your code changes, Sentry fires, or an area goes stale, a loop wakes, reads what changed, and proposes one thing — or records an honest "nothing found."

  3. Greenlight or decline. Greenlit proposals land in To Do as specs. Declined ones teach the loops. Want something no loop raised? Write the spec by hand.

  4. Get a spec your agent can close. What to build, why, acceptance criteria and a build-order checklist. The spec gives you the context that standard kanban metrics like cycle time and throughput can't capture on their own. For teams managing multiple planned features, ai project planning keeps everything structured across the full roadmap.

  5. Merge closes the card. Your coding agent builds the spec via MCP. The PR that says Closes TEK-123 moves the card to Done once its checklist is complete.

Who This Is For

Solo founders and indie builders. You're the architect, the PM, and the developer. Nobody else is watching the auth checks or the payment webhooks. Tekk's loops do, and they bring you what they find as cards you can greenlight.

Small teams building with AI coding agents. If your stack includes Cursor, Claude Code, or Codex, you know the problem: the agent writes code, but someone still has to decide what it builds next. Tekk's loops fill that queue, and each card is a spec your agent can pick up through MCP and close with a merge.

Developers who are done with Jira. You don't need sprint velocity tracking, custom workflows, or approval chains. 56% of Agile teams already use Kanban precisely because it strips away that ceremony. You need to know what to build, why it matters, and what files to touch. Tekk gives you that without the overhead.

Not for: Enterprise teams that need process governance, custom field configurations, approval workflows, or team collaboration features like comments and notifications. Tekk is a board that fills itself from your code, not a project management suite. Teams that need deeper queue management alongside their board should also look at the backlog management tool for prioritizing what gets planned next.

What Is Kanban Board Software?

Kanban is a visual workflow method invented at Toyota in the late 1940s. Taiichi Ohno, then a machine shop manager, studied how supermarkets restocked shelves and adapted that pull-based logic into a card-based system for tracking work through stages — the same logic behind every kanban board tool in use today.

In software, a kanban board is a set of columns (typically To Do, In Progress, Done) and cards (individual tasks). Teams move cards left to right as work progresses. The key practice: WIP (work-in-progress) limits. Cap how many cards can be in any column at once, and you force work to finish before new work starts. Teams that enforce WIP limits improve delivery times by up to 37%. That simple constraint reduces context-switching and surfaces bottlenecks.

Kanban software ranges from dead-simple (Trello) to enterprise-grade (Jira, Businessmap). Most tools now include AI features: auto-prioritization, bottleneck detection, workload balancing, board generation from documents. What almost none of them do: put cards on the board from your actual codebase, and take them off when the work merges. Tekk.coach was built for that gap — loops that propose the work, on a kanban board that stays out of your way.