Concept

Capture an idea as a single bead labeled concept. This is the lightest unit of planning — one bead, no sub-tasks, no implementation plan. Just the idea crystallized.

Input

Either:

• A topic/idea from the user's message (e.g., "think about adding rate limiting")
• An explicit request to explore something

Process

1. Explore if needed. If the concept relates to existing code, read relevant files to ground the idea in reality. Keep exploration brief — this is thinking, not implementation planning.

2. Create one bead:

   bd create \
     --title="<concise concept title>" \
     --type=task \
     --priority=2 \
     --labels=concept \
     --description="<what the idea is and why it matters>" \
     --design="<technical thinking, trade-offs, options considered>"
   

3. Report to user: Share the concept summary and bead ID. Keep it conversational — this is a thinking exercise, not a spec review.