brainstorming

To turn vague project ideas into actionable design requirements, provide a design briefing to clarify goals, explore context, and define success criteria. The skill asks clarifying questions one at a time to structure ideation and align on a plan before implementation.

Collaborative ideation for early-stage projects is facilitated by structuring context gathering and requirement discovery. The process involves proposing two to three design approaches to surface trade-offs, ensuring teams align on a clear design intent before any implementation begins.

You create a design doc and coordinate spec reviews by presenting design choices for approval and tracking decisions. A spec-review loop integrates feedback-driven iteration from exploration through implementation planning, ensuring all requirements are vetted.

Yes, you can use structured brainstorming for feature de-scoping sessions. The skill is explicitly applicable to de-scoping by guiding context exploration, asking clarifying questions, and generating design options to help teams align on refined project boundaries.

Structured ideation handles design trade-offs by proposing two to three distinct approaches for evaluation. It tracks decisions by creating a design doc and integrating a spec-review loop, ensuring feedback-driven iteration captures all approved choices.

You should avoid collaborative ideation when your project already has finalized design docs and approved specs. This skill targets early-stage ideation and de-scoping, so using it after implementation planning adds unnecessary context gathering and clarifying questions.