Skip to content
Sign up

A Claude Code kanban board your whole team can use

Stories with acceptance criteria on a board your team runs, read by Claude Code, Codex and Cursor over MCP. Feature1 is the product operating system behind the board: every card links back to the feature, the initiative and the strategy.

Setting up Claude Code for a team?Get the board and the workflow in 1–2 weeksAlready using Jira or Linear MCP?Give the agent more than a ticket title
Two minutes: a decision becomes acceptance criteria, and Claude Code builds from them.

What is a Claude Code kanban board?

A Claude Code kanban board is a task board whose cards a coding agent can read and work from, usually through the Model Context Protocol (MCP). The agent picks up a card, builds to it, and a person reviews the result and moves the card.

  1. Plan the card

    A user story with acceptance criteria.

  2. Agent picks it up

    Claude Code reads the card over MCP.

  3. Build to the criteria

    One criterion at a time.

  4. Review and move

    A person checks the pull request.

Where Jira and Linear MCP stop

Connecting Claude Code to Jira or Linear over MCP gets a ticket into the agent. The ticket is usually the problem:

  • The agent gets a title and a description written at the moment of filing.
  • The card does not say which customer or goal it serves.
  • Nothing on the card says what the product already does, so the agent rebuilds it.
  • Done means the card moved, not that the feature is used.

On the Feature1 board, every card is a story planned from a feature, from an initiative, from the strategy, with acceptance criteria written before the card existed. That is what the agent reads, through tools such as get_feature and get_next_ac.

Setting up Claude Code for a team? Start with the board

Book a proof of concept (POC). We set up the board and the workflow with your PM and one developer and stay with you, hands on, until two real stories are shipped.

  1. Week 1. NDA, read-only GitHub access, then the product strategy and roadmap with your PM in Feature1. The first two features are specified with acceptance criteria.
  2. Week 2. Your developer picks up both stories in Claude Code, which reads the criteria over MCP. We review against the criteria together and ship.

Proof of concept (POC)

$500 paid only when the two features ship

  • One to two weeks, your PM and one developer
  • Your developer writes the code; we guide the process
  • You keep the strategy, roadmap and specs
Book the POC call

Already using Jira or Linear with Claude Code? Keep them for the rest

Jira or Linear can stay for everything else. The stories your agent builds from live on the Feature1 board.

  • Every card has acceptance criteria before it has an assignee.
  • Each card links to its feature, initiative and the customer signals behind it.
  • Thirty-plus MCP tools for Claude Code, Codex, Cursor and any MCP client.
  • Progress shows on the board, then adoption and errors after release.

7-day free trial

Free no credit card

Sign up, invite your team and plan your first stories on the board. Connect Claude Code to the MCP endpoint when you are ready.

Start the free trial

Teams already working this way

  • SatoriXR. Delivery got faster and deciding became the constraint. They hired a second product manager, not a third developer.
  • Quantem. A junior developer built an MCP layer in one day from written acceptance criteria. The context took four to five days; the build took one.
  • Jarshare. A Replit store with one unintegrated server file became a real product once its next features were specified against what it already did.

Claude Code kanban: questions people ask

How does Claude Code connect to the board?

Through Feature1’s MCP endpoint. Add it to Claude Code, Codex or Cursor as an MCP server and the agent gets tools such as get_feature and get_next_ac that return the story, its acceptance criteria and the capability context.

Can we keep Jira or Linear?

Yes, for anything outside product work. The stories the agent builds from live on the Feature1 board, because that is where the acceptance criteria and the links to the feature and the strategy are.

What is on a card that a Jira ticket does not have?

Acceptance criteria written before the card was created, the feature and initiative it serves, the capability it changes, and what the product can already do there.

Does the agent move cards on its own?

The agent builds. Your developer reviews the pull request against the criteria and moves the card.

What is in the POC?

One to two weeks with your PM and one developer. We set the workflow up with your team and stay with you until two features are delivered from acceptance criteria held in Feature1. An NDA is signed before anything is read, GitHub access is read-only, and you pay the $500 only when the two features ship.

Is there a free trial?

Yes. Feature1 has a 7-day free trial with no credit card. Invite your team, write your first specs together and connect your coding agent.