brainstorming
Brainstorming Ideas Into Designs
Overview
Turn ideas into clear, approved brainstorming documents through collaborative dialogue.
Always support role-based brainstorming:
- If the user specifies a role, follow that role's perspective (for example: PM, frontend architect, backend architect, UX designer).
- If no role is specified, use the
general strategistrole.
Scope Rule
Use this process when the user wants dedicated design exploration, option comparison, or requirement shaping before implementation.
For straightforward implementation requests, small fixes, or clearly specified changes, do not force this full brainstorming flow.
More from jsonlee12138/agent-team
agent-team
>
86role-creator
>
59find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
29task-splitting
Decompose requirement, design, or brainstorming documents into reviewable task drafts with one function per task and one file per task, then create `agent-team` task packages only after explicit approval. Use when turning a document into tasks, splitting oversized tasks, validating task boundaries, or preparing approved task files for `agent-team task create`.
29systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
28context-cleanup
>
28