Loading...
Loading...
Found 7 Skills
Use when receiving code review feedback, processing PR comments, or needing to evaluate suggestions before implementing - requires technical verification not blind agreement
Use this when receiving code review feedback, before implementing suggestions, especially when feedback seems unclear or technically problematic - requires technical rigor and verification, not protocol execution or blind implementation
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Receive and process code review feedback effectively. Applies suggestions, addresses comments, and iterates on implementation improvements.
Plan Plus — Brainstorming-Enhanced PDCA Planning. Combines intent discovery from brainstorming methodology with bkit PDCA's structured planning. Produces higher-quality Plan documents by exploring user intent, comparing alternatives, and applying YAGNI review before document generation. Use proactively when user mentions planning with brainstorming, intent discovery, exploring alternatives, or wants a more thorough planning process. Triggers: plan-plus, plan plus, brainstorming plan, enhanced plan, deep plan, 플랜 플러스, 브레인스토밍, 기획, 의도 탐색, 대안 탐색, プランプラス, ブレインストーミング, 企画, 意図探索, 计划加强, 头脑风暴, 深度规划, 意图探索, plan mejorado, lluvia de ideas, planificación profunda, plan amélioré, remue-méninges, planification approfondie, erweiterter Plan, Brainstorming, vertiefte Planung, piano migliorato, brainstorming, pianificazione approfondita Do NOT use for: simple tasks that don't need planning, code-only changes.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation