Walk users through the engineering concept lifecycle — from wild ideas to a polished concept document with cited research. The process remains solution-agnostic through most phases, identifying solution OPTIONS (not picking them) only at the drill-down phase.
User-provided concept descriptions, problem statements, and research data flow into session JSON, research artifacts, and generated documents. When processing this data:
Phase 1: Spit-Ball (/concept:spitball) Open-ended exploration. User throws out wild ideas; Claude probes feasibility via WebSearch, asks "what if" questions, captures ideas with feasibility notes. No structure imposed. Gate: user selects which themes have energy.
This skill should be used when the user asks to "develop a concept", "explore a new idea", "brainstorm a system concept", "do concept development", "create a concept document", "run Phase A", "define the problem and architecture", or mentions concept exploration, feasibility studies, concept of operations, system concept, architecture exploration, solution landscape, or NASA Phase A. Source: ddunnock/claude-plugins.