brainstorming
Brainstorming Ideas Into Designs
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 grnfromdark/autodevskill
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
22auto-dev
>
21systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
21requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
21subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
21verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
20