Built for Claude Code · Kanban for AI-driven development

Same AI. Completely different results.

Three commands move the work: /breakdown, /doing, /review. 60+ skills attach to every card and load before a line of code is written. Plus a harness that blocks destructive commands.

60+ skills shipped · 50+ harness rules

The board

A board built around context.

Columns, cards, real-time sync, and a first-class Skills system. Every card carries the context an AI needs to pick it up and execute without a briefing.

Skills

Standards that travel with the work.

A skill is a reusable brief attached to the card. It can hold an architectural pattern, a review standard, or a security rule. Your AI reads every attached skill before touching a single line of code.

  • One skill, attached to many cards. The standard travels with the work.
  • /breakdown automatically picks the right skills.
  • /doing loads every attached skill into the agent before it executes.
  • Three layers: shipped defaults · team policy · personal overrides.
A work item showing the attached skills that travel with it.
How a card moves

Intent in, execution out

01/breakdown
Turn intent into a card with skills attached.
“Migrate our Stripe customer IDs to Polar with no downtime.”
polarbackend-designdatabase-migrations
Draft written · acceptance criteria set · skills attached.
KO-0008 · ready
02/doing
Read the brief. Use the skills.
Loaded 3 skills · 12 docs · 4 prior decisions.
Migration plan drafted in 38s.
--auto walks the Ready column without pausing.
KO-0008 · in progress
03/review
Self-check before handoff.
AC checked · tests run · diff read.
Missing rollback step. Sent back with suggestions.
--auto reviews every Reviewing item in one pass.
KO-0008 · back to in progress
Watch the walkthrough

See Kontekstboard in action.

claude-code · ~/work/example
Bash(rm -rf ~/work/example/.DS_Store ~/work/example/cli/.DS_Store ~/work/example…)
Error: PreToolUse:Bash hook error: [kontekst harness check]:
Kontekstboard Harness [HIGH] Recursive forced delete
Why this was skipped:
Recursive forced deletion permanently removes files with no recovery path. A wrong path can cause serious data loss.
What to do instead:
List what would be deleted first (ls -la <path>), then delete specific files. Consider moving to a temp dir before confirming.
Skipped:
rm -rf ~/work/example/.DS_Store ~/work/example/cli/.DS_Store…
Listed 1 directory (ctrl+o to expand)
Contents confirmed. Moving to a temp dir instead of recursive delete, so it's reversible:
Built on PreToolUse

Guardrails, not handcuffs.

Harness intercepts every Claude Code tool call before it runs. When a dangerous command matches a rule, the agent gets a plain-English explanation and steers around it. No hard crash. No lost work.

PreToolUse hook
Fires on every bash, write, and edit.
50+ rules
Destructive commands, credential exposure, force-push, cloud wipe.
Three layers
System, Enterprise/Team, and Personal. All synced to Claude Code.
Why Kontekst·board

Same AI. Completely different results.

Vibe codingKontekst·board
PlanningDescribe it again every session.Run /breakdown. The AI writes the item for you.
ContextAI starts fresh every time.Skills attached to the item, loaded automatically.
ConsistencyDifferent patterns on every run.Same standards enforced across every execution.
DriftHope the AI stays on track./doing picks up with full context.
Code reviewSurprised by what the AI produces.AI follows your review standards before writing a line.
OnboardingBrief the AI every time someone joins.Skills are shared. Context travels with the board.
Install

Ready when you are.

Install the CLI on macOS, Linux, or Windows. Sign in once your waitlist slot opens.

zsh
$curl -fsSL https://kontekstboard.com/install.sh | sh

Plan and execute as intended.

Join the waitlist for early access. We open slots in batches. Bring your team when it's your turn.

Join the waitlist