obra/superpowers@brainstorming
Brainstorming Ideas Into Designs
Overview
Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
Anti-Pattern: "This Is Too Simple To Need A Design"
Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
Checklist
You MUST create a task for each of these items and complete them in order:
More from openakita/openakita
obra/superpowers@systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
77obra/superpowers@subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
72obra/superpowers@writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
68file-manager
|
64obra/superpowers@using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
64obra/superpowers@finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
64