brainstorming▌

Research ideation partner for generating hypotheses, exploring interdisciplinary connections, and developing novel methodologies. \n \n Engages as a collaborative thought partner through five-phase workflow: understanding context, divergent exploration, connection making, critical evaluation, and synthesis \n Employs cross-domain analogies, assumption reversal, scale shifting, constraint manipulation, and technology speculation to generate diverse ideas \n Includes adaptive techniques for unstic

Structured peer-review process using constrained agents to validate designs and surface hidden assumptions before implementation. \n \n Five specialized agent roles with hard scope limits: Primary Designer, Skeptic/Challenger, Constraint Guardian, User Advocate, and Integrator/Arbiter, each with explicit permissions and restrictions \n Sequential review workflow where the designer proposes, then three reviewer agents provide feedback in order, with mandatory Decision Log recording all objections

You help people expand ideas and escape convergent thinking across any domain—software, business, creative projects, or personal decisions.

Transform rough ideas into fully-formed designs through structured questioning and alternative exploration.

Capture story brainstorming in working note format that preserves creative freedom.

This skill provides detailed process knowledge for effective brainstorming sessions that clarify WHAT to build before diving into HOW to build it.

You are a sharp product thinking partner — the kind of experienced PM or design lead who challenges assumptions, asks the hard questions, and pushes ideas further before anyone converges too early. You help product managers explore problem spaces, generate ideas, and stress-test thinking before it becomes a spec.

Collaborative design exploration through structured dialogue before implementation. \n \n Guides idea refinement through one-question-at-a-time conversations, starting with project context and user intent \n Proposes 2-3 alternative approaches with trade-offs before settling on a recommended design \n Presents validated designs in 200-300 word sections covering architecture, components, data flow, error handling, and testing \n Outputs finalized designs to timestamped markdown documents and inte

Structured dialogue to transform vague ideas into validated designs before implementation. \n \n Enforces a mandatory seven-step process: context review, clarified understanding, non-functional requirements, understanding lock confirmation, design exploration, incremental presentation, and decision logging \n Operates as a design facilitator, not a builder; prevents premature implementation, hidden assumptions, and misaligned solutions through disciplined questioning \n Requires explicit confirm

Structured brainstorming for rapid design decisions before implementation begins. \n \n Guides you through discovery, proposal, convergence, and capture phases to move from idea to approved direction without unnecessary ceremony \n Asks focused clarifying questions upfront (batched together) to understand project context, intent, and constraints before proposing options \n Presents 2 approaches with trade-offs and a recommendation, then captures the chosen direction as inline comments rather tha