From bdk
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.
npx claudepluginhub broneq/bdk --plugin bdkThis skill uses the workspace's default tool permissions.
> Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Relies on BDK foundation (STARTUP_INSTRUCTIONS.md) for project context and MCP tool preference.
Transform vague ideas into concrete, validated designs through structured dialogue.
Core Principle: Understand → Explore → Design → Validate → Document
CLAUDE.md and relevant rulesGATE: Complete context analysis before Phase 2.
AskUserQuestion with 2-4 options when possibleGATE: Clear success criteria before Phase 3.
GATE: User selects approach before Phase 4.
GATE: All sections user-approved before Phase 5.
GATE: No unresolved gaps before Phase 6.
.bdk/brainstorming/YYYY-MM-DD-HHMM-<topic>-design.mdSee design-template for full document structure.
# [Feature Name] Design
**Date**: YYYY-MM-DD
**Status**: Draft | Approved | Implemented
> **Implementation Note**: To implement this design, use `/bdk:create-plan` to generate a detailed implementation plan.
## Problem Statement
[2-3 sentences]
## Selected Solution
### Architecture Overview
[high-level description]
### Key Components
[list of components with responsibilities]
### Data Flow
[step-by-step flow]
### Error Handling
[error scenarios and responses]
## Testing Strategy
[unit, integration, edge cases]
GATE: Design document exists, matches approved content.
/bdk:create-plan