SuperAPI AI Directory

brainstorm

General & other

View repository

Updated 10-15 17:31

About this skill

Overview

Helps turn ideas into fully developed designs and specifications through natural collaborative dialogue.

Start by understanding the current project context, then ask questions one at a time to refine the idea. When you understand what needs to be built, present the design in small sections (200–300 words), checking each time whether everything looks correct at this stage.

Process

Understanding the idea:

  • First, examine the current state of the project (files, documentation, recent commits)
  • Ask questions one at a time to refine the idea
  • Prefer multiple-choice questions when possible, but open-ended questions are acceptable too
  • Only one question per message; if a topic needs to be explored more deeply, break it into several questions
  • Focus on understanding: goals, constraints, success criteria

Exploring approaches:

  • Propose 2–3 different approaches with their pros and cons
  • Present the options in a conversational manner, with your recommendation and explanation
  • Start with the recommended option and explain why it is preferable

Presenting the design:

  • Once you are confident that you understand what needs to be built, present the design
  • Break it into sections of 200–300 words
  • After each section, ask whether everything looks correct
  • Cover topics: architecture, components, data flow, error handling, and others you consider necessary
  • Be prepared to go back and clarify details if anything is unclear

After the design

Documentation:

  • Write the approved design to docs/plans/YYYY-MM-DD-<topic>-design.md

Key principles

  • One question at a time — don't overload with several questions at once
  • Prefer answer options — they are easier to answer than open-ended questions
  • YAGNI ruthlessly — remove all unnecessary features from designs
  • Explore alternatives — always propose 2–3 approaches before choosing one
  • Incremental validation — present the design piece by piece and validate each step
  • Flexibility — go back and clarify if something doesn't make sense