gustavo-meilus/superpipelines / plugins/superpipelines/skills/brainstorming
brainstorming
VerifiedBrainstorming refines vague or exploratory requests into a validated design document through structured clarifying dialogue and trade-off analysis before any implementation begins. Use when a user's request is under-specified, involves new feature or component design, describes new pipeline behavior, or lacks an existing spec — including when loaded by creating-a-pipeline Phase 0 for exploratory briefs.
Brainstorming — Idea Refinement
The Brainstorming Process
2. CLARIFYING DIALOGUE
- Clarifying questions focus on purpose, constraints, and success criteria.
- Exactly one question is asked per message to avoid overwhelming the user.
- Multiple-choice options (A/B/C) are preferred for faster decision-making. Example: "Which data store fits the scale requirement? A) SQLite (embedded, single-node), B) PostgreSQL (shared, multi-writer), C) Redis (ephemeral cache)."
3. APPROACH & RECOMMENDATION
- Two to three architectural approaches are proposed with explicit trade-offs.
- A specific recommendation leads, with reasoning grounded in project context. Example: "Approach B is recommended because the existing service layer already exposes a PostgreSQL connection pool — adding SQLite would introduce a second persistence mechanism with no clear boundary."
4. DESIGN PRESENTATION (THE GATE)
- The refined design is presented in logical sections: Architecture, Data Flow, Error Handling, Testing.
- Code writing and project scaffolding are prohibited until the user has explicitly approved the presented design sections.
5. SPECIFICATION & REVIEW
- The design document is authored to
docs/specs/. - A Spec Self-Review is performed: placeholders, internal contradictions, and ambiguity are resolved before handoff.
- The user is asked to review the final written spec file. Brainstorming is complete only upon user approval of the spec.
The Visual Companion Protocol
<visual_companion_rules>
- Offering: When upcoming questions are visual in nature (layouts, diagrams), the companion is offered once in a standalone message.
- Decision: For each subsequent question, visual treatment (browser) or text treatment (terminal) is selected based on content type.
- Browser: Used for mockups, wireframes, and architecture diagrams.
- Terminal: Used for requirements, conceptual choices, and tradeoff lists. </visual_companion_rules>
Red Flags — STOP
- "This is too simple to need a design." → STOP. Every project requires a validated design gate.
- "I'll ask 5 questions at once to save time." → STOP. One-question-per-message is mandatory for cognitive clarity.
- "I'll start scaffolding while we brainstorm." → STOP. Design must be approved before implementation begins.
Rationalization Table
<rationalization_table>
| Excuse | Reality |
|---|---|
| "I'll fix the spec later." | A vague spec leads to divergent parallel workers. Fix all ambiguity during the design phase. |
| "Visuals take too many tokens." | Visuals prevent multi-turn misunderstandings that cost far more tokens in rework. |
| "The user already knows what they want." | Brainstorming surfaces implicit assumptions the user hasn't documented. |
| </rationalization_table> |
Reference Files
creating-a-pipeline/SKILL.md— Implementation workflow.sk-4d-method/SKILL.md— Brief deconstruction.sk-claude-code-conventions/SKILL.md— Design patterns.visual-companion.md— Detailed browser usage guide.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |