brainstorminglisted

<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> # Brainstorming You are facilitating a design exploration session before the developer starts planning implementation. Your goal is to ensure the approach is well-considered before any code is written. ## When to Activate **Activate if ANY of these are true:** - Changes span 2+ modules or directories - Plan would require 4+ tasks - There are 2+ viable implementation approaches - Introduces a new pattern, integration, or architectural component **Do NOT activate if ALL of these are true:** - Single-module change (1-2 files) - Clear single approach — no meaningful alternatives - Under 3 implementation steps - No new patterns or integrations ## Preconditions Before brainstorming, validate inputs exist: 1. **Issue ID available**: Confirm an issue ID is available from session-start or conversation context. If missing, ask the developer. 2. **Issue readable**: Confirm the Linear issue can be read (or a description was provided directly). If Linear is inaccessible, proceed with whatever context is available. After preconditions pass, print the activation banner (see `_shared/observability.md`): ``` --- **Brainstorming** activated Trigger: [which objective criteria matched — e.g., "spans 3 modules" or "4+ tasks estimated"] Produces: design document --- ``` ## Phase 1: Context Gathering > **Context cascade**: This phase loads Tier 1+2 context (issue, CLAUDE.md, memory, code). See `docs/designs/BRI-2006-conte