Identify ambiguous requests and shape them into clear design directions.
npx skills add https://github.com/Ocean326/Agents --skill brainstorming-ocean326
Please help me install this Agent Skill. Skill: brainstorming Source: https://github.com/Ocean326/Agents/tree/main/skills/global/brainstorming Command: npx skills add https://github.com/Ocean326/Agents --skill brainstorming-ocean326
Ambiguity around feature requests or UX directions slows progress; this Skill guides discovery to turn vague inputs into well-scoped directions for design and planning.
Describe your ambiguous idea and ask Brainstorming to propose 2–3 concrete directions.
High-intent search queries and answers about installing and using this skill.
To turn vague ideas into clear design directions, you need guided discovery that surfaces needs, constraints, and success criteria. This process identifies ambiguous requests and shapes them into well-scoped options with established guardrails and trade-offs.
The best way to explore design options during early discovery is to propose 2-3 concrete approaches with defined trade-offs. This establishes a recommended direction and ensures acceptance criteria are set before committing to a plan.
Creating a design brief for team handoff requires consolidating discovery outputs into compact, actionable materials. This ensures durable handoff by documenting selected directions, guardrails, and acceptance criteria for implementation.
Yes, you can use brainstorming to establish acceptance criteria before committing to a plan. It identifies ambiguous requests and ensures guardrails, trade-offs, and success criteria are clearly defined during early product discovery.
Ideation and design discovery are limited to early planning phases, focusing on shaping vague inputs into clear directions. They do not handle actual implementation, engineering execution, or post-handoff development tasks.
You need guided discovery to specify requirements when facing ambiguous feature requests or UX directions. It surfaces necessary constraints and success criteria to prevent slow progress and ensure well-scoped planning.
AzrinPutraGuide exploratory conversations to elicit project requirements and generate an intent brief.
ulpi-ioTranslate UX concepts into design specs, tokens, and component briefs for Next.js and React handoff.
euroconicEvaluate feature scope, acceptance criteria, and trade-offs using a structured framework.
Steve-Smith-CODEIdentify and resolve ambiguities in software feature specifications using a structured requirements taxonomy.
