brainstorming
Brainstorming Ideas Into Designs
Transform ideas into fully formed designs through structured, collaborative dialogue. No code gets written until there's an approved design.
Hard Gate
Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. A todo app, a config change, a single utility function — all go through this process. "Simple" projects are where unexamined assumptions cause the most wasted work.
Instructions
Read these before starting any brainstorming session:
- Questioning Techniques — how to ask effective clarifying questions
- Approach Evaluation — how to generate, compare, and recommend approaches
- Design Presentation — how to structure and present designs for approval
- Anti-Patterns — common mistakes that derail brainstorming sessions
Checklist
More from roin-orca/agent-skills
brainstormingv2
You MUST use this before any creative work — designing features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design through structured collaborative dialogue before any implementation begins.
0json-tools
Helps with common JSON file tasks: formatting, validating, diffing, transforming, querying, and fixing malformed JSON. Use when the user asks to work with JSON data or .json files.
0brainstorm
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
0brainstormingv3
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
0git-commit-guidelines
Git commit message best practices. Use when writing commit messages, reviewing commits, or setting up commit conventions for a project. Ensures clear, consistent, and useful commit history.
0