Practical overview
When it fits
Use bkit when working in Claude Code and you want a defined path from feature or release planning through implementation and quality checks, particularly when work spans multiple sessions.
Who it is for
- Claude Code users seeking a structured workflow for AI-assisted feature development.
- Solo developers and indie builders who want specialist-agent support.
- Team leads planning releases across context-budgeted sprints.
Documented uses
- Plan a feature or multi-feature release and organize work into sprints.
- Coordinate specialist roles for implementation and QA.
- Compare generated code with a design specification and respond to identified gaps.
- Retain project progress and context across Claude Code sessions.
Requirements & limits
Requires Claude Code 2.1.143 or later. The repository is public and licensed under Apache-2.0.
- bkit is a Claude Code plugin and requires that host application at version 2.1.143 or later.
- Parallel team execution is optional and requires enabling Claude Code's experimental agent-teams setting.
- The README notes that with Claude Code 2.1.232 and later, some sprint gates may report “not measured” under default fork behavior; it documents
CLAUDE_CODE_FORK_SUBAGENT=0to restore in-turn results. - The repository identifies the project as JavaScript and lists an Apache-2.0 license.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install bkit and start a single-feature workflow
Install the plugin in Claude Code and invoke its documented PDCA workflow for one feature.
Before you start
- Claude Code 2.1.143 or later
Steps
Install the plugin with
claude plugin install bkit.Describe the feature using
/pdca pm my-feature.
Expected outcome
The documented quick start invokes bkit's PDCA workflow for a feature.
Guide limitations
- The README does not provide an expected completion result for this single-feature command.
- Parallel team execution is optional and requires setting
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Plan and start a multi-feature release
Create a release plan with feature sprints, approve it, and start the first sprint.
Before you start
- Claude Code 2.1.143 or later
Steps
Install the plugin with
claude plugin install bkit.Create a plan with
/sprint master-plan my-release --name "Q2 Launch" --features auth, billing, reports.Review and approve the plan.
Start the first sprint with
/sprint start my-release-s1.
Expected outcome
The documented workflow plans a multi-feature release and starts its first sprint after approval.
Guide limitations
- The README describes sprint planning and starting work but does not establish that a release will complete successfully.
- Parallel team execution is optional and requires setting
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- ww-w-ai/bkit-claude-code · Official homepage title · retained in its source language

