Research-Backed Brainstorming Command

Launch the Brainstorming AI skill to turn ideas into validated designs through:

• Research-backed exploration of product ideas
• Architecture and system design decisions
• Tech stack comparisons with current best practices
• Feature design with market/competitor awareness
• Engineering patterns validated against production experiences

How it Works

1. Invoke the skill: Launches lde:brainstorming
2. Domain routing: Routes to product or engineering brainstorming path
3. Adaptive questioning: Gathers context through structured questions
4. Deep research pass: Composes a scoped brief from your answers and runs it through the deep-research harness (fan-out web search, source-fetching, adversarial fact-checking, cited synthesis)
5. Critical orchestration: Interrogates the returned report — tests evidence, resolves conflicts, fills gaps with a focused follow-up
6. Present approaches: 2-3 research-backed options with recommendations
7. Incremental validation: Design presented in sections for feedback
8. Design document: Saves validated design with sources to local scratch (.local/brainstorms/, gitignored)

Usage

/lde:brainstorming [optional: idea to explore]

Examples

# Without arguments - will ask what you want to explore
/lde:brainstorming

# Product ideas
/lde:brainstorming add real-time notifications feature
/lde:brainstorming redesign onboarding flow for better conversion
/lde:brainstorming freemium vs subscription pricing model

# Engineering decisions
/lde:brainstorming migrate from REST to GraphQL
/lde:brainstorming choose between Redis and Memcached for caching
/lde:brainstorming implement event-driven architecture
/lde:brainstorming monorepo vs polyrepo for microservices

What Gets Created

A structured design document saved to .local/brainstorms/<topic>/YYYY-MM-DD-design.md (local-only scratch, gitignored — promote to docs/plans/ if the brainstorm matures into a shippable decision):

• Context: Problem, constraints, success criteria
• Research Findings: State-of-the-art insights with sources
• Decision: Chosen approach with rationale
• Rejected Alternatives: What was considered and why not
• Design: Detailed design by section
• Next Steps: Concrete action items

Brainstorming Options

When invoked without arguments, you'll see:

1. Product idea - Feature, user experience, market fit, product strategy
2. Engineering decision - Architecture, system design, tech stack, patterns
3. Both/Unclear - Not sure yet, help me figure it out

Each path has tailored research queries and design considerations.

Research Capabilities

The skill runs a deep-research pass before presenting options — a single scoped brief that the harness fans out internally across these angles:

Codebase awareness ("existing foundations") comes from the skill's project-grounding step — deep-research covers the web, not your repo.

Key Benefits

✅ Research-first: Current data before opinions - no outdated advice ✅ Adaptive intake: Only asks about genuine gaps in context ✅ Deep research harness: Delegates to deep-research — parallel web search, source-fetching, and adversarial fact-checking ✅ Verified, not just gathered: Claims are adversarially checked before they shape the design ✅ Codebase-aware: Considers existing patterns and constraints from project grounding ✅ Source citations: All recommendations backed by verified research ✅ Incremental validation: Check direction at each design section ✅ Local-only by default: Design documents stay in .local/brainstorms/ (gitignored); promote to docs/plans/ only when a brainstorm matures into a shippable decision

Skill Invocation

This command invokes the lde:brainstorming skill using the Skill tool.