Enforces a PDCA (Plan-Do-Check-Act) quality gate workflow for AI-generated code, verifying implementation against design specs with automated agents, audit trails, and level-based trust controls. Includes fullstack project scaffolding, sprint management, Zero Script QA via structured logs, and deployment pipelines.
bkit plugin help - Show all available bkit functions. Workaround for skills autocomplete issue. Use "/bkit" or just type "bkit help" to see available functions list. Triggers: bkit, bkit help, bkit functions, show bkit commands, 도움말, 기능 목록, ヘルプ, 機能一覧, 帮助, 功能列表, ayuda, lista de funciones, aide, liste des fonctions, Hilfe, Funktionsliste, aiuto, elenco funzioni
Install bkit output styles to your project or user directory. Copies output style files from bkit plugin to the appropriate location. Triggers: output style setup, install output style, setup style, 아웃풋 스타일 설치, 스타일 설정, 出力スタイル設定, 输出样式安装, instalar estilo, installer style, Stil installieren, installare stile
bkend.ai BaaS platform expert agent. Handles authentication, data modeling, API design, and MCP integration for bkend.ai projects. Use proactively when user mentions login, signup, authentication, database operations, or fullstack development with a BaaS platform. Triggers: bkend, BaaS, authentication, login, signup, database, fullstack, backend, API integration, data model, REST API, file upload, presigned url, CRUD, 인증, 로그인, 회원가입, 데이터베이스, 풀스택, 백엔드, 파일 업로드, 認証, 数据库, autenticacion, authentification, Authentifizierung, autenticazione
bkit plugin architecture and impact analysis specialist agent. Deeply understands bkit's codebase, philosophy, and component architecture to assess how external changes (CC version upgrades) affect bkit. Use proactively when CC version changes need to be mapped to bkit impact, or when bkit architecture analysis is required for upgrade planning. Triggers: bkit impact, architecture analysis, plugin analysis, impact assessment, bkit 영향, 아키텍처 분석, 플러그인 분석, 영향 평가, bkit影響, bkit影响, impacto bkit, impact bkit, bkit-Auswirkung, impatto bkit
Claude Code CLI version change researcher agent. Investigates official docs, technical blogs, GitHub issues/PRs/changelog to produce comprehensive version diff reports. Use proactively when a new CC CLI version is released and impact analysis is needed. Triggers: CC version, CLI update, version research, changelog, release notes, CC 버전, CLI 업데이트, 버전 조사, 변경사항, 릴리스 노트, CCバージョン, CC版本, versión CC, version CC, CC-Version, versione CC
Agent that analyzes code quality and architecture compliance. Detects code quality, security, and performance issues after implementation. Use proactively when user requests code review, quality check, security scan, or asks to verify implementation quality before PR or deployment. Triggers: code analysis, quality check, security scan, code review, architecture check, any issues?, any problems?, something wrong?, something off?, analyze, 코드 분석, 품질 검사, 보안 스캔, 이상해, 뭔가 이상해, 괜찮아 보여?, 품질, コード分析, 代码分析, hay problemas?, il y a des problèmes?, gibt es Probleme?, ci sono problemi?
CTO-level team lead agent that orchestrates the entire PDCA workflow. Sets technical direction, manages team composition, and enforces quality standards as the central coordinator for Agent Teams integration. Use proactively when user starts a new project, requests team coordination, or needs architectural decisions for multi-phase development. Triggers: team, project lead, architecture decision, CTO, tech lead, team coordination, 팀 구성, 프로젝트 리드, 기술 결정, 팀장, 팀 조율, チームリード, 团队协调, coordinación de equipo, chef d'équipe, Teamleiter, coordinamento del team
Live PDCA dashboard ticking every 30s — reads pdca-status.json + token-ledger.ndjson tail, renders fixed-width panel via CC /loop. Triggers: pdca watch, live dashboard, watch progress, 실시간 대시보드, ライブダッシュボード, 实时仪表板, panel en vivo, tableau de bord.
PDCA + Sprint document templates — Plan, Design, Analysis, Report for individual features plus templates/sprint/{master-plan, prd, plan, design, iterate, qa, report}.template.md for sprint-level documents (v2.1.13). Triggers: template, plan document, design template, 템플릿, 문서 양식.
By-The-Way: 작업 중 개선 제안을 즉시 수집하고 관리하는 스킬. Triggers: /btw, /btw list, /btw analyze, /btw promote, /btw stats Keywords: btw, 개선, 제안, suggestion, improve, idea, feedback
bkit plugin help - list available functions including /pdca (9-phase feature cycle), /sprint (8-phase feature container, v2.1.13), /control (Trust L0-L4 + SPRINT_AUTORUN_SCOPE), /bkit-explore, and 40+ specialized skills. Use "/bkit" or "bkit help". Triggers: bkit, help, functions, 도움말, 기능, ヘルプ, 帮助, ayuda, aide, Hilfe, aiuto.
View audit logs, decision traces, and session history for AI transparency. ACTION_TYPES (19 entries) include PDCA events (phase_transition, gate_passed/failed, agent_spawned/completed/failed, rollback_executed, destructive_blocked) and Sprint events (sprint_paused, sprint_resumed, master_plan_created — v2.1.13). Triggers: audit, log, decision trace, history, 감사 로그, 결정 추적.
CTO-perspective style optimized for Enterprise-level development. Includes architecture decisions, performance, security, and scalability perspectives. Triggers: enterprise, CTO, architecture, microservices, scalability, performance, 엔터프라이즈, 아키텍처, 마이크로서비스, 확장성, 성능, エンタープライズ, アーキテクチャ, マイクロサービス, スケーラビリティ, 企业, 架构, 微服务, 可扩展性, 性能, empresa, arquitectura, microservicios, escalabilidad, rendimiento, entreprise, architecture, microservices, évolutivité, performance, Unternehmen, Architektur, Microservices, Skalierbarkeit, Leistung, impresa, architettura, microservizi, scalabilità, prestazioni
Educational style for learning bkit 9-Phase Pipeline and PDCA while developing. Provides learning points after each task. Triggers: learn, beginner, tutorial, education, guide, explain, 배우기, 초보, 튜토리얼, 교육, 가이드, 설명, 学ぶ, 初心者, チュートリアル, 教育, ガイド, 学习, 初学者, 教程, 教育, 指南, aprender, principiante, tutorial, educación, guía, apprendre, débutant, tutoriel, éducation, guide, lernen, Anfänger, Tutorial, Bildung, Anleitung, imparare, principiante, tutorial, educazione, guida
Combined PDCA workflow guide + CTO Enterprise perspective style. Tracks PDCA progress with status badges while providing architecture decisions, performance, security, and scalability analysis. Triggers: PDCA, enterprise, CTO, architecture, workflow, checklist, gap analysis, 워크플로우, 아키텍처, 체크리스트, 확장성, 성능, ワークフロー, アーキテクチャ, チェックリスト, スケーラビリティ, 工作流程, 架构, 检查清单, 可扩展性, 性能, flujo de trabajo, arquitectura, lista de verificación, escalabilidad, flux de travail, architecture, liste de contrôle, évolutivité, Arbeitsablauf, Architektur, Checkliste, Skalierbarkeit, flusso di lavoro, architettura, lista di controllo, scalabilità
PDCA workflow guide optimized style. Automatically displays checklists and progress for each phase. Best used with the bkit plugin for optimal results. Triggers: PDCA, workflow, checklist, progress, gap analysis, phase, 워크플로우, 체크리스트, 진행, 단계, ワークフロー, チェックリスト, 進捗, 工作流程, 检查清单, 进度, flujo de trabajo, lista de verificación, flux de travail, liste de contrôle, Arbeitsablauf, Checkliste, flusso di lavoro, lista di controllo
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Executes bash commands
Executes bash commands
Hook triggers when Bash tool is used
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
The only Claude Code plugin that verifies AI-generated code against its own design specs.
Three commands. Anyone — even someone vibe-coding for the first time — can ship robust, production-quality software. bkit turns Claude Code into a Context Engineering system: 44 skills, 34 specialist agents, 11 quality gates, and a memory that survives across sessions deliver the right context to the AI at the right moment, so you don't have to know prompts, commands, or PDCA to get high-quality results.
Requirement: bkit requires Claude Code v2.1.143 or later (the strict plugin-manifest path recognizes the official
displayNamefield only from v2.1.143). On older Claude Code you will seeValidation errors: Unrecognized key: "displayName"duringclaude plugin install. Runnpm install -g @anthropic-ai/claude-code@latestto upgrade, or seedocs/06-guide/cc-compatibility.guide.md.
| You are… | bkit gives you |
|---|---|
| 🌱 First-time vibe coder — you describe what you want and AI codes for you, but you don't yet know how to tell if the result is correct | A safety net. AI proposes, bkit measures the result against its own design spec, and auto-repairs the gap when it drifts. You can ship without becoming a senior engineer first. |
| 👤 Solo developer / indie builder | A team-in-a-box. /pdca team spawns 4–6 specialist agents in parallel — frontend, backend, QA, security — orchestrated by an AI tech lead. |
| 👥 Team lead planning a release | Sprint Management. /sprint master-plan splits your release into context-budgeted sprints so a single Claude Code session can finish each one without running out of memory, and resumes after any session interruption. |
| 🌐 Non-English speaker | 8-language auto-detection. Type "로그인 기능 만들어줘" or "作成新功能" and bkit picks the right command for you. |
The promise: anyone — including non-developers — can build robust, production-quality software by using bkit. bkit replaces the senior engineer's intuition with a workflow.
| Without bkit | With bkit |
|---|---|
| AI gives you plausible code; you have no way to know if it really matches what you asked for | gap-detector measures match rate between your design spec and the generated code. Below 90 % → bkit auto-repairs (up to 5 cycles). |
| You only spot drift at PR review — by then the cleanup is expensive | 11 Quality Gates halt the workflow before drift compounds (match rate, critical issues, convention, test coverage, security, dataFlow integrity, …) |
| Long projects exceed Claude Code's session window and you lose context | bkit splits the project into context-budgeted Sprints (≤ 75 K tokens each); memory + Task Management lets any session resume where the last one stopped |
| You don't know which command, agent, or skill to use | 8-language auto-trigger + intent-router pick the right skill / agent automatically. You just describe what you want. |
| AI ships code, you ship hope; nobody documents what changed | Docs = Code philosophy: every feature produces a PRD + plan + design + analysis + completion report. The history is the audit trail. |
This is the canonical workflow when you use bkit. You describe a release; bkit handles the rest.
flowchart TB
You(["You: describe the release"])
You --> S1["Step 1<br/>/sprint master-plan my-release<br/>--features auth, billing, reports"]
S1 --> Auto1["bkit auto-action<br/>• sprint-master-planner agent investigates code + web in depth<br/>• Splits features into context-budgeted Sprints (≤ 75K tokens each)<br/>• Writes the master plan with Context Anchor"]
Auto1 --> S2["Step 2<br/>You approve the plan"]
S2 --> Auto2["bkit auto-action<br/>• Every sprint registered in Task Management<br/>• Memory saved — survives session clear"]
Auto2 --> S3["Step 3<br/>/sprint start sprint-1"]
S3 --> Auto3["bkit auto-action — full PDCA per feature:<br/>PRD/Plan → Design → Do → Iterate (target 100%, gated) →<br/>QA (gated) → Report. /pdca pm, /pdca team, /pdca qa as needed."]
Auto3 --> Gate{"All quality<br/>gates pass?"}
Gate -- "no, auto-fix" --> Repair["pdca-iterator self-repair<br/>(max 5 cycles)"]
Repair --> Gate
Gate -- "yes" --> Done(["Release-ready code + docs"])
Ctrl["Step 4<br/>/control level 0..4"] -.->|"set how much<br/>runs unattended"| Auto1
Ctrl -.->|"applies"| Auto3
npx claudepluginhub popup-studio-ai/bkit-claude-code --plugin bkitClaude Code 초보자를 위한 한글 학습 가이드 및 설정 템플릿
Use Claude Code As Is - native plugin leveraging built-in architecture
Helder's personal SDLC toolbelt for AI coding agents — from spec to ship. Bundles the tracer-bullet workflow alongside TDD, code review, audits, and shipping skills.
PRD-driven AI dev team control plane for Claude Code — agents, skills, and a GitHub-first sprint workflow.
Code transformation: Dev SDLC orchestrator (code-shipping pipeline), plan, assert, audit, review, test, refactor, debug, for-sure. Hosts engineering agents.
AI-powered development workflow automation - Phase-based planning, implementation orchestration, preflight code quality checks with security scanning, ship-it workflow, and development principles generator for CLAUDE.md
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards