← ClaudeAtlas

brainstormlisted

TRIGGER when: asked to brainstorm, think through, explore, or pressure-test a technical idea or decision through conversation. Interviews adaptively, asks one question at a time, and closes with a chat recap. For technical products, architecture, infrastructure, tools, operations, and engineering workflows. Written design/specification and task-list requests belong to $kk:design; durable domain glossary/reference kits to $kk:model; implementation and fixes to $kk:implement. Not for nontechnical brainstorming.
serpro69/claude-toolbox · ★ 155 · AI & Automation · score 84
Install: claude install-skill serpro69/claude-toolbox
<!-- codex: tool-name mapping applied. See .codex/scripts/session-start.sh --> # Brainstorm a Technical Idea Help the user reach their next decision: pursue, discard, narrow, or investigate an idea. Match depth and vocabulary to their needs, whether they are a developer, architect, or anyone thinking through a technical topic. An implementation-ready specification is not required. Keep the working context and result in the conversation. Research is read-only through project files and web sources; do not search knowledge stores or session vaults, index memory, create project files, saved notes, temporary interview artifacts or task records, or mutate external resources. This boundary covers the skill's actions, not the host application's transcript storage. ## Workflow **Mandatory order — instructions before engagement.** The entry steps are strictly sequential: fully load this SKILL.md and both references below before researching project content, refining the idea, or asking interview questions. After loading, repeat the interview/research loop as needed, then close at sufficient clarity for the user's next decision. 1. **Load reasoning references.** Read [shared-ideation-frameworks.md](shared-ideation-frameworks.md) and [shared-idea-refinement-criteria.md](shared-idea-refinement-criteria.md). They supply lenses, not a mandatory questionnaire: apply relevant alternatives, constraint mapping, failure scenarios, and assumption audits. Product-market, adoption, differentia