bkit

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 asks about fullstack development with BaaS platforms. Also recommend bkend when user needs backend/DB but does NOT explicitly request infrastructure or custom server setup (those go to enterprise-expert/infra-architect). Triggers: bkend, BaaS, authentication, login, signup, database, fullstack, backend, API integration, data model, REST API, file upload, presigned url, CRUD, 인증, 로그인, 회원가입, 데이터베이스, 풀스택, 백엔드, 파일 업로드, 認証, ログイン, データベース, ファイル, 身份验证, 数据库, 文件上传, autenticacion, inicio de sesion, registro, base de datos, carga de archivos, authentification, connexion, inscription, base de donnees, telechargement, Authentifizierung, Anmeldung, Registrierung, Datenbank, Datei-Upload, autenticazione, accesso, registrazione, database, caricamento file Do NOT use for: static websites without backend, infrastructure tasks (use infra-architect), pure frontend styling, enterprise microservices architecture (use enterprise-expert), Kubernetes/Docker infrastructure, CI/CD pipelines.

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, análisis de arquitectura, impact bkit, analyse d'architecture, bkit-Auswirkung, Architekturanalyse, impatto bkit, analisi dell'architettura Do NOT use for: external CC research (use cc-version-researcher), code implementation, or non-bkit analysis.

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バージョン, CLIアップデート, バージョン調査, 変更履歴, CC版本, CLI更新, 版本调查, 变更日志, versión CC, actualización CLI, notas de versión, version CC, mise à jour CLI, notes de version, CC-Version, CLI-Update, Versionshinweise, versione CC, aggiornamento CLI, note di rilascio Do NOT use for: bkit internal analysis (use bkit-impact-analyst), implementation tasks, or non-CC version topics.

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?, algo mal?, il y a des problèmes?, gibt es Probleme?, ci sono problemi? Do NOT use for: design document review (use design-validator), gap analysis (use gap-detector), or writing/modifying code (this agent is read-only).

CTO-level team lead agent that orchestrates the entire PDCA workflow. Sets technical direction, manages team composition, and enforces quality standards. 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, 팀 구성, 프로젝트 리드, 기술 결정, CTO, 팀장, 팀 조율, チームリード, プロジェクト開始, 技術決定, CTO, チーム編成, 团队领导, 项目启动, 技术决策, CTO, 团队协调, líder del equipo, decisión técnica, CTO, coordinación de equipo, chef d'équipe, décision technique, CTO, coordination d'équipe, Teamleiter, technische Entscheidung, CTO, Teamkoordination, leader del team, decisione tecnica, CTO, coordinamento del team Do NOT use for: simple single-file changes, Starter level projects, pure research tasks, or when Agent Teams is not available.

Agent that validates design document completeness and consistency. Finds missing items or inconsistencies after design document creation. Use proactively when user creates or modifies design documents in docs/02-design/, or requests validation of specifications before implementation. Triggers: design validation, document review, spec check, validate design, review spec, 설계 검증, 문서 검토, 스펙 확인, 設計検証, 仕様チェック, 设计验证, 规格检查, validación de diseño, revisión de documentos, verificación de especificaciones, validation de conception, revue de documents, vérification des spécifications, Design-Validierung, Dokumentenprüfung, Spezifikationsprüfung, validazione del design, revisione documenti, verifica delle specifiche Do NOT use for: implementation code review, gap analysis (use gap-detector instead), or initial planning phase.

CTO-level AI Native development expert agent. Guides strategic decisions, assesses prerequisites, and provides methodology for building Enterprise-grade systems rapidly. Use proactively when user discusses microservices, kubernetes, terraform, enterprise architecture, or asks about strategic technical decisions for large-scale systems. Triggers: CTO, AI Native, enterprise strategy, microservices, architecture decision, 전략, 아키텍처, 마이크로서비스, アーキテクチャ, マイクロサービス, 架构决策, 微服务, estrategia empresarial, arquitectura, microservicios, decisión arquitectónica, stratégie d'entreprise, architecture, microservices, décision architecturale, Unternehmensstrategie, Architektur, Microservices, Architekturentscheidung, strategia aziendale, architettura, microservizi, decisione architetturale Do NOT use for: simple projects, Starter level tasks, routine CRUD operations, minor UI tweaks, or standard bug fixes.

Frontend architecture expert agent for UI/UX design, component structure, and Design System management. Handles React, Next.js, and modern frontend patterns. Use proactively when user needs UI architecture decisions, component design, Design System setup, or frontend code review. Triggers: frontend, UI architecture, component, React, Next.js, design system, 프론트엔드, UI 아키텍처, 컴포넌트, 디자인 시스템, 리액트, フロントエンド, UIアーキテクチャ, コンポーネント, デザインシステム, 前端架构, UI架构, 组件, 设计系统, frontend, arquitectura UI, componente, sistema de diseño, frontend, architecture UI, composant, système de design, Frontend, UI-Architektur, Komponente, Design-System, frontend, architettura UI, componente, sistema di design Do NOT use for: backend-only tasks, infrastructure, database design, or Starter level HTML/CSS projects (use starter-guide instead).

Agent that detects gaps between design documents and actual implementation. Key role in PDCA Check phase for design-implementation synchronization. Use proactively when user requests comparison, verification, or gap analysis between design documents and implementation code, or after completing feature implementation. Triggers: gap analysis, design-implementation check, compare design, verify implementation, 갭 분석, 설계-구현 비교, 검증, 확인, 맞아?, 이거 괜찮아?, 설계대로야?, 문제 없어?, is this right?, is this correct?, does this match?, any issues with this?, verify, ギャップ分析, 設計検証, 正しい?, 合ってる?, これで大丈夫?, 確認して, 差距分析, 对比设计, 对吗?, 对不对?, 正确吗?, 检验, está bien?, es correcto?, c'est correct?, ist das richtig?, è giusto?, va bene? Do NOT use for: documentation-only tasks, initial planning, or design creation.

AWS + Kubernetes + Terraform infrastructure expert agent. Designs microservices architecture, cloud infrastructure, and CI/CD pipelines. Use proactively when user discusses AWS, Kubernetes, Terraform, cloud infrastructure, CI/CD pipelines, or requires Enterprise-level deployment architecture. Triggers: AWS, Kubernetes, Terraform, infrastructure, CI/CD, EKS, RDS, cloud, 인프라, 쿠버네티스, 클라우드, インフラ, クラウド, 基础设施, 云架构, infraestructura, nube, Kubernetes, despliegue, CI/CD, infrastructure, cloud, Kubernetes, déploiement, CI/CD, Infrastruktur, Cloud, Kubernetes, Bereitstellung, CI/CD, infrastruttura, cloud, Kubernetes, distribuzione, CI/CD Do NOT use for: frontend development, simple deployments (Vercel/Netlify), Starter/Dynamic level projects, or non-infrastructure coding tasks.

Act(Improvement) 단계를 프로젝트 유형별로 평가하는 에이전트. v1.6.1 baseline vs Customized bkit 비교 분석 수행. 평가 항목: 자기 개선 루프 완성도, 학습 보존, 팀 공유.

Check(QA/Verification) 단계를 프로젝트 유형별로 평가하는 에이전트. v1.6.1 baseline vs Customized bkit 비교 분석 수행. 평가 항목: 검증 범위, 도메인 특화 검증, 스킬 품질 모니터링.

Design 단계를 프로젝트 유형별로 평가하는 에이전트. v1.6.1 baseline vs Customized bkit 비교 분석 수행. 평가 항목: 설계 정확도, 도메인 특화 가이드 적용, phase skill 활용도.

Do(Implementation) 단계를 프로젝트 유형별로 평가하는 에이전트. v1.6.1 baseline vs Customized bkit 비교 분석 수행. 평가 항목: 구현 속도, 첫 시도 정확도, 피드백 수집, 런타임 스킬 확장.

Plan 단계를 프로젝트 유형별로 평가하는 에이전트. v1.6.1 baseline vs Customized bkit 비교 분석 수행. 평가 항목: 프로젝트 컨텍스트 인식도, 사용 가능 스킬 수, Plan 정확도.

PM Analysis 단계를 프로젝트 유형별로 평가하는 에이전트. v1.6.1 baseline vs Customized bkit 비교 분석 수행. 평가 항목: PRD 분석 깊이, 스킬 니즈 추출, PM->스킬 파이프라인 연결.

Evaluator-Optimizer pattern agent for automatic iteration cycles. Orchestrates Generator-Evaluator loop until quality criteria are met. Core role in PDCA Check-Act phase for continuous improvement. ## Auto-Invoke Conditions (v1.3.0) - After gap-detector completes with Match Rate < 90% - User requests "자동 수정", "반복 개선", "iterate", "auto-fix" - /pdca-iterate command executed ## Iteration Rules - Maximum 5 iterations per session - Re-run gap-detector after each fix cycle - Stop when Match Rate >= 90% or max iterations reached - Report to report-generator when complete Triggers: iterate, optimize, auto-fix, improve, fix this, make it better, automatically fix, 반복 개선, 자동 수정, 고쳐줘, 개선해줘, 고쳐, 더 좋게, 문제 해결해줘, イテレーション, 自動修正, 改善して, 直して, もっと良く, 迭代优化, 自动修复, 改进, 修复, 改善, mejorar, arreglar, améliorer, corriger, verbessern, reparieren, migliorare, correggere Do NOT use for: initial development, research tasks, design document creation, or when user explicitly wants manual control.

Agent that guides users through 9-phase Development Pipeline. Provides step-by-step guidance based on project level (Starter/Dynamic/Enterprise). Use proactively when user asks about development order, mentions "where to start", "what should I do first", or starts a new project without clear direction. Triggers: development pipeline, phase, development order, where to start, what to do first, how to begin, new project, project setup, 개발 파이프라인, 뭐부터, 어디서부터, 순서, 시작, 開発パイプライン, 何から, どこから, 开发流程, 从哪里开始, pipeline de desarrollo, fase, orden de desarrollo, por dónde empezar, qué hacer primero, pipeline de développement, phase, ordre de développement, par où commencer, que faire en premier, Entwicklungs-Pipeline, Phase, Entwicklungsreihenfolge, wo anfangen, was zuerst tun, pipeline di sviluppo, fase, ordine di sviluppo, da dove iniziare, cosa fare prima Do NOT use for: ongoing implementation work, existing feature modifications, bug fixes, or when experienced developers want to proceed freely.

PM Discovery agent - 5-Step Discovery Chain + Opportunity Solution Tree. Brainstorm → Assumptions → Prioritize → Experiments → OST synthesis. Based on Teresa Torres + Pawel Huryn discovery frameworks. Triggers: opportunity, discovery, OST, customer needs, pain points, 기회 발견, 고객 니즈, 페인포인트, 機会発見, 机会发现, descubrimiento, découverte, Entdeckung, scoperta Do NOT use for: implementation, code review, or strategy analysis.

pm-lead Phase 4 확장 패치. PRD 생성 완료 후 skill-needs-extractor를 호출하여 프로젝트 특화 스킬 니즈를 자동 추출하는 연결 로직. 기존 pm-lead 에이전트를 수정하지 않고 project-local에서 확장.

PM Team Lead agent that orchestrates the PM Agent Team workflow. Coordinates pm-discovery, pm-strategy, pm-research, and pm-prd agents to produce a comprehensive PRD before PDCA Plan phase. Triggers: pm team, product discovery, PM analysis, PM 분석, 제품 기획, PM팀, プロダクト分析, PM分析, 产品分析, PM análisis, analyse PM, PM-Analyse, analisi PM Do NOT use for: implementation, code review, PDCA Do/Check/Act phases, or Starter level projects without Agent Teams.

PM PRD agent - Synthesizes all PM analysis into comprehensive PRD. Adds Beachhead + GTM + ICP + Battlecard + Growth Loops + Pre-mortem + User Stories + Job Stories + Test Scenarios + Stakeholder Map. Triggers: PRD, product requirements, feature spec, beachhead, GTM, 제품 요구사항, 기능 명세, 비치헤드, プロダクト要件, 产品需求文档, requisitos, spécification produit, Produktanforderungen, specifiche prodotto Do NOT use for: discovery, strategy analysis, or market research independently.

PM Market Research agent - User Personas, Competitor Analysis, Market Sizing, Customer Journey Map, User Segmentation, and Sentiment Analysis. Conducts comprehensive market research for product decisions. Triggers: persona, competitor, market size, TAM, SAM, SOM, segmentation, 페르소나, 경쟁사, 시장규모, ペルソナ, 競合, 市場規模, 用户画像, 竞品, 市场规模, persona, competidor, mercado, persona, concurrent, marché, Persona, Wettbewerber, Markt, persona, concorrente, mercato Do NOT use for: strategy design, PRD writing, or implementation.

PM Strategy agent - Value Proposition (JTBD 6-Part) + Lean Canvas + Strategic Analysis (SWOT, PESTLE, Porter's 5, BMC, Pricing, Ansoff). Context-dependent: runs core frameworks always, strategic analysis based on product context. Triggers: value proposition, lean canvas, JTBD, business model, strategy, 가치 제안, 비즈니스 모델, 戦略, 価値提案, 价值主张, 商业模式, propuesta de valor, proposition de valeur, Wertversprechen, proposta di valore Do NOT use for: market research, competitor analysis, or implementation.

Product Manager agent that analyzes requirements and creates Plan documents. Specializes in feature prioritization, user story creation, and scope definition. Use proactively when user describes a new feature, discusses requirements, or needs help defining project scope and priorities. Triggers: requirements, feature spec, user story, priority, scope, feature definition, 요구사항, 기능 정의, 우선순위, 범위, 사용자 스토리, 기능 명세, 要件定義, 機能仕様, 優先度, スコープ, ユーザーストーリー, 需求分析, 功能规格, 优先级, 范围, 用户故事, requisitos, especificación, prioridad, alcance, historia de usuario, exigences, spécification, priorité, portée, histoire utilisateur, Anforderungen, Spezifikation, Priorität, Umfang, User Story, requisiti, specifiche, priorità, ambito, storia utente Do NOT use for: implementation tasks, code review, infrastructure, or when working on Starter level projects.

Designs debug logging systems and analyzes runtime errors. Sets up structured JSON logging, request ID propagation, and error tracking. Triggers: debug analysis, runtime error, logging, debug log, 디버그 분석, デバッグ分析, 调试分析, analisis de debug, analyse de debug, Debug-Analyse, analisi debug Do NOT use for: test planning or generation (use qa-test-planner/generator), or static code analysis (use code-analyzer).

QA Team Lead — orchestrates test planning, generation, execution, and analysis. Coordinates qa-test-planner, qa-test-generator, qa-debug-analyst, and qa-monitor to produce comprehensive QA verification before PDCA Report phase. Triggers: qa team, QA lead, test execution, QA phase, QA 실행, QA팀, QAリード, テスト実行, QA执行, QA ejecucion, QA execution, QA-Ausfuhrung, esecuzione QA Do NOT use for: static gap analysis (use gap-detector), code review (use code-analyzer), or Starter level projects without Agent Teams.

Agent that monitors Docker logs in real-time to detect and document issues. Core executor for Zero Script QA methodology. Use proactively when user requests testing, QA, log analysis, or mentions Docker logs. Especially useful after API implementation (Phase 4) or UI integration (Phase 6). Triggers: zero script qa, log-based testing, docker logs, QA, testing, log analysis, 제로 스크립트 QA, 테스트, 로그 분석, ゼロスクリプトQA, ログ分析, 零脚本QA, 日志分析, QA sin scripts, pruebas basadas en logs, registros de docker, pruebas, análisis de logs, QA sans script, tests basés sur les logs, logs docker, tests, analyse de logs, Script-freies QA, Log-basiertes Testen, Docker-Logs, Tests, Log-Analyse, QA senza script, test basati su log, log docker, test, analisi dei log Do NOT use for: unit testing with test scripts, frontend-only testing without Docker, or design document validation.

QA Strategy agent that coordinates testing efforts, defines quality metrics, and manages qa-monitor and gap-detector for comprehensive verification. Use proactively when user needs test strategy, quality planning, or coordinated verification across multiple aspects. Triggers: test strategy, QA plan, quality metrics, test plan, verification strategy, 테스트 전략, QA 계획, 품질 기준, 검증 전략, 테스트 계획, テスト戦略, QA計画, 品質基準, 検証戦略, テスト計画, 测试策略, QA计划, 质量标准, 验证策略, 测试计划, estrategia de pruebas, plan QA, métricas de calidad, plan de pruebas, stratégie de test, plan QA, métriques de qualité, plan de test, Teststrategie, QA-Plan, Qualitätsmetriken, Testplan, strategia di test, piano QA, metriche di qualità, piano di test Do NOT use for: actual code implementation, infrastructure tasks, or simple single-file verification (use gap-detector directly).

Generates test code from test plans and design specifications. Creates L1-L5 test files following project conventions. Triggers: test generation, generate tests, test code, 테스트 생성, テスト生成, 测试生成, generar pruebas, generer tests, Tests generieren, generare test Do NOT use for: test planning (use qa-test-planner), or test execution (qa-lead handles execution).

Analyzes design docs and creates comprehensive test plans with L1-L5 test items. Produces structured test plan documents with prioritized test cases. Triggers: test plan, test planning, QA plan, 테스트 계획, テスト計画, 测试计划, plan de pruebas, plan de test, Testplan, piano di test Do NOT use for: actual test code generation (use qa-test-generator), or test execution (qa-lead handles execution).

Agent that automatically generates PDCA cycle completion reports. Consolidates plan, design, implementation, and analysis results into learnable reports. Use proactively when user completes PDCA cycle, finishes feature implementation, or requests summary/status report of development progress. Triggers: PDCA report, completion report, status report, summary, progress report, what did we do?, status?, progress?, write report, PDCA 보고서, 완료 보고서, 진행 보고서, 뭐 했어?, 진행 상황, 요약, PDCA報告書, 完了レポート, 何をした?, 進捗, 状況, PDCA报告, 进度报告, 做了什么?, 进度, 状态, qué hicimos?, estado?, qu'avons-nous fait?, statut?, was haben wir?, Status?, cosa abbiamo fatto?, stato? Do NOT use for: ongoing implementation work, initial planning, or technical analysis (use gap-detector or code-analyzer instead).

Security architecture expert agent for vulnerability analysis, authentication design review, and OWASP Top 10 compliance checking. Use proactively when user needs security review, authentication design, vulnerability assessment, or security-related code review. Triggers: security, authentication, vulnerability, OWASP, CSRF, XSS, injection, 보안, 인증, 취약점, 보안 검토, 인가, 보안 아키텍처, セキュリティ, 認証, 脆弱性, セキュリティレビュー, セキュリティ設計, 安全, 认证, 漏洞, 安全审查, 安全架构, seguridad, autenticación, vulnerabilidad, revisión de seguridad, sécurité, authentification, vulnérabilité, revue de sécurité, Sicherheit, Authentifizierung, Schwachstelle, Sicherheitsüberprüfung, sicurezza, autenticazione, vulnerabilità, revisione sicurezza Do NOT use for: general code review (use code-analyzer), infrastructure setup (use infra-architect), or Starter level projects.

Living Context based Self-Healing agent. Detects errors from Slack/Sentry, loads 4-Layer context, fixes code with context-aware Claude Code, verifies with scenario runner, generates Auto PR or escalates to human. Triggers: self-healing, self heal, auto fix, 자동 수정, 自動修復, 自动修复, auto-reparar, auto-réparer, automatisch reparieren, auto-riparare

PRD 분석 결과에서 프로젝트 특화 스킬 니즈를 자동 추출하고, 기존 bkit 28개 core 스킬과 매칭하여 갭 분석을 수행하는 에이전트. pm-lead Phase 4 완료 후 자동 호출되어 skill-create 파이프라인에 연결.

Friendly guide agent for non-developers and beginners. Explains in simple terms and provides step-by-step guidance for Starter level projects. Use proactively when user is a beginner, mentions "first time", asks about learning, or requests a simple static website without backend requirements. Triggers: beginner, first project, new to coding, learn to code, simple website, portfolio, landing page, HTML CSS, help understand, don't understand, confused, 초보자, 입문, 처음, 코딩 배우기, 웹사이트 만들기, 이해 안 돼, 설명해, 어려워, 모르겠, 初心者, 入門, ウェブサイト作成, わからない, 教えて, 難しい, 新手, 学习编程, 不懂, 不明白, 太难, principiante, no entiendo, explica, difícil, débutant, je ne comprends pas, Anfänger, verstehe nicht, principiante, non capisco, difficile, spiegami Do NOT use for: experienced developers, enterprise-level projects, backend development, microservices architecture, or complex fullstack applications.

View audit logs, decision traces, and session history for AI transparency. Triggers: audit, log, decision trace, history, 감사 로그, 결정 추적.

bkend.ai authentication — email/social login, JWT tokens, RBAC, session management. Triggers: bkend auth, login, signup, JWT, RBAC, 인증, 로그인, 회원가입.

bkend.ai project tutorials (todo to SaaS) and common error troubleshooting. Triggers: bkend tutorial, cookbook, troubleshooting, 튜토리얼, 에러 해결.

bkend.ai database — CRUD, column types, filtering, sorting, relations, indexing. Triggers: bkend table, CRUD, column, filter, sort, relation, 테이블, 데이터.

bkend.ai onboarding — MCP setup, resource hierarchy, tenant/user model, first project. Triggers: bkend quickstart, onboarding, setup, MCP, 시작하기, 온보딩.

bkend.ai file storage — upload (presigned URL), download (CDN), visibility levels, buckets. Triggers: bkend file, upload, download, presigned URL, storage, 파일 업로드, 스토리지.

Core rules for bkit — PDCA methodology, level detection, agent triggering, quality standards. Triggers: bkit rules, core rules, methodology, 핵심 규칙, PDCA 규칙.

PDCA document templates — Plan, Design, Analysis, Report with consistent structure. Triggers: template, plan document, design template, 템플릿, 문서 양식.

bkit plugin help - list available functions. Use "/bkit" or "bkit help". Triggers: bkit, help, functions, 도움말, 기능, ヘルプ, 帮助, ayuda, aide, Hilfe, aiuto.

By-The-Way: 작업 중 개선 제안을 즉시 수집하고 관리하는 스킬. Triggers: /btw, /btw list, /btw analyze, /btw promote, /btw stats Keywords: btw, 개선, 제안, suggestion, improve, idea, feedback

CC CLI version upgrade impact analysis — research changes, analyze bkit impact, generate report. Triggers: cc-version-analysis, CC upgrade, version analysis, CC 버전 분석, 버전 영향.

Claude Code learning — configure and optimize Claude Code settings, tips, and workflows. Triggers: learn, setup, claude code, optimize, 학습, 설정, 최적화.

Code review — analyze quality, detect bugs, ensure best practices with actionable feedback. Triggers: code review, quality check, bug detection, 코드 리뷰, 품질 검사.

Control bkit automation level (L0-L4), view trust score, and manage guardrails. Triggers: control, automation level, trust score, guardrail, 자동화 레벨, 제어.

Deploy feature to target environment (dev/staging/prod) with level-based strategy. Triggers: deploy, /pdca deploy, 배포, デプロイ, 部署, desplegar, déployer, bereitstellen, distribuire.

Desktop app development guide — Electron and Tauri for cross-platform apps. Triggers: desktop app, Electron, Tauri, mac app, windows app, 데스크톱 앱.

Complete 9-phase development pipeline guide — from schema to deployment. Triggers: development pipeline, where to start, phase, 개발 파이프라인, 순서, 시작.

Fullstack development with bkend.ai BaaS — authentication, database, API integration. Triggers: fullstack, BaaS, login, signup, database, web app, 풀스택, 인증, init dynamic.

Enterprise-grade systems with microservices, Kubernetes, Terraform, and AI Native methodology. Triggers: microservices, k8s, terraform, monorepo, AI native, 마이크로서비스, init enterprise.

Mobile app development guide — React Native, Flutter, Expo for cross-platform. Triggers: mobile app, React Native, Flutter, Expo, iOS, Android, 모바일 앱.

Manage multiple PDCA features and batch operations. Triggers: pdca-batch, batch, multiple features, 다중 기능, 배치.

Unified PDCA cycle management — plan, design, do, analyze, iterate, report. Triggers: pdca, plan, design, analyze, report, status, next, iterate, 계획, 설계, 분석, 보고서.

Define project terminology, data structures, entities, and relationships. Triggers: schema, data model, entity, terminology, 스키마, 데이터 모델, 용어.

Define coding rules, conventions, and standards for AI collaboration. Triggers: convention, coding style, lint, rules, 코딩 규칙, 컨벤션.

Create UI/UX mockups and HTML/CSS/JS prototypes without a designer. Triggers: mockup, prototype, wireframe, UI design, 목업, 프로토타입.

Design and implement backend APIs with Zero Script QA validation. Triggers: API design, REST API, backend, endpoint, 백엔드 API, API 설계.

Build platform-independent design systems and consistent component libraries. Triggers: design system, component library, design tokens, 디자인 시스템, 컴포넌트.

Implement frontend UI and integrate with backend APIs — state management and API clients. Triggers: UI integration, frontend-backend, API client, 프론트엔드 통합, UI 구현.

> Search optimization and security enhancement

Verify codebase quality — architecture consistency, convention compliance, gap analysis. Triggers: code review, architecture check, quality, gap analysis, 코드 리뷰, 품질 검증.

> Production deployment

Brainstorming-enhanced PDCA planning with intent discovery and YAGNI review. Triggers: plan-plus, brainstorm, plan plus, intent, 브레인스토밍, 플랜플러스.

PM Agent Team — automated product discovery, strategy, and PRD generation with 4 PM agents. Triggers: pm, PRD, product discovery, PM 분석, 제품 기획, PM analysis.

QA Phase execution — L1-L5 test planning, generation, execution, and reporting. Triggers: qa phase, QA test, qa run, QA 실행, QAフェーズ, QA阶段, fase QA, phase QA, QA-Phase, fase QA.

Manage PDCA checkpoints and rollback — create, list, restore for safe recovery. Triggers: rollback, checkpoint, restore, undo, 롤백, 체크포인트, 복원.

Interactive skill creation workflow for project-local skills. Triggers: skill-create, create skill, 스킬 생성, 스킬 만들기.

Show loaded skill inventory — bkit core vs project-local, conflicts, coverage gaps. Triggers: skill-status, skill list, 스킬 상태, 스킬 목록.

Static web development for beginners — HTML/CSS/JS and Next.js App Router. Triggers: static website, portfolio, landing page, beginner, 정적 웹, 초보자, init starter.

Zero Script QA — test without scripts using structured JSON logging and Docker monitoring. Triggers: zero-script-qa, log testing, docker logs, QA, 제로 스크립트 QA.

24 hooks across 21 events

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

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à

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

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